Skip to content
Abhiram Chandramohan
Idea discovery

Fall in love with the problem, not your solution

Abhiram Chandramohan · 2 min read

In short

Most startups fail by building the wrong thing, not by building it badly. Founders who start from a sharp problem statement and its riskiest assumption reach a go, pivot or kill decision before they spend their savings.

After advising more than 200 startups across 18 sectors, I see the same pattern again and again. A founder arrives with a beautiful solution: the screens are sketched, the features are listed, sometimes a developer is already hired. What is missing is a clear answer to a simpler question: whose problem is this, and how badly does it hurt?

Why do founders fall in love with the solution?

Because solutions are fun. They are tangible, you can show them to friends, and they feel like progress. Problems are uncomfortable. Studying them means hearing that your idea might not matter.

But the market does not pay for solutions. It pays for problems that go away.

What does problem-first look like in practice?

It starts with three questions, asked of real people rather than of a survey form:

  • Who feels this pain most? Not "small businesses", but the operations manager at a 20-person logistics firm who loses four hours every Friday to manual reconciliation.
  • How do they cope today? Every real problem already has a workaround: a spreadsheet, a WhatsApp group, an intern. The workaround is your real competitor.
  • What does it cost them? In money, time, risk or reputation. If nobody can name the cost, the problem is not urgent enough.

How do you turn a hunch into a testable bet?

Write one sharp problem statement, then write down the single assumption that would kill the idea if it were wrong. That is your riskiest assumption. Your first job is not to build; it is to find the cheapest experiment that could prove that assumption wrong.

Most founders fall in love with their solution. I make them fall in love with the problem first.

What do you get from this?

A go, pivot or kill decision backed by evidence, before you spend your savings. Sometimes the answer is "kill", and that is a win: a few weeks of honest discovery is far cheaper than a year of building something nobody needs.

  • #Idea validation
  • #Founders
  • #Startups

FAQ

Questions on this topic

Still unsure? Send a note with your idea and I'll tell you honestly whether I can help.

Ask me directly

It is the one belief that, if wrong, makes the whole idea fail. Typically it is whether a specific customer has the problem badly enough to change behaviour or pay. Test it first, before building.

There is no magic number, but patterns usually appear after 10 to 15 conversations with people from one well-defined segment. Stop when you keep hearing the same pains and workarounds.

Keep reading

AI adoption

AI adoption · 2 min read

Where AI actually pays off for early-stage founders

AI makes small teams faster when it is used in research, building and operations with a clear problem in mind. It does not replace talking to customers or deciding what to build.

Read article

Let's talk

If you are at zero, I am your first call.

Tell me about the idea, the customer and where you are stuck. I will tell you honestly whether I can help, and what the first ninety days should look like.

  • A validated problem, not a guess
  • A launched MVP, faster and cheaper
  • Evidence for customers and investors

Your details are only used to reply to you.