AboutHow we built thisSponsorshipShop
SearchSubscribeDecision ToolsBusiness ModelsFrameworksReading Lists
Privacy PolicyTerms of UseCookie PolicyRefund PolicyAccessibilityDisclaimer

© 2026 Faster Than Normal. All rights reserved.

Faster Than Normal
DecisionsPeopleBusinessesNewsletterSubscribe
Start reading →
  1. Home
  2. Business frameworks
  3. Solve hidden problems lying in plain sight

Solve hidden problems lying in plain sight

22 min read

On this page

  • How It Works
  • When to Use This Framework
  • When It Misleads
  • Step-by-Step Process
  • Questions to Ask Yourself
  • Company Examples
  • Adjacent Frameworks
  • Analyst's Take
  • Opportunity Checklist
  • Top Resources

Contents

  1. 1. How It Works
  2. 2. When to Use This Framework
  3. 3. When It Misleads
  4. 4. Step-by-Step Process
  5. 5. Questions to Ask Yourself
  6. 6. Company Examples
  7. 7. Adjacent Frameworks
  8. 8. Analyst's Take
  9. 9. Opportunity Checklist
  10. 10. Top Resources
The best startup opportunities often hide in plain sight — problems so universal, so deeply embedded in daily life, that people have stopped recognizing them as problems at all. This framework is a systematic approach to identifying and solving the inefficiencies, frictions, and absurdities that billions of people tolerate every day simply because they've never imagined an alternative.
Section 1

How It Works

The core cognitive shift is deceptively simple: stop looking for problems people complain about and start looking for problems people have stopped complaining about. The most valuable startup opportunities aren't in the things people actively hate — those attract competition immediately. They're in the things people have accepted as immutable features of reality. The taxi was slow, unreliable, and impossible to hail in the rain for decades. Nobody wrote angry blog posts about it. They just got wet.
This works because of a well-documented psychological phenomenon: hedonic adaptation applied to friction. Humans are extraordinarily good at normalizing inconvenience. When a pain point has existed for long enough, it stops registering as a pain point and becomes "just the way things are." File syncing was a nightmare in 2007 — people emailed documents to themselves, carried USB drives, and lost work constantly. But nobody described this as a crisis. It was simply how computers worked. Drew Houston saw the gap between what people tolerated and what was technically possible, and Dropbox was born.
The framework exploits an asymmetry between what people say they need and what they actually need. If you ask someone in 2007 what they want, they'll tell you a faster horse — a bigger USB drive, a better email attachment system. They won't tell you they want seamless cloud sync because they can't imagine it. The founder's job is to see the invisible friction, name it, and then build the thing that makes people say "how did I ever live without this?" That retroactive obviousness is the signature of a hidden-problem startup.
The reason this framework is so powerful — and so difficult — is that it requires you to override your own hedonic adaptation. You've normalized the same frictions everyone else has. The skill isn't technical. It's perceptual. You have to train yourself to notice what you've trained yourself to ignore.
"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."
— Paul Graham, Y Combinator
Section 2

When to Use This Framework

✓

Best Conditions for Solving Hidden Problems

DimensionIdeal conditions
Founder profileObsessive 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.
StageIdeation 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 conditionsBest 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 environmentIdeal 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 neededEthnographic 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.
This framework is especially potent right now because AI has created a massive gap between what's technically possible and what most people experience daily. Millions of knowledge workers still copy-paste data between spreadsheets, manually summarize meeting notes, and search through email threads for information that should be instantly retrievable. These are hidden problems lying in plain sight — the kind that will look absurd in five years.
Section 3

When It Misleads

⚠

Failure Modes & Blind Spots

Blind spotWhat goes wrong
The problem is hidden because it's smallNot 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 biasYou 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 changeThe 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 fullThe 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 upOnce 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 payPeople 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.
The single most common mistake is falling in love with the insight and skipping the economics. Founders who spot a genuine hidden problem often become so enamored with the elegance of their observation that they skip the hard questions: Is this a $10/month problem or a $100/month problem? Can I reach these people cheaply? Will they switch from their current workaround? The insight is necessary but not sufficient. The business model is what turns a clever observation into a company.
Section 4

