What we're actually optimizing for
Every major innovation in human history shares the same underlying goal: shrink the time and effort from what we think we want to the actual output.
We want to get from point A to point B. First we walked. Then we invented the wheel. Then the cart, the horse, the car, the plane. Each step compressed the time and the physical effort between intention and arrival.
Same pattern everywhere. We wanted to remember things—so we wrote. Writing wasn't enough, so we built the printing press. Then the typewriter, the computer, the cloud. We wanted to talk to someone far away—so we had runners, then mail, then the telegraph, the phone, the internet. In every case we're not inventing new desires; we're inventing faster, easier paths from desire to outcome.
The pattern holds for small things too. A better form shaves a minute off a workflow. A clearer label removes a decision. A default removes a click. None of that is glamorous in a pitch deck, but it is the same family of optimization: less standing between intent and result.
Friction hides in the gap
People talk about "product-market fit" as if the market were a single static object. Often the work is closer to fit between intention and outcome. You thought you wanted X; what you actually do is fight the interface until you get something like Y. Great products narrow that gap. Bad ones widen it with extra steps, jargon, or surprise.
That is why user research that only asks "what do you want?" underperforms. People are bad at naming the friction. They are good at showing you where they stall, repeat work, or open three tabs to finish one task. The delay is the product.
Why it matters for what we build
When you're building a product or a feature, the same lens applies. The best innovations don't create new wants—they shorten or smooth the path from an existing want to its fulfillment. Less friction, less time, less cognitive or physical effort.
Sometimes the win is batching: do five related actions in one flow instead of five trips. Sometimes it is prediction: show the next likely action before the user asks. Sometimes it is honesty: kill a feature that only exists because the org chart needed a roadmap bullet. In each case you are asking where the user's energy is leaking, and whether you can reclaim it.
That's the thread that runs from the wheel to the smartphone to the next wave of AI tools. The question to ask isn't only "what do users want?" but "between their intention and the outcome, where is the delay and the effort?" Then go compress that.
Compression has a cost
Shrinking the gap is not always good. If you make it too easy to do the wrong thing, you have optimized for speed off a cliff. If you remove friction that was actually a guardrail, you get accidents. So the design question pairs with an ethics question: whose intention are we serving, and what outcome are we making inevitable?
Still, the north star is recognizable. Less time, less waste, fewer steps between what someone meant and what they got. Everything else is implementation detail.