Systematic Analysis
Systematic Analysis is the discipline of examining your organisation's internal and external factors in a fixed order, rather than jumping straight to conclusions, so the decision that follows rests on ground everyone actually looked at.
Numbered steps line up in a fixed order, each one building on the last before any conclusion.
Reach for this when…
- A decision keeps getting made on whoever spoke last in the meeting.
- You have data scattered across departments and no shared read of what it means.
- You need a defensible basis for a decision the board will question.
How to run it
- Gather the relevant data before anyone states a conclusion.
- Examine internal factors: resources, capability, performance.
- Examine external factors: market, competitors, regulation.
- Look for patterns and relationships across both, not each in isolation.
- Write the conclusion only after the analysis, not before it.
A worked example
Situation. Jean-Paul Uwimana runs a small electronics components plant in Kigali, Rwanda, and had watched three straight quarters of falling margin blamed on 'the market' in every meeting.
Applied. He ran a systematic analysis, internal first, yield rates and machine downtime, then external, a competitor's new pricing and a currency shift, before letting anyone conclude anything.
Result. The real driver turned out to be internal: unscheduled downtime on one production line, not the market at all. Fixing the line recovered most of the margin.
The catch
The structure can become a ritual that delays an obvious decision while data gets gathered nobody will actually use. It also assumes the data available is the data that matters, which sends analysis down whatever path is easiest to measure rather than most relevant. Use it when the conclusion is genuinely contested, not as a formality before decisions everyone already agrees on.
If the conclusion was obvious before you started, the analysis is theatre. Save it for the decisions people actually disagree about.