Instructions
A problem statement is the short, sharp paragraph that captures the essence of what you're solving and for whom.
It doesn't describe your product. It doesn't list features. It describes the user, the situation, and the gap that creates an opportunity. Done well, it becomes the anchor for almost everything that follows — research priorities, design decisions, validation experiments, even copy on your eventual landing page.
If you can't write a clear problem statement, the rest of the work tends to drift. The act of writing it forces the clarity that vague thinking can otherwise avoid.
What to aim for
A problem statement of two to four sentences. Specific. Honest. Anchored in real users. Free of jargon. Something you could read aloud to a stranger and have them roughly understan...
