Problem statement template

A good problem statement does a lot of quiet, unglamorous work: it keeps your team focused on root causes instead of feature wish lists. This template walks you through building one, step by step.

What is a problem statement template?

It's a fill-in-the-blanks framework for writing clear, evidence-based problem statements. You'll work through the five components that make a statement strong (the problem, who's affected, context, impact, and desired outcome), pick a framework that fits your situation, and stress-test the result before it becomes the foundation for your next roadmap decision.

Who is it for?

This one's for product managers and anyone else who owns discovery, whether you're kicking off a new initiative or trying to bring some rigor to a feature request that showed up without much evidence behind it.

If you've ever watched a team jump straight to "let's build a dashboard" without agreeing on what problem the dashboard solves, this template gives you a way to pump the brakes.

How to use the template

1. Work through the five components first: they're the raw material for everything that follows.
2. Pick whichever framework fits best, whether that's the 5Ws, a business case angle, or Jobs-to-be-Done, and use it to draft your statement.
3. Run it through the solution-bias check to catch any hidden assumptions.
4. Take it to design, engineering, and your most customer-facing colleagues for a gut check.
5. Treat the result as a living document. It should evolve as you learn more, not stay frozen as your first draft.

Get your problem statement template

Problem statement template

Problem statement template Define the problem before you define the solution Drafted by Date Product area Status Draft / validated The five components Work through each row to build the raw material for your statement. Keep answers short and specific. Component Prompt Your…

Google Docs