Nobody Asks for the Future

If you ask customers what they want, they'll say faster horses. The line is attributed to Henry Ford, popularized by Jobs, and misunderstood by almost everyone who quotes it. It does not mean ignore your customers. It means understand what they're actually telling you when they speak.

This is Part 3 of a four-part series on my product design philosophy. The rest: Part 1 — If Your Product Needs a Manual, the Design Already Failed, Part 2 — Start With the Experience, and Part 4 — Saying No to 1,000 Good Ideas.

Customers are experts in problems, amateurs in solutions

"Faster horses" is actually a perfect piece of customer feedback, if you listen to it correctly. The customer is telling you the problem with total precision: getting places takes too long. What they can't tell you is the solution, because they can only describe the future using the parts of the present. Nobody who had never seen a car could request one. Nobody asked for the iPhone. Nobody filed a feature request for the spreadsheet, the search engine, or the chat-based coding agent.

So the job splits cleanly. Take the problem statement literally, it's gold. Take the solution request as a clue, never as a spec. When a customer asks for a faster horse, the roadmap-driven team breeds horses. The team that's listening hears "speed matters more than anything" and starts questioning the horse.

This is why I'm cold on market research as a source of direction. Research is a rear-view mirror; it describes the world the last generation of products created. It can validate, it can prioritize, it can kill a bad assumption, all valuable. But it cannot show you the future, because the future isn't in the data yet. Create products people don't know they need. By the time they know they need it, someone has already built it.

Innovation is seeing, then having the nerve to act

True innovation means seeing what others can't, and the romantic version of that sentence stops there, as if vision were a gift. It isn't. In my experience the "seeing" is mostly proximity: the people who spot the future early are the ones closest to the friction, watching real users do real work and noticing the workaround everyone else has normalized. The insight is lying on the workshop floor. Most people step over it daily.

The rare part isn't the seeing. It's the nerve. Acting on something only you can see means committing resources to a thing no customer asked for, no analyst projected, and no competitor validates. It will look wrong to smart people, by definition, because if it looked right to everyone it wouldn't be early. That's why conviction is a design input, not a personality flaw. "Think different" was never decoration; it's the willingness to be temporarily wrong in public on the way to being right.

Own what carries the vision

Jobs' refusal to build on other people's components, the obsessive integration of hardware and software, gets dismissed as control-freakery. It was strategy. Great experiences come from controlling the stack that delivers them, because every layer you don't control is a place your vision gets negotiated down to someone else's roadmap.

Translated out of Cupertino and into the companies I work with: you don't need to build everything, you need to own the layers where your differentiation lives. Buy commodity, build identity. Your auth, your billing, your email delivery, rent them happily. But the workflow that is your product, the data model that encodes how you see the customer's world, the experience from Part 2 that you worked backwards from? Outsource those and you've outsourced the company. I've written about owning the whole stack organizationally; this is the product version of the same conviction. Everything must work together seamlessly, and seamless is precisely the property you cannot buy from three vendors and glue.

The modern test case is AI. Companies bolting a vendor's chatbot onto an unchanged product are integrating someone else's component and calling it innovation, faster horses with a plugin. The companies getting it right are rethinking what their product even is now that software can act, and they're keeping that rethinking in-house, because it's the new core.

Conviction has a price, and it's Part 4

Betting on what you see instead of what's requested means you will sometimes be wrong, and you'll be wrong with real money. The only thing that makes this philosophy survivable is the discipline that pairs with it: ferocious focus, small bets, working prototypes, and the willingness to kill what isn't great. That discipline is the finale of this series: saying no to 1,000 good ideas.

If you're sitting on something only you can see and you need help finding the nerve, or the plan, let's talk →