Write problems so your team can choose where to play and how to win.
A fuzzy problem statement makes everyone busy. A clear one makes everyone decide.
A CEO once opened a meeting with: “We need to improve customer experience.” The team agreed right away. Then everyone offered fixes—training, new tools, new dashboards, new rules. The meeting felt productive, so they moved on.
Two weeks later, the same complaints came back. The team did not fail because they lacked effort. They failed because the problem stayed blurry. When the problem is blurry, every solution feels “right,” and the team avoids the hard work of choosing.
What a problem statement is (so we mean the same thing)
Most people say a problem statement is a short description of what is wrong and why it matters. That is true. Leaders use it in memos, decks, and kickoff meetings to explain why work needs to happen.
Strategic thinkers use it for something bigger. They use it as a decision trigger. A good problem statement describes reality so clearly that the next decision becomes easier to see.
If your problem statement does not help people choose, it will not help people win.
The Play to Win bridge that most teams forget
Strategy is not a long plan.
Strategy is a set of choices.
When you use the Playing to Win approach, you focus on two big choices:
- Where to play: which customers, markets, channels, or arenas you will focus on
- How to win: what advantage you will build in that arena
A strong problem statement should point to one of these choices. If it does not, your team will likely “fix things” without changing the game.
Why common problem statements fail
People often say:
“Sales is slow.”
“Marketing isn’t working.”
“Execution is weak.”
“Customers are unhappy.”
These statements may be true, but they do not guide action. They invite people to argue about solutions. Each leader brings a favorite fix, and the meeting turns into a menu of ideas.
When leaders cannot decide, they usually do not have an “ideas problem.” They have a “problem statement problem.”
A short story: the “execution problem” that wasn’t execution
A COO once said, “Execution is weak.” Everyone agreed, but everyone meant something different. One person blamed the team. Another blamed the tools. Another blamed the workload.
We slowed down and looked for the pattern. The problem showed up in one place: onboarding. Clients changed requirements mid-week. No one had the authority to stop the changes. The team kept missing deadlines, and everyone felt stressed.
The COO did not have an execution problem. He had an intake and scope-control problem. Once the team named it, they stopped blaming people and started choosing a better system.
The 5D Problem Statement Upgrade Script
You do not need a long checklist.
You need a simple script you can reuse in every meeting.
D1 — Dump the raw line
Start with the plain sentence people say out loud.
“Sales is slow.”
“Customers complain.”
“We miss deadlines.”
“Growth is flat.”
This line is not your final statement. It is your starting point.
D2 — Define the arena
Ask: “Where exactly is this happening?”
Name the segment, channel, region, product, team, or part of the customer journey. This step makes the problem smaller and clearer.
D3 — Describe the damage
Ask: “What is the cost if we do nothing?”
Pick one number. Use revenue, churn, cycle time, refunds, errors, overtime, or escalations. One number is enough to focus attention.
D4 — Draft the driver
Ask: “What do we think is causing this?”
State it as a guess, not a verdict. Say, “We believe the driver is…” This keeps people curious and honest.
D5 — Decide the choice
Ask: “What choice does this problem force?”
End with one of these:
- “This forces a choice about where to play.”
- “This forces a choice about how to win.”
- “This forces a choice about the capability we must build.”
This step turns a complaint into a strategy conversation.
Copy-paste template
Use this in your notes, your agenda, or your next memo.
Because [what changed],
[who] cannot [do what] in [arena],
so [measurable damage] is happening.
We believe the main driver is [hypothesis].
This forces a choice about [where to play / how to win / capability].
Example 1: Where to play
Raw line: “Sales is slow.”
Upgraded problem statement:
Because we target too many buyer types at the same time, our sales team cannot build a repeatable pitch for mid-market buyers, so pipeline coverage dropped from 3.0x to 1.7x this quarter. We believe the driver is unclear focus on a single buyer segment. This forces a choice about where to play: commit to one priority segment for the next two quarters, or build two separate plays with different offers, messaging, and targets.
Notice what changed. The team no longer debates effort. The team debates focus.
Example 2: Where to play (growth)
A CEO says, “We need growth.” A leader replies, “We can sell to everyone.” Then the company spreads its time across many small campaigns and never wins big anywhere.
Upgraded problem statement:
Because we spread our growth bets across too many segments, teams cannot build depth in any one market, so results spike and then fade each month. We believe the driver is a missing decision on our priority segment. This forces a choice about where to play: double down on one core segment for the next two quarters, or invest in two separate segments with separate teams, offers, and scorecards.
Example 3: How to win
A leader says, “Customers are unhappy.” People suggest training, automation, or new tools. Those ideas can help, but first the team must choose what “winning” looks like in service.
Upgraded problem statement:
Because customers experience slow responses during escalations, complaints increased and refunds rose this month. We believe the driver is unclear ownership and no simple escalation routine. This forces a choice about how to win: win on speed and reliability with strict response standards, or win on premium care with fewer customers and higher-touch service.
Now the team can design the right solution for the kind of win they want.
How to teach this in 7 minutes
Pick one issue from your next meeting.
Ask five questions in order:
- What is the raw issue in one sentence?
- Where exactly does it show up?
- What is one number that shows the damage?
- What do we believe drives it?
- What choice does it force—where to play or how to win?
Rewrite the statement as a group. Then move to decisions.
One-minute recap
A problem statement becomes strategic when it forces a choice.
Most people write problem statements to describe pain. Strategic thinkers write them to guide decisions about where to play and how to win.
Use the 5D script. End with the choice.
Your next step
Take one issue you plan to discuss this week.
Write it using the template.
If you cannot finish the sentence “This forces a choice about…,” keep rewriting. That is your signal that you still have fog.
When you remove the fog, your team can choose. When your team can choose, your strategy can win.