Step-by-Step Process

Step 1 — Defamiliarize

Train yourself to see what you've stopped seeing

Spend two weeks keeping a daily friction journal. Every time you encounter something annoying, slow, confusing, or unnecessarily manual — write it down. Don't filter for "startup ideas." Just document friction. Pay special attention to moments where you think "that's just how it works." Those are the highest-signal entries. Supplement by watching someone outside your demographic use technology, navigate a city, or complete a task you find trivial. Their confusion reveals your blind spots.
Tools: Friction journal, context switching, beginner's mind exercises, shadowing non-tech users
Step 2 — Pattern-Match

Identify which frictions are systemic, not personal

Review your friction journal and look for entries that are structural — problems caused by how systems, industries, or institutions work, not by your personal preferences. Cross-reference with public signals: Are people complaining about this on Reddit without framing it as a solvable problem? Are there 3-star app reviews that describe workarounds for the exact friction you noticed? Are there entire subreddits dedicated to navigating a process that shouldn't be this hard?
Tools: Reddit, Twitter/X, Quora, customer review mining, Google Trends, App Store reviews
Step 3 — Size and Validate

Determine if the hidden problem is worth solving commercially

Run 30+ conversations using Mom Test principles — don't pitch your solution, ask about their current behavior. How do they handle this friction today? How much time or money does it cost them? Have they tried alternatives? Would they pay to make it disappear? Simultaneously, estimate the addressable market: How many people experience this friction, how frequently, and at what economic cost? Check Crunchbase and Product Hunt for startups that have already attempted this — their outcomes are data.
Tools: TAM estimation, willingness-to-pay interviews, competitive landscape scan, The Mom Test methodology
Step 4 — Prototype the Disappearance

Build a solution that makes the friction vanish, not one that manages it

The best hidden-problem solutions don't give users a better tool to manage the friction — they eliminate the friction entirely. Uber didn't give you a better way to hail a taxi; it removed hailing from the equation. Dropbox didn't give you a better USB drive; it made the USB drive irrelevant. Prototype the experience of the problem disappearing. Test whether users have the "how did I ever live without this?" reaction. If they say "that's nice," you haven't gone far enough.
Tools: Figma, no-code platforms (Bubble, Retool), concierge MVP, Wizard of Oz testing
Step 5 — Defend the Insight

Build a moat before the problem becomes obvious to everyone

