Contents
How It Works
— Paul Graham, Y Combinator"The best startup ideas tend to have three things in common: they're something the founders themselves want, something they can build, and something few others realize are worth doing."
When to Use This Framework
Best Conditions for Solving Hidden Problems
| Dimension | Ideal conditions |
|---|---|
| Founder profile | Obsessive observers over domain experts. The best hidden-problem founders are people who notice things — the friend who says "why do we still do it this way?" at dinner. Domain expertise helps but can actually blind you to the friction because you've normalized it more deeply than anyone. Fresh eyes paired with execution ability is the ideal combination. |
| Stage | Ideation and early validation. This is fundamentally an opportunity-identification framework. It's most useful when you're searching for what to build, not when you're scaling something you've already built. |
| Market conditions | Best when enabling technology has recently matured but consumer behavior hasn't caught up. GPS + smartphones existed before Uber, but nobody had connected them to the taxi problem. Cloud storage existed before Dropbox, but nobody had made it invisible. The gap between what's technically possible and what people actually experience is where hidden problems live. |
| Competitive environment | Ideal when incumbents are complacent or structurally unable to see the problem. Taxi commissions had no incentive to fix hailing. Hotels had no incentive to unlock spare bedrooms. The hidden problem is often hidden precisely because the incumbents benefit from the status quo. |
| Inputs needed | Ethnographic observation (watching people, not surveying them), personal frustration journals, time-motion studies of daily workflows, technology capability scans, and conversations with people who recently switched contexts (new city, new job, new country) — because context-switchers temporarily lose their hedonic adaptation and can see friction clearly. |
When It Misleads
Failure Modes & Blind Spots
| Blind spot | What goes wrong |
|---|---|
| The problem is hidden because it's small | Not every normalized friction is a billion-dollar opportunity. Some things are mildly annoying but not painful enough to change behavior. The fact that people tolerate something doesn't mean they'll pay to fix it — sometimes the tolerance is rational because the problem genuinely isn't worth solving. |
| Founder projection bias | You notice a friction in your own life and assume it's universal. But your experience as a tech-savvy, high-income urbanite may not generalize. The "hidden problem" you see may be invisible to 95% of the population because they don't share your context. |
| Solution requires behavior change | The problem is real but the solution demands that people change deeply ingrained habits. Dropbox succeeded because it required almost zero behavior change — files just appeared. Many hidden-problem startups fail because their solution, while objectively better, requires users to do something fundamentally different. |
| The graveyard is full | The problem may not be as hidden as you think. Dozens of startups may have already tried and failed to solve it — not because the problem doesn't exist, but because the economics don't work, the timing is wrong, or the solution is technically harder than it appears. Check the graveyard before you dig. |
| Incumbents wake up | Once you name the hidden problem and prove demand, incumbents can often solve it faster than you can scale. Google adding cloud storage to Gmail, Apple adding screen time controls, banks adding peer-to-peer payments — the hidden problem becomes obvious, and the incumbent has distribution you don't. |
| Confusing inconvenience with willingness to pay | People may acknowledge the friction when you point it out but still not value the solution enough to pay for it. Free alternatives, workarounds, or simple inertia can kill conversion even when the problem is real. |
Step-by-Step Process
Train yourself to see what you've stopped seeing
Identify which frictions are systemic, not personal
Determine if the hidden problem is worth solving commercially
Build a solution that makes the friction vanish, not one that manages it
Build a moat before the problem becomes obvious to everyone
Questions to Ask Yourself
Company Examples





Adjacent Frameworks
Analyst's Take
Opportunity Checklist
Hidden Problem Opportunity Scorecard
Top Resources
Why this matters next
Uber applied the Network Effects mental model
Uber applied the Compounding mental model
Uber applied the Inertia mental model
Uber applied the Intelligence mental model
Uber applied the Scale mental model
Uber applied the Environment mental model
Continue exploring
Framework
Recent funding rounds
Analyze companies that have recently secured significant investment, identifying
Framework
Unbundling
Breaking down a bundled product or service into separate, standalone offerings,
Framework
Industry timing arbitrage
Apply newly developed technology from one industry to another that hasn't yet ad
Framework
Acqui-Deaths
Identify opportunities created when large companies acquire startups, potentiall
Framework
Three-Star reviews
Find business opportunities by analyzing moderately satisfied customers' feedbac
Framework
Niche down
Focus on a highly specific market segment or customer base, becoming a specialis
More like this, in your inbox
I send a newsletter every week — free, no spam, unsubscribe anytime.