Opportunity Discovery: When "Find a Problem" Isn't Working
Opportunity Discovery: When "Find a Problem" Isn't Working The Problem in Concrete Terms You've read the advice: "Talk to customers," "Scratch your own itch," "Look for complaints on Reddit." You've done the interviews. You've scanned the forums. You've listed fifty problems. And you're still stuck—either because every problem feels too small, too crowded, too hard to monetize, or because you…
Opportunity discovery often feels like a frustrating dead end—no matter how many problems you uncover, it's hard to pinpoint the right one to pursue. There are three key stumbling blocks that typically arise: the "So What?" problem, where customers complain about pain points but have no intention of paying to fix them; the "Already Solved" problem, where every issue you identify already has numerous competitors and failed attempts; and the "Vague Hunch" problem, where you sense an opportunity but can't articulate a clear, testable hypothesis.
The issue lies in treating opportunity discovery as research rather than hypothesis generation under uncertainty. Customer interviews, scratching your own itch, and mining forums rarely yield the valuable insights needed. The real challenge is constructing a hypothesis that matches a specific problem, audience, solution approach, and go-to-market strategy.
To overcome these hurdles, start by selecting a domain you can access, then map the workflow in that domain, focusing on friction rather than problems. Extract candidate opportunities using three filters: budget authority, workaround cost, and no strategic incumbent lock-in. This method helps you move from a vague space to a testable hypothesis, rather than relying on traditional research methods that often fail to deliver actionable insights.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
