An idea is a guess about a solution. A problem is a fact about someone's life. Start from the fact.
10 min read · Level 1
You can be wrong about an idea and recover; you cannot be wrong about the problem and recover, because everything you build sits on top of it. Starting from your solution also quietly corrupts your research — you begin wanting a particular answer, and people are kind. The founders who find real problems are not more creative. They are more willing to be told they were wrong while it is still cheap.
An idea is your proposed solution: 'an app that does X'. A problem is something a specific person currently struggles with, at a cost, and works around today.
Ideas are cheap and yours. Problems are expensive to find and belong to other people. Building starts from the problem.
Because you can be wrong about an idea and still succeed — you change the solution. If you are wrong about the problem, nothing you build can rescue it.
Starting from an idea also makes you defensive during discovery: you want people to like it, so you ask questions that produce agreement rather than information.
Idea-first: 'A social network for dog owners.' You build for four months. Nobody comes. There is no way to iterate, because the assumption underneath — that dog owners want another social network — was never checked.
Problem-first: 'Dog owners who travel struggle to find someone they trust to look after their dog. They currently ask in a local WhatsApp group, and it fails about a third of the time.'
That is a fact you can verify by talking to twenty dog owners. The solution might be a marketplace, a vetting service or a better group tool — but any of them can be tested, because the problem is stable and the solution is the variable.
First-time founders often describe their problem in terms of their solution: 'the problem is there is no good app for this'. That is not a problem, it is the absence of your idea.
A real problem statement contains a person, a situation, a cost, and what they do instead today. If any of the four is missing, you are still describing an idea.
If you cannot describe it without referring to what you want to build, you have not found the problem yet.
Not 'small businesses'. A role, a situation, a moment when the problem bites.
Everyone solves their problems somehow. The workaround tells you how painful it really is and what you compete with.
Time, money, risk or stress. If the workaround is cheap and fine, there is no room for a product.
Ten conversations. If most do not recognise the problem, it is yours and not theirs — which is useful to know now.
At the very start, and again after any pivot or failed launch.
Some products genuinely start from a technical capability rather than a problem. That is legitimate — but you still have to find whose problem the capability solves before you build a company on it.
Stripe's founders had repeatedly experienced how difficult it was for developers to accept payments online — days of paperwork and integration for something that should have taken minutes. The company began from that specific, personally felt friction rather than from a decision to enter payments.
A problem you have personally felt gives you an unfair head start on judging what is genuinely painful versus merely annoying.
The most common non-problem statement founders bring. It describes the absence of their idea, not a difficulty anyone has. A real problem statement contains a person, a situation, a cost and what they do instead today — and if any of the four is missing, no amount of building will supply it.
Write your problem without naming your solution. If you cannot, you have an idea and no problem, and that is the most useful thing to learn this week.
Create a free account to read the rest and apply it to your own startup.