There's a story engineers love to tell.
A man installed a new, expensive pump on his farm. Next week it jammed. He bought a second pump — jammed again. He blamed the pump supplier, then his workers, then "bad luck." Nobody looked at the water the pump was pulling from. It was silt-heavy, and silt kills pumps.
The problem was never the pumps. It was the system the pumps sat inside.
That's systems thinking in one story: stop blaming single parts, and look at how the parts interact.
Why your brain default is "single cause"
Our brains want simple stories. So does the internet. "The problem is corrupt officials." "The problem is that app." "The problem is my boss."
All of these are true in a tiny way — and dangerous in a big one, because a system caused the situation, and blaming one part never fixes the system.
Examples everywhere in Ghana:
- A trader who keeps "losing money" — it's not one bad decision; it's a loop of unmeasured stock, credit to friends, and week-end price dips.
- A disorganised meeting — it's not a bad leader; it's unclear roles, no agenda, and phone distractions all feeding each other.
- An "expensive" food market — the high price isn't one greedy seller; it's transport costs, storage losses, and middlemen stacked end to end.
See how the story gains power? The person who sees the loop controls the loop.
The 3 habits that build a systems lens
You don't need engineering diagrams. You need three habits.
1. Ask "what feeds this?"
Every situation has inputs. Before you judge an outcome, ask: what feeds this? A student "not serious" might be feeding on: home noise, no quiet space, a phone that never sleeps, and no sleep schedule. Change what feeds the behaviour and the behaviour changes — often without lectures.
2. Look for loops, not just events
An event is "prices went up today." A system is "prices rise → buyers buy less → sellers raise price to keep their margin → prices rise more." That's a loop. Spot one loop and you've spotted the real machinery.
3. Find the pressure point (leverage)
Systems have places where a small change makes a big difference. A trader whose stock is unmeasured: the pressure point isn't "work harder" — it's "write every purchase down for two weeks." One tiny practice, huge effect. Leverage is almost always in the everyday bottleneck, not the dramatic role.
The "five whys" in 2 minutes
Here's a practical drill you can run alone or with friends:
- Start with the problem: "Sales dropped."
- Ask why. Get an answer. "Because we ran out of stock."
- Ask why again. "Because we over-bought one item."
- Again. "Because we estimated demand by guessing, not records."
- Again. "Because there's no simple sales log."
- Again. "Because nobody owns the log — it's everyone's job and no one's job."
By the 5th "why," you're at a system my cause (missing ownership) instead of a one-off event. That's where real fixes live.
Traps that undo systems thinking
- Trap: "It's too complex, forget it." Start small — one loop, one pressure point, one habit.
- Trap: analysis paralysis. Systems thinking is a tool to act, not an excuse to postpone. Find the deepest cause you can actually nudge, and nudge it.
- Trap: forgetting the human. Systems are run by people with feelings. A good mechanic fixes the pump — and pays the workers fairly. Don't let "it's the system" become cold.
Practise it with real problems
The best classroom for systems thinking is a real project with a deadline — a big clean-up, a hackathon challenge, a volunteer drive. That's why KlagonOrg runs hands-on community projects: they force you to see the whole system — people, supplies, timing, communication — instead of just your own part.
You can also sharpen it through the Leadership Foundations course, which covers structured problem-solving and clear thinking.
Call it what you will: perspective, insight, seeing the bigger picture. It's the skill of noticing the connections that everyone else walks past.
Look beyond the pump. Find the silt. Fix the water — and the whole farm changes.