5 Ws Problem Framing Framework
Type: template
Stage: Stage 1: Problem Proof
Difficulty: beginner
A methodical breakdown that forces you to define the unmet need clearly — moving from a vague idea to a specific, testable problem statement using Who, What, When, Where, and Why.
Overview
Most early-stage founders can describe their idea but not their problem. The 5 Ws framework fixes this by forcing a structured answer to five specific questions — producing a one-paragraph problem statement that is testable, focused, and free of solution language.
The five questions
• Who has this problem? Define the specific person, role, or context — not a broad demographic. 'Freelance graphic designers who work with multiple clients' is a who. 'Small business owners' is not specific enough.
• What is the problem, exactly? Describe it in behavioral terms. What does the person do, fail to do, or have to do manually because the problem isn't solved?
• When does it occur? Identify the specific moment or trigger. Problems that happen rarely are harder to build businesses around than problems that happen on a regular cadence.
• Where does it occur? What context, platform, environment, or workflow is involved? Location shapes the solution.
• Why does it matter? What is the cost — in time, money, stress, or missed opportunity — when the problem isn't solved?
How to use it
Fill in each of the five questions independently, then combine your answers into a single problem statement paragraph.
The format: '[Who] struggles with [What] when [When] because [Why], and current solutions fail because [gap in the market].'
Example: 'Freelance graphic designers struggle to track client revision requests when a project is in progress because feedback arrives across email, Slack, and WhatsApp simultaneously. Current tools require clients to log in to a separate platform, which most don't do.'
If you can't write a clear sentence for each W, you don't yet understand the problem well enough. The gaps in your answers tell you what to research next.
Testing your problem statement
Once written, test your problem statement with two questions:
1. Could someone read this and immediately identify whether they are the person with the problem? If yes, it's specific enough.
2. Does it describe the problem without mentioning your solution? If you've snuck the solution into the statement, rewrite it.
A well-formed problem statement is the input for your interview guide, your positioning work, and your evidence threshold. It also serves as the clearest check on whether your research is confirming or disconfirming what you thought you knew.
Common mistakes
• Answering 'Who' too broadly — 'entrepreneurs' or 'students' are not audiences, they're categories
• Conflating the problem with the solution in the 'What' answer
• Skipping 'When' — the timing of a problem shapes its urgency and the appropriate solution type
• Writing 'Why it matters' in terms of market size instead of individual cost — the individual cost is what drives behavior change