OUR METHODS
ON THIS PAGE
Business outcome
Performance or opportunity gap
Hypotheses + evidence
Root causes
Organizational choices
Performance gap
A result is below the level the strategy or current commitments require.
For example: customer retention, service reliability or margin is below the required level.
Opportunity gap
The business has identified value it could create but is not yet capturing.
For example: revenue from a new customer segment, income from services or the contribution expected from a new business remains below the required level.
A USEFUL GAP STATEMENT
[Current performance] compared with [required performance] by [time horizon], while preserving [critical condition].
Why precision matters
A vague gap produces a broad diagnosis and familiar solutions. A precise gap establishes what must be explained, sets the boundary of the inquiry and gives leaders a common basis for judging evidence. Discipline at this stage prevents the team from solving a different problem from the one the business faces.
Where are we now?
Use evidence that is specific enough for the leadership team to recognize the same starting point.
What result is required?
State the outcome in business terms rather than naming an organizational solution in advance.
By when?
The time horizon affects which causes are material and which interventions are feasible.
What must be preserved?
Safety, service, customer trust or a distinctive capability may constrain how the organization should change.
Explanation
What might be causing the gap, and through what mechanism?
Evidence for
What would we expect to observe if this explanation were true?
Evidence against
What would cause us to reject or revise the explanation?
ONE POSSIBLE CAUSAL CHAIN
WHY 1
Name the immediate condition producing the result.
WHY 2
Ask what process or decision produces that condition.
WHY 3
Examine the organizational arrangement behind it.
WHY 4
Look at the relationships that sustain the arrangement.
WHY 5
State the mechanism the team is prepared to test.
The fifth answer is not automatically the root cause. The team tests the chain against evidence, looks for rival explanations and revises it when the evidence does not hold.
Stay with observable evidence.
Separate what people have observed from the meaning they have assigned to it.
Keep rival explanations alive.
Ask what else could produce the same pattern and what evidence would distinguish the explanations.
Examine relationships across the system.
Look at how tasks, people, formal organization and culture reinforce one another.
Describe mechanisms rather than blame.
A useful diagnosis distinguishes causes leaders can influence from conditions the organization must accommodate.
Critical tasks
Formal organization
Examine the relationships among the elements.
A small set of tested causal explanations, with evidence for and against each.