Systems Thinking
Seeing patterns where simple explanations fail
I often wonder why systems thinking isn’t taught to all of us at school.
It deals with complexity — and today, almost everything we encounter is complex. From our personal lives and relationships to large issues such as poverty, immigration, or environmental pollution, simple cause-and-effect explanations rarely hold.
I always raise my ears when I hear someone mention a systems approach or systems thinking. For me, those words signal something important: an understanding that problems are rarely isolated, that causes overlap, and that outcomes often take time to show up. It gives me an extra degree of confidence that this person — or organisation — might be equipped to deal with the issue at hand. Still, I hear it far less often than I expect.
Some years ago, while interviewing a therapist to help me navigate a particular issue, she mentioned systems thinking almost in passing. I trusted her immediately — not because she offered answers, but because she recognised how intertwined personal history, relationships, habits, and external pressures can be. When complexity is ignored, problems feel impossible. When it’s acknowledged, at least we’re no longer guessing blindly.
I’m reminded of a university professor who used to warn us during exams: don’t rush to write your answers yet. Most of the time, she said, should be spent reading and understanding the question. The problems were long and detailed — describing a situation, a system. Without understanding it properly, mistakes were almost guaranteed. The answers themselves were often brief: a few equations, clearly stating assumptions and limits.
I studied industrial engineering, where the idea of a system was everywhere. We were taught ways to understand complexity — not to eliminate it, but to work with it. Over time, I’ve found myself wondering how these ideas might be simplified and made useful outside engineering classrooms.
This post is an attempt to do that.
Linear Thinking vs Systems Thinking
Most of us are trained in linear thinking.
Something goes wrong. We look for the cause. We fix it. Problem solved.
This works well for simple problems — fixing a leaking tap, following a recipe, solving a maths equation with known variables.
But many problems don’t behave that way.
Systems thinking starts with a different assumption: that causes are often multiple, effects are delayed, and fixing one thing can change the whole situation — sometimes in unexpected ways.
In a linear frame, traffic congestion is caused by too many cars, so more roads seem like the answer. In practice, more roads often lead to more traffic.
In a linear frame, feeling stuck is treated as a motivation problem. In a systems frame, it may be the result of routines, expectations, habits, and risk avoidance each reinforcing one another.
Linear thinking asks: What went wrong?
Systems thinking asks: What keeps happening — and why does this pattern hold?
That difference matters. Linear fixes often feel good quickly, but wear off. Systems thinking trades speed for understanding — and usually gains durability in return.
The Seduction of Quick Fixes
One reason linear thinking is so appealing is that quick fixes often work — briefly.
Coffee for fatigue.
Sugar for low energy.
Nicotine for stress.
Alcohol for social ease or emotional relief.
Each provides fast feedback. The system responds immediately.
From a linear point of view, this looks like success:
tired → coffee → alert
anxious → drink → relaxed
Problem solved.
From a systems point of view, these are short-term relief mechanisms. They don’t change what produced the fatigue or stress in the first place. In some cases, they reinforce it.
Coffee hides sleep debt.
Sugar sharpens energy swings.
Alcohol smooths discomfort while reducing resilience.
What makes quick fixes attractive is speed. Structural change is slow.
Quick fixes keep the system running — just not well. They are useful signals, though. They point directly to where change might actually matter. And they remind us of something important: when you remove a quick fix, things usually feel worse before they feel better. That’s not failure — it’s exposure.
Five Practical Ways to Use Systems Thinking
1. Notice patterns before reacting to events
If something keeps happening, it’s unlikely to be an accident.
Traffic congestion that returns every year.
The same disagreement with a friend.
The familiar feeling of being stuck.
The mistake is reacting to each episode rather than asking what keeps producing it.
Try this
Instead of asking why did this happen again?, ask:
What conditions make this likely to happen at all?
Small changes start there.
2. Change one condition, not everything
Big redesigns rarely work. Small shifts often do.
Plastic waste reduced more effectively when responsibility shifted to producers than when consumers were told to try harder. Relationships often improve through one consistent boundary rather than repeated serious conversations.
This idea is central to the work of Donella Meadows, who showed that modest structural changes often outperform grand plans.
Try this
Identify one rule, expectation, or default that quietly shapes behaviour — and adjust that.
3. Expect delays — and don’t judge change too early
Many changes fail because they are evaluated too soon.
Public transport takes years to alter commuting habits. Clearer boundaries can make relationships feel tense before they feel stable.
Early discomfort is not always a sign something is wrong.
Try this
Once you make a change, hold it steady long enough for the system to respond.
4. Pay attention to what you’re measuring
Systems tend to optimise for what gets noticed.
Energy use drops when people can see real-time consumption. Personal momentum improves when attention shifts from approval or outcomes to effort and learning.
Nothing else changes — just visibility.
Try this
Notice what you reward, track, or dwell on. Small shifts in attention can change behaviour over time.
5. Reduce friction before applying pressure
Most systems don’t fail because of laziness. They fail because of friction.
Voting increases when processes are simpler. Repeated personal conflict often eases when timing or setting changes — not arguments.
Pressure exhausts. Friction reduction restores flow.
Try this
Ask: What is making the right action harder than it needs to be? Remove one obstacle.
A closing thought
You don’t need to change the whole system.
You need to understand which small part is holding it in place — and allow time for it to move.
That, to me, is the quiet usefulness of systems thinking. And why I still wish more of us learned it earlier.
This is a very clear explanation of the idea and how to apply it. I’ll share it with others who might find it useful to help them encourage others to improve complex systems
I really liked this Hurol and think it is very useful to see the small elements in a whole (marriage, health, work patterns) and I found this really pertinent to me right now. Yes, good phrase Christopher, broad and deep thinking we all need to do!