Once you solve a hidden problem, it stops being hidden. Your window of advantage is the time between when you name the problem and when incumbents or copycats arrive. Use that window to build defensibility: network effects (Uber's driver liquidity), data moats (Dropbox's sync intelligence), brand association (Airbnb owning "stay like a local"), or switching costs (users' files, history, and habits locked into your platform). Document your defensibility thesis before you launch.
Deliverable: Defensibility memo — network effects, data advantages, switching costs, brand, regulatory positioning
Section 5

Questions to Ask Yourself

Discovery
What do I do every day that involves unnecessary friction — steps that exist because "that's just how it works"?
What would a visitor from 2035 find absurd about how we currently do this?
Where do people build elaborate workarounds instead of demanding a real solution?
What has technology made possible in the last 2–3 years that hasn't yet been applied to this everyday friction?
Who recently switched contexts (new city, new job, new country) and was shocked by something everyone else accepts?
Validation
When I describe this friction to people, do they say "oh my god, yes" — or do they shrug?
Can I find at least 3 independent signals (Reddit threads, app reviews, forum posts) of people describing this friction without framing it as solvable?
How much time or money does this friction cost the average person per week — and is that enough to drive adoption?
Have previous startups tried to solve this? If so, why did they fail — was it the problem, the solution, or the timing?
Solution Design
Does my solution eliminate the friction or merely reduce it? Would a user describe the experience as "magical" or "slightly better"?
How much behavior change does my solution require — and is that change smaller than the pain of the status quo?
Can I deliver the core value in the first 60 seconds of use, before the user has to invest effort?
Defensibility
Once I name this problem publicly, how long before an incumbent can ship a competing solution?
What structural advantage do I have that an incumbent with 100x my resources cannot easily replicate?
Does my solution get better with more users (network effects) or more data — creating a compounding moat?
Am I building a product or a feature? Could Google, Apple, or Amazon add this in a quarterly update?
Section 6

Company Examples

Uber logo
Uber
Made the invisible friction of hailing taxis visible — then eliminated it
Before Uber, getting a taxi in San Francisco meant standing on a corner, hoping one would pass, having no idea if the driver would accept your destination, and carrying cash because card machines were "broken." Nobody called this a crisis — it was just how taxis worked. Travis Kalanick and Garrett Camp's insight was that GPS-enabled smartphones had made this friction technically unnecessary since roughly 2008, but nobody had connected the dots. Uber's first version launched in San Francisco in 2010 as a black car service; by 2011 it had expanded to UberX. The company reached a peak valuation of $82 billion at IPO in 2019. The key insight wasn't ride-hailing — it was that the entire concept of "hailing" was an artifact of pre-smartphone technology that billions of people had simply accepted.
Airbnb logo
Airbnb
Revealed that millions of spare bedrooms were an untapped hospitality network
Hotels were expensive. Millions of people had spare rooms. These two facts coexisted for decades without anyone treating the gap between them as a solvable problem. Brian Chesky and Joe Gebbia's original insight in 2007 was narrow — rent air mattresses during a sold-out conference — but it revealed a hidden problem at massive scale: the global hospitality industry had trained consumers to believe that "accommodation" meant "hotel," while an enormous supply of underutilized living space sat idle. Airbnb reached 4 million hosts and over 1.5 billion guest arrivals by 2023. The friction they solved wasn't just price — it was the artificial constraint that accommodation had to be a commercial product rather than a peer-to-peer exchange.
Dropbox logo
Dropbox
Solved the file-access problem people had stopped recognizing as a problem
Drew Houston famously conceived Dropbox after repeatedly forgetting his USB drive on the bus. But the deeper insight was that millions of knowledge workers had built elaborate, fragile workarounds — emailing files to themselves, maintaining duplicate folders on multiple machines, losing version control constantly — and had accepted this as normal computing. Houston's Y Combinator application in 2007 noted that existing solutions (FTP, WebDAV, rsync) were too technical for mainstream users. Dropbox's genius was making sync invisible: files just appeared on every device. The company reached 700 million registered users and generated $2.5 billion in revenue in 2023. The problem was so hidden that when Houston first pitched it, many investors said "I can already do this" — not realizing that their own workarounds were the problem.
CostCo logo
CostCo
Exposed the hidden markup in retail that consumers had normalized
The average American grocery store operates on 25–30% gross margins. Consumers had accepted retail pricing as a fixed feature of commerce — you pay what the store charges, and the markup is invisible. Costco's founding insight in 1983 was that this markup was a hidden problem: consumers were paying a significant premium for the convenience of small-format retail, product variety, and brand marketing — most of which they didn't actually value. By stripping out those costs, limiting SKUs to roughly 3,700 (versus 30,000+ at a typical supermarket), and capping margins at 14–15%, Costco made the hidden tax visible. The membership model — $65–$130/year — reframed the relationship: you pay us directly, and we stop overcharging you on products. Costco generated over $242 billion in revenue in fiscal 2023 with membership fees accounting for the majority of operating profit.
Calm logo
Calm
Named the hidden problem of chronic stress that people had accepted as modern life
Stress, anxiety, and poor sleep were not new problems in 2012 when Calm launched. They were arguably the most universal problems in the developed world. But they were hidden in plain sight because people had categorized them as personal failings rather than solvable conditions. Calm's insight was that the same smartphone causing much of the anxiety could also deliver the solution — guided meditation, sleep stories, breathing exercises — in a format that required no prior experience, no therapist appointment, and no stigma. The app reached over 100 million downloads and was valued at $2 billion by 2020. Calm didn't invent meditation. It reframed a problem that billions of people tolerated as something a $70/year subscription could meaningfully address.
Section 7

Adjacent Frameworks

Hidden problems rarely exist in isolation. Here's how this framework connects to the broader toolkit:
Pairs well with
Three-Star reviews
Three-star reviews are where people describe hidden problems in their own words. They're not angry enough to one-star, not satisfied enough to five-star — they're articulating the friction they've half-accepted. Mining these reviews is one of the most efficient ways to surface hidden problems.
Pairs well with
Spot the fringes — what are nerds doing on weekends
Power users and hobbyists often build ugly, manual solutions to hidden problems years before the mainstream notices. If someone has written a Python script to automate something that millions of people do manually, you've found a hidden problem with a proven solution waiting to be productized.
In tension with
Build a Copycat
Copycat assumes the problem is already visible and solved elsewhere. Hidden problems, by definition, haven't been solved anywhere yet. These frameworks pull in opposite directions — one rewards observation, the other rewards replication.
In tension with
Category creation
Category creation often involves educating the market that a problem exists. Hidden-problem startups face the same challenge — but the best ones skip education entirely by making the solution so intuitive that the problem becomes retroactively obvious. The tension is in whether you name the problem or just solve it.
Apply next
Find processes where people spend hours researching for information/data and give it to them easily
Once you've identified a hidden problem, this framework helps you operationalize the solution — particularly for information-asymmetry problems where the friction is in finding, comparing, or understanding data that should be readily accessible.
Apply next
Find processes for people and companies with a lot of steps and pain (friction) in going through and make fast and simple
The natural execution companion. After identifying the hidden friction, this framework provides the methodology for systematically eliminating steps, reducing cognitive load, and compressing multi-step processes into single actions.
Section 8

Analyst's Take

Faster Than Normal — Editorial View
Here's what most people get wrong about this framework: they think it's about having a brilliant insight. It's not. It's about having a disciplined practice of noticing. The founders who consistently find hidden problems aren't smarter than everyone else — they've just built a habit of questioning things that other people accept. Drew Houston didn't have a eureka moment. He had a USB drive he kept forgetting. The difference is that he treated his frustration as data rather than dismissing it.
The framework is deceptively hard to execute because it requires you to fight your own psychology. Hedonic adaptation is powerful. By the time you're an adult, you've normalized thousands of frictions — and the more expert you become in a domain, the more deeply you've normalized the frictions within it. This is why the best hidden-problem founders are often outsiders to the industry they disrupt. Chesky and Gebbia were designers, not hoteliers. Houston was an engineer, not an IT administrator. Kalanick was a serial entrepreneur, not a transportation executive. Their ignorance was an asset because it prevented them from accepting the status quo.
The biggest risk I see founders make with this framework is confusing "I find this annoying" with "this is a hidden problem worth solving." The gap between personal irritation and commercial opportunity is enormous. I've seen dozens of startups built on genuine hidden problems that turned out to be $5 million markets, not $500 million markets. The friction was real. The willingness to pay was not. Before you build anything, you need to answer one question with brutal honesty: Is this a problem people will pay to solve, or is it a problem people will thank you for solving and then continue using their free workaround?
The framework is most powerful when combined with a technology inflection point. The hidden problems that produce the biggest companies aren't just old frictions — they're old frictions that have become newly solvable because of a recent technology shift. Uber needed smartphones with GPS. Airbnb needed widespread broadband and digital payments. Dropbox needed cheap cloud storage. Right now, the equivalent inflection is large language models. The number of hidden problems that LLMs make newly solvable — summarizing, translating, searching, drafting, analyzing — is staggering. The founders who will build the next generation of hidden-problem companies are the ones who can see the gap between what AI can now do and what people are still doing manually.
My honest assessment: this is one of the highest-ceiling frameworks in the entire library, but it has a low hit rate. For every Uber, there are a hundred startups that correctly identified a hidden problem and still failed — because the market was too small, the behavior change was too large, or the incumbent woke up too fast. Use this framework for ideation, but pair it ruthlessly with economic validation before you commit.
Section 9

Opportunity Checklist

Use this scorecard to evaluate whether a specific hidden problem is worth building a company around. Score each item as yes (1 point) or no (0 points).

Hidden Problem Opportunity Scorecard

The friction affects millions of people on a daily or weekly basis, not just a niche segment.
People have built workarounds (manual processes, hacks, spreadsheets) rather than demanding a real solution — indicating the problem is real but normalized.
A recent technology shift (mobile, cloud, AI, APIs) has made this problem newly solvable in a way that wasn't possible 3–5 years ago.
When I describe the friction to potential users, they react with recognition ("oh my god, yes") rather than indifference.
The incumbent industry benefits from the status quo and has no structural incentive to solve this problem.
My solution eliminates the friction entirely rather than merely reducing it — users would describe the experience as "magical."
The solution requires minimal behavior change — it fits into existing workflows rather than demanding new ones.
I can deliver the core value within 60 seconds of first use, before the user has invested significant effort.
The addressable market is large enough to support a venture-scale outcome ($1B+ TAM) or a highly profitable niche business.
I have a credible defensibility thesis — network effects, data moats, or brand — that protects me once the problem becomes visible to incumbents.
I have checked the graveyard: previous attempts to solve this either don't exist or failed for reasons I can specifically identify and avoid.
Section 10

Top Resources

01
Zero to One — Peter Thiel (2014)
Book
Thiel's central argument — that the best businesses are built on "secrets" that are true but not widely believed — is the philosophical foundation of the hidden-problem framework. Chapter 8 on secrets is the most directly relevant: Thiel argues that valuable secrets are hiding in plain sight because people have been trained not to look for them. Essential reading for anyone practicing this framework.
02
The Mom Test — Rob Fitzpatrick (2013)
Book
The single best guide to validating whether a hidden problem is real or just your projection. Fitzpatrick's methodology — ask about behavior, not opinions; never pitch your solution — is perfectly suited to hidden-problem discovery because the people experiencing the friction often can't articulate it directly. You have to infer the problem from how they describe their current behavior.
03
Thinking, Fast and Slow — Daniel Kahneman (2011)
Book
The scientific foundation for why hidden problems stay hidden. Kahneman's work on cognitive biases — particularly status quo bias, anchoring, and the availability heuristic — explains why billions of people tolerate friction they could avoid. Understanding these mechanisms makes you better at spotting the frictions others can't see.
04
“Do Things That Don’t Scale” — Paul Graham
Essay
Graham's classic essay is directly relevant to the early stages of hidden-problem startups. When you've identified a friction that nobody else sees, you can't rely on viral growth or word-of-mouth — you have to manually recruit early users and demonstrate the value one person at a time. This essay provides the tactical playbook for that phase.
05
Inspired — Marty Cagan (2017)
Book
Cagan's framework for product discovery — particularly the distinction between "customer problems" and "customer requests" — is essential for hidden-problem founders. The book provides structured methods for observing users, identifying unmet needs they can't articulate, and prototyping solutions that test whether the friction is worth solving commercially.

Why this matters next

mental modelsNetwork Effects

Uber applied the Network Effects mental model

mental modelsCompounding

Uber applied the Compounding mental model

mental modelsInertia

Uber applied the Inertia mental model

mental modelsIntelligence

Uber applied the Intelligence mental model

mental modelsScale

Uber applied the Scale mental model

mental modelsEnvironment

Uber applied the Environment mental model

Continue exploring

RR

Framework

Recent funding rounds

Analyze companies that have recently secured significant investment, identifying

UN

Framework

Unbundling

Breaking down a bundled product or service into separate, standalone offerings,

IA

Framework

Industry timing arbitrage

Apply newly developed technology from one industry to another that hasn't yet ad

AC

Framework

Acqui-Deaths

Identify opportunities created when large companies acquire startups, potentiall

TR

Framework

Three-Star reviews

Find business opportunities by analyzing moderately satisfied customers' feedbac

ND

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.

Or open the full subscribe page.

On this page

  • How It Works
  • When to Use This Framework
  • When It Misleads
  • Step-by-Step Process
  • Questions to Ask Yourself
  • Company Examples
  • Adjacent Frameworks
  • Analyst's Take
  • Opportunity Checklist
  • Top Resources