andreworia Problem Definition
When to use
Use this when the problem is stated as a symptom ("sales are down"), as a solution in disguise ("we need a rebrand"), or as something too broad to solve ("fix growth"). It is the right skill whenever the team could spend weeks analyzing and still not agree on what question they were answering. Define the problem before scoping any work.
What it does
It converts a fuzzy starting point into a crisp, agreed problem statement using the SCQA structure (Situation, Complication, Question, Answer-space), and it distills the whole engagement down to one key question. That key question is decision-shaped: answering it forces a choice, and it is narrow enough to be answered with evidence. A sharp key question is the single highest-leverage artifact in a strategy project.
Method
The skill runs the SCQA discipline and then pressure-tests the resulting question.
Capture the raw ask verbatim. Write down exactly how the problem was handed over, in the sponsor's own words. This is the thing you will improve, and keeping it visible prevents scope drift later.
Establish the Situation. State the stable, uncontested context that everyone already agrees on. No tension yet, no blame. If a reader would nod along, it belongs in Situation.
Name the Complication. State what changed or what tension makes the situation no longer acceptable. This is the "but" that creates the need to act. Most weak briefs fail here because they never make the complication explicit.
Derive the Question. The Question follows directly from the Complication: given this tension, what must we now decide or resolve? Force it into a single interrogative sentence.
Bound the Answer-space. State the type of answer that would satisfy the sponsor: a go/no-go, a choice among options, a number, a plan. This stops the team from answering a different question than the one asked.
Sharpen the key question against five tests. Rewrite until it passes all five:
- Decision-shaped: answering it changes what someone does.
- Single: it asks one thing, not three joined by "and."
- Scoped: the unit, market, and time horizon are explicit.
- Answerable: evidence could in principle settle it inside the timeframe.
- Neutral: it does not assume the answer or a preferred solution.
Separate the question from sub-questions. Anything that is really a component of the answer is parked. It belongs in the issue tree, not in the key question. The key question stays singular.
Confirm scope boundaries. State explicitly what is in and out of scope, and list the decisions this work will and will not make. Get the sponsor to agree to the one-pager before analysis begins.
Inputs
- The raw ask as it was given, ideally verbatim.
- The sponsor and the decision the work is meant to inform.
- Any known constraints: timeframe, budget, non-negotiables, and what has already been decided.
Output format
A one-page problem statement:
- The raw ask, quoted.
- Situation: the agreed context, two to three sentences.
- Complication: the tension that forces action, one to two sentences.
- Key question: one decision-shaped sentence, in bold.
- Answer-space: the shape of a satisfying answer.
- In scope / out of scope: two short lists.
- Sub-questions parked for the issue tree: a short list.
Example
Raw ask: "Our margins are getting crushed, we need to cut costs."
Situation: The company sells a mid-market hardware product through distributors and has held roughly stable revenue for two years.
Complication: Gross margin has fallen for several consecutive quarters while revenue held flat, so the decline is coming from price or cost, not volume.
Weak question (rejected): "How do we cut costs?" It assumes the answer is cost, it is not decision-shaped beyond "cut," and it ignores price.
Sharpened key question: "Should we defend margin primarily through pricing and mix or through cost, and which specific move recovers the most margin within four quarters without losing share?"
Answer-space: a recommended primary lever plus the two or three specific moves under it, with the margin recovery each is expected to deliver.
In scope: pricing, product mix, and direct cost. Out of scope: acquisitions and a new product line. Parked sub-questions (for the issue tree): which segments are least price-sensitive, where cost is genuinely above benchmark, and how distributors would react to a price move.