Why this matters
If you cannot state the problem in one plain sentence, you do not understand it yet, and everything downstream (interviews, MVP, copy, pricing) inherits that fog. This sentence is the cheapest artifact in your whole startup and the one everything else is checked against.
What "done" looks like
- One sentence, in plain words a stranger understands on first read
- It names WHO has the problem, WHEN it hits, and WHAT it costs
- It contains no solution, no product name, and no buzzwords
- Said aloud to someone who fits the audience, it gets a "yes, that's a thing"
How to do it
- Use the frame: "[Specific person] struggles to [job] when [trigger], which costs them [time/money/risk]."
- Be embarrassingly specific. "Freelance designers lose hours chasing overdue invoices every month" beats "people struggle with payments."
- Strip the solution out. If your sentence contains "an app that…", you are pitching, not describing a problem.
- Test it on five people who match the persona. Watch for recognition, not politeness.
- Rewrite after every learning. The sentence is a living artifact; version it.
Common mistakes
- Describing a market ("productivity is broken") instead of a person's bad afternoon
- Smuggling the solution into the problem statement
- Wordsmithing alone at your desk instead of testing recognition
Real-world examples
- Startup advisors widely recommend stating the problem from the customer's point of view in a single, specific sentence, descriptive without being prescriptive, so it names the pain without smuggling in your solution.
- One well-circulated technique (from a Josh David Miller piece on quick problem statements) is to finish the sentence with "as you can imagine…", e.g. "As you can imagine, it's logistically challenging for restaurants to run their own delivery, especially since they already operate on tight margins", the phrasing forces you to connect the problem to something a listener already accepts as true.
- The one sentence rarely tells the whole story, but it frames everything else. It should flow straight into your unique angle and your value proposition.
From a founder's point of view
If you can't say the problem in one plain sentence, you probably don't understand it yet, and a fuzzy problem produces a fuzzy product. The discipline here is keeping the solution out of the sentence; the moment you write "the problem is that they don't have my app," you've stopped describing a problem and started describing a wish. State the pain in the customer's words and the rest of the plan gets easier to judge.
Rule of thumb
Read it to someone in your target audience: if they do not interrupt you with their own story about it, the sentence, or the problem, is not sharp enough.