Business

Problem Statement Examples (With a Seven-Part Template)

By Business editorial team · Updated

Guide 1, Structured Problem Solving, from The Consultant's Playbook

A good problem statement says what you are solving, why now, what is in and out of scope, and what a good answer looks like, in one page or less. Most weak ones skip at least three of those. This page gives you a seven-part template, five worked examples with invented companies, and the checks that turn a vague request into a question you can finish.

What a problem statement is for

A problem statement is the agreement between you and whoever asked. When a disagreement appears three weeks into the work, it is the page you point to. When a new person joins, it is what they read first. Writing it takes about ten minutes and prevents most scope arguments.

It is not a description of the solution, a history of the issue, or a list of symptoms. It names a question that can be answered with evidence.

The seven-part template

PartQuestion it answers
ContextWhat is the background, in one or two sentences?
TriggerWhat changed that makes this urgent?
Key questionWhat exactly must be answered?
ScopeWhat is in, and what is explicitly out?
Success criteriaWhat does a good-enough answer look like?
ConstraintsWhat are the limits on time, budget, data or access?
Decision ownerWho will use the answer?

Each row prevents a specific kind of trouble. Without a trigger, nobody can judge urgency. Without scope, the work quietly doubles. Without success criteria, you cannot tell when to stop. Without a decision owner, you produce an answer nobody has the authority to act on.

Five problem statement examples

All companies below are fictional.

1. Rising returns at an online bike shop

2. Slow support replies

3. Falling margin at a coffee roaster

4. A staffing-or-booking question

5. A decision with a deadline

How to check your key question

The key question is the part most often written badly. Test it against five letters.

CheckA failing questionA better version
SpecificHow can we improve customer experience?Which three steps in the returns process cause the most customer contacts?
MeasurableWhy is morale low?Which factors do staff cite most often as reasons for leaving?
ActionableWhy is the market changing?Which two market changes should change our pricing this year?
RelevantWhat is the history of our returns policy?Does our returns policy cause the increase in returns?
Time-boundSomeday we should know why.By the March meeting, which causes explain most of the increase?

Also check that the question is a single question. "Why did returns rise and what should we do about our supplier?" is two. Separate them or pick the one you will answer now.

Write success criteria about the answer, not the business

Success criteria describe the quality of your answer. You can promise a ranked list of causes with evidence. You cannot promise that the company's results will improve, because that depends on decisions and events outside your analysis. Imagine the final meeting and ask what the decision owner would need to see for it to go well. That is your success criterion.

Common mistakes

From statement to structure

Once the question is sharp, the next step is to split it into parts you can investigate. The issue tree guide shows how, and the MECE framework explains the rule that keeps the split clean. When the work becomes a formal project, the statement usually becomes a section of the project charter.

Five steps in order: define, structure, hypothesize, analyze and communicate

Use the worksheet

The first guide in The Consultant's Playbook covers exactly this step. It walks through the situation, complication and question, the seven parts above and the SMART test, then applies them in one complete worked case. It includes two printable worksheets, SCQ and Problem Statement and SMART Question Check, so you can fill in your own version rather than copy an example.

Educational content. It is not legal, financial or tax advice.

Frequently asked questions

How long should a problem statement be?

One page at most, and often a short paragraph or a table. If it needs more, you are probably describing the solution or the history instead of the problem.

What is the difference between a problem statement and a project charter?

A problem statement defines the question, its scope and what a good answer looks like. A charter is broader. It adds the team, milestones, governance and sign-off, and it usually contains the problem statement as one section.

Should a problem statement include the solution?

No. It should describe what you are trying to solve and how you will judge an answer. A solution hidden inside the statement closes off options before you have looked at the evidence.

How do I know the key question is good enough?

Run it through five checks: specific, measurable, actionable, relevant and time-bound. If it fails one, rewrite it. A good test is whether you can say what evidence would settle it.