Two different ways to think about what to build

There are two kinds of conversations you can have about a product.

One starts with features. “Let’s add this. Let’s build that.” The discussion is about what the product will include.

The other starts with outcomes. “How do we help users finish their week faster?” The discussion is about what changes for the user.

These sound subtle. They feel like the same thing. They’re not. The first one almost always produces a bigger, busier, more confused product. The second one produces a sharper, more useful one.

Founders who learn to default to outcome-first thinking quietly outperform founders who default to feature-first thinking. The difference adds up over months and years.

Why feature-first thinking creeps in

Features feel concrete. They’re easy...

Thinking in outcomes, not features