The dominant story of human progress goes like this: Humans become aware of a need, then develop solutions to meet it. We recognize we’re hungry, then we hunt. We realize we’re sick, then we develop medicine. We identify a market gap, then we innovate to fill it.
This narrative is compelling, intuitive, and almost entirely backward.
If you look at the major inflection points in human well-being, the moments when lifespans jumped, diseases retreated, and material abundance exploded, you find a different pattern. Capability expansion precedes need articulation. Technological evolution drives progress, not the expansion of what we know we want.
The historical pattern
Consider the most significant improvements in human health and longevity:
-
Germ theory and antibiotics: We didn’t discover we needed to cure bacterial infections and then develop penicillin. We developed microscopes and staining techniques that revealed the microbial world. Only then could we even conceptualize antibacterial therapy as a possibility.
-
Anesthesia: We didn’t realize surgery needed to be painless and then develop ether. We discovered chemical properties that induced unconsciousness, then discovered that surgery could be radically transformed.
-
Vaccination: We didn’t identify the need to prevent smallpox and then develop cowpox inoculation. We stumbled upon a biological phenomenon (milkmaids not getting smallpox), investigated it, and only then understood what disease prevention could look like.
In each case, the capability (measurement, conceptual framework, delivery technology) emerged first. The application came later, often in ways the original innovators didn’t anticipate.
The market-led innovation mistake
This history exposes a flaw in contemporary business strategy. We build organizations as if customer awareness must precede innovation. Marketing departments articulate customer needs. R&D functions serve those needs. Product roadmaps begin with “voice of the customer.”
But if capability precedes need, this structure is backward. Customer voice can tell us about wants we already know how to satisfy. It cannot tell us about needs we lack the capability to address, or even imagine.
This is why survey-based market research is so effective at incremental innovation and so poor at breakthrough innovation. Customers can tell you they want a faster horse. They cannot tell you they want an automobile.
The flying car method
This suggests a radical reorientation of innovation strategy. Rather than beginning with customer needs, organizations should begin with technological possibility. They should invest in expanding capabilities even when no obvious business application exists.
This is the “flying car” method: develop capabilities without clear use cases, then search for problems they solve. It’s typically derided as wasteful, unfocused, the epitome of solution-in-search-of-a-problem thinking.
But if capability precedes need, this isn’t a bug. It’s a feature. The flying car method is how most consequential technologies actually emerge.
Organizational implications
What would an organization built around ability-first innovation look like?
-
R independence: R&D would not serve marketing. It would have its own mandate, budget, and decision rights.
-
Capability tracking: Organizations would measure “capability expansion” as a leading indicator (new measurement technologies, new delivery methods, new conceptual frameworks), not just patent count or R&D spend.
-
Tolerance for ambiguity: Budget would flow to research projects without clear business cases, based on assessments of capability potential rather than market need.
-
Time horizons: Investors would evaluate R&D spending on decadal timeframes, recognizing that today’s capability expansion may solve problems customers don’t know they have yet.
The counterargument
Not all innovation is ability-first. Some domains (painkillers, contraceptives, entertainment) are clearly need-led. Humans have always known they wanted to avoid pain, control reproduction, and be amused. In these areas, customer articulation precedes capability.
But these may be the exceptions that prove the rule. They’re domains where human want is stable, obvious, and biologically hardwired. For most of human history, we didn’t know what was possible. How could we articulate needs for capabilities we couldn’t imagine?
Why this matters now
We’re in a period of technological stagnation in many sectors: construction, education, transportation, energy. Customer wants in these domains are well-articulated. Everyone knows they want cheaper housing, better schools, faster commutes, cleaner energy.
If need-awareness drove innovation, these sectors should be booming. They’re not. What’s missing isn’t customer voice. It’s capability expansion.
The path forward isn’t better market research. It’s investing in the foundational technologies (the measurement methods, the delivery platforms, the conceptual frameworks) that will reveal problems we don’t yet know we have.
Self-awareness didn’t get us this far. Capability did. It’s time we built our innovation organizations around that fact.