Think Better · Tool

Problem Framer

Turn a messy problem into one clear question you can actually answer. Answer five short steps. Get a sharp problem statement you can share with your team.

Time
5 min
You'll leave with
One clear key question
Status
Free · No sign-up
Your problem 0 of 5 steps
1

Get it out of your head

Write the problem the way you'd describe it to a friend. Messy is fine.

2

What's going on?

Separate the facts from the change. This is where most confusion hides.

What's true today? Stick to facts everyone would agree with.
What changed, or why does this need attention now?
3

What does good look like?

Describe the outcome, not the fix. Add a number and a date.

The result you want. Avoid naming a solution like “build an app” or “hire someone”.
4

Who and what's involved?

Name the decision owner, and draw a line around the problem.

What are you deliberately NOT solving? One per line.
5

Your key question

We draft it from your answers. Edit it until it sounds right.

How the Problem Framer works

Consultants spend a surprising amount of time on the first step of any project: agreeing exactly what problem they're solving. It feels slow. It saves weeks.

Why framing matters

Most stuck problems aren't hard. They're vague. Different people are solving slightly different problems, so every discussion goes in circles. A clear frame gets everyone answering the same question.

Situation, complication, question

A simple and widely used way to frame a problem is to split it into three parts:

  • Situation: the stable facts. What's true today?
  • Complication: what changed, or why it matters now.
  • Question: the one thing you need to answer as a result.

Steps 2 and 5 of the tool follow this structure. Steps 3 and 4 add what makes a question answerable: a measurable goal, a deadline, an owner and clear limits.

What a good key question looks like

A good key question is specific, measurable, time-bound, owned, scoped and solution-free. The checklist next to your result tests for each one.

Weak: “How do we fix customer satisfaction?”

Strong: “How can we get customer satisfaction back above 80% by the end of June, given no extra headcount?”

Common mistakes

  • Hiding a solution in the question. “How do we roll out a new CRM?” assumes the CRM is the answer. Ask about the outcome instead.
  • Too broad. “How do we grow?” can't be answered in a meeting, or a quarter.
  • No owner. If nobody decides, nothing gets decided.
  • No limits. Without an “out of scope” list, the problem quietly doubles in size.

What to do next

Framing is the first stage of Futureback problem solving: frame, structure, hypothesise, prioritise, analyse, recommend. Once your question is clear, break it into parts with an issue tree, form a best guess at the answer, then focus your analysis on what matters most.

See the full problem-solving process · Read about the Think Better skill