Systematic Approach to Management
The Systematic Approach to Management breaks a large, vague problem into components small enough to actually analyse and act on, instead of managing the whole mess at once.
Picture the messy problem entering on the left and exiting on the right as five distinct, ownable pieces.
Reach for this when…
- A problem is described as 'everything is broken' and nobody can start anywhere.
- Resources keep going to the loudest issue rather than the most important one.
- Progress on a big initiative has stalled because no one owns a specific piece of it.
How to run it
- Name the problem precisely, not as a general complaint.
- Break it into components small enough that one person can own each.
- Analyse each component with actual data, not assumption.
- Set an objective and allocate resource per component.
- Track each component's progress separately, then roll it up.
A worked example
Situation. Robert Mugisha runs a cocoa processing plant in Kampala, Uganda, and had a standing problem on the board simply labelled 'quality issues', unowned for two years.
Applied. He broke it into five components, drying time, storage humidity, transport handling, sorting accuracy and packaging, and assigned each to a named supervisor with its own target.
Result. Three of the five components turned out to be fine. The real problem was storage humidity, fixed within a month once it had a name and an owner.
The catch
Breaking a problem into components can lose the interactions between them, fixing each piece while the combination still fails. It also takes real time up front, which competes badly against the instinct to just act on the loudest symptom. Use it on problems that have resisted a quick fix, not everything that lands on your desk.
If the components do not add back up to the original problem, you have solved five smaller problems and left the real one standing.