Framing the problem and tracing root causes
Step 1 / 4·Problem statements: specific and backed by data
0/4 steps done
Learning objectives — after this module you will:
- Write a clear, data-backed problem statement
- Apply 5 Whys down to the genuine root cause
- Use a fishbone diagram to widen the search
Problem statements: specific and backed by data
Write a problem statement to standard.
A well-framed problem is half solved. A proper problem statement answers: WHAT is happening, WHERE, WHEN, HOW BIG (in numbers), and how large the GAP is versus what you want.
Equally important: a problem statement must NOT contain a cause or a solution. 'People are leaving because pay is low' bakes in an unverified conclusion and locks all subsequent analysis into a single direction.
Two ways to frame a problem
A weak statement
“'Our onboarding has problems, new hires keep leaving because pay isn't competitive.'”
Vague, no numbers, and it bakes in both a cause ('because pay') and an implied solution — closing the analysis before it starts.
A strong statement
“'Over the last 12 months, 8 of 24 new hires (33%) left within 90 days, concentrated in operations. The industry benchmark is under 15%. Gap: 18 percentage points.'”
Specific on scope, time and magnitude; states the gap; and bakes in NO cause — leaving room for honest analysis.
Key takeaway: A problem statement needs what – where – when – how big, and must NOT contain a cause or solution.