Experienced people solve the wrong problems all the time.

Not because they lack intelligence or commitment, but because they are focussed on the behaviour they see looking at the visible event rather than the underlying system producing it. A team misses a deadline, so the response is tighter project management. Customer complaints increase, so the response is more training. Employee engagement drops, so the response is a new survey, a manager briefing, or another internal campaign.

Sometimes those actions help. Often they do not. Sometimes they a solution that seems to work initially, can have significant unintended negative consequences down the road. The same patterns comes back because the underlying system has not changed. Systems thinking is useful because it helps people look beyond the obvious causes and symptoms and ask a better question: what relationships, incentives, behaviours and feedback loops are producing this result?

What is systems thinking?

Systems thinking is a way of understanding problems by looking at the whole system, in all of its complexity; not just the individual parts. A system is made up of elements that interact with each other. In an organisation, those elements might include people, teams, processes, policies, culture, technology, incentives, leadership behaviour, customer expectations and market pressures.

None of these things operates in isolation. They influence each other constantly. That is why behaviour in a system often emerges from relationships, not from the parts themselves.

Donella Meadows, author of Thinking in Systems, remains one of the clearest voices on this subject. Her work helped make systems thinking practical by showing that systems are shaped by structure, feedback and purpose. In simple terms, if you want to understand why something keeps happening, you need to understand the system that keeps producing it.

This is the difference between asking, “Who caused this?” and asking, “What conditions made this likely?” That shift matters. It moves the conversation away from blame and towards understanding. It also gives people a better chance of positively influencing system behaviour. making changes that last.

A systems thinking approach does not mean trying to map everything. That can become overwhelming and unhelpful. It means paying attention to the relationships that matter most, the patterns that repeat, and the points where change might have a wider effect.

Why linear thinking falls short

Linear (reductive) thinking is useful when the relationship between cause and effect is clear. If a machine breaks because one part has failed, replace the part. If a form is missing a required field, add the field. If a process has five steps and one is duplicated, remove the duplication. These can be are complicated problems, but they are not necessarily complex.

Organisational life is different. Imagine a leadership team that keeps making the same decisions and getting the same results. They want more innovation, but every new idea has to pass through layers of approval. They want people to speak up, but managers respond defensively when challenged. They want faster delivery, but every team is measured on avoiding risk rather than learning quickly.

On the surface, the problem might look like a lack of creativity, confidence or capability. The obvious response might be innovation training, communication workshops, or a new leadership message. But the system is saying something else.

The behaviour is not random. It is being produced by the way authority, incentives, trust and decision-making interact. People are behaving sensibly within the conditions around them. If those conditions do not change, the behaviour is likely to continue.

The core elements of a systems thinking approach

The first element is the feedback loop. A feedback loop happens when an action produces a result that then influences future action. Some feedback loops reinforce a pattern. Others balance or stabilise it. A manager who does not trust the team becomes more involved in decisions. The team then waits for approval more often. The manager sees this as evidence that the team lacks ownership, so they become even more involved. The loop reinforces itself.

The second element is stocks and flows. A stock is something that builds up or reduces over time. A flow is what increases or decreases it. In organisations, trust can be thought of as a stock. So can capability, morale, technical debt, customer confidence or leadership credibility. Trust usually disappears over time because repeated behaviours deplete it. It is also built over time through consistent action.

The third element is emergence. Emergence means that a system produces outcomes that cannot be fully explained by looking at each part separately. A team culture is a good example. You can interview every individual and still not fully understand how the team behaves together. The culture emerges from relationships, habits, norms, history, power and repeated interactions.

The fourth element is interconnection. In a system, changing one thing often affects something else. A new performance measure might improve short-term productivity while damaging collaboration. A new approval process might reduce risk while slowing innovation. A restructuring might create clarity in one area and confusion in another.

Where systems thinking gets applied

Systems thinking is useful wherever the problem involves multiple people, competing pressures and unclear cause and effect. In short, when it is complex. In organisational strategy, it helps leaders understand the conditions that will support or block a strategic ambition. A strategy does not succeed because it is well written. It succeeds when the surrounding system makes the right behaviours possible.

In leadership development, systems thinking helps leaders see that their behaviour is part of a wider pattern. A leader might want more accountability, but if the system punishes honest mistakes, people will avoid ownership. A leadership workshop that ignores the system may produce insight, but not much change.

In facilitation and workshop design, systems thinking helps groups make sense of complex situations together. The facilitator’s role is not to force a quick answer, but to help the group see the relationships between the parts. This is particularly important when people hold different pieces of the truth. That is why facilitation techniques for complex group work need to be chosen with care.

In complex problem-solving, systems thinking gives teams a way to avoid shallow fixes. Instead of asking only what action to take, they can ask what is driving the current pattern, what might change if they intervene, and where the system has the greatest potential for movement. If you are exploring that distinction, it is worth reading more about how the Cynefin Framework approaches sense-making in complex systems.

Systems thinking in practice: one tool worth knowing

There are many tools for systems thinking. Some are visual. Some are analytical. Some are conversational. The right tool depends on the group, the problem and the level of complexity involved.

One practical method we use is LEGO Serious Play Build Level 3. This is not about using LEGO bricks as a gimmick. At Build Level 3, participants build a shared system model. They identify the elements in the system, explore the relationships between them, and test how the system responds when something changes. The model sits in the middle of the room, which means the group can work with the system physically rather than only talk about it.

That makes a difference. People can point to relationships, move elements, question assumptions and see patterns that are difficult to capture in normal discussion. It also gives every participant a route into the conversation, not only the most confident or analytical voices. We have written separately about LEGO Serious Play as a systems thinking tool for those who want to understand how Build Level 3 works in more depth.

This cluster also goes further into feedback loops, systems thinking in organisations, how systems thinking compares to design thinking and leverage points. Each article looks at a different part of the same question: how do we understand complex systems well enough to act with more care?

FAQ

What is the difference between systems thinking and analytical thinking?

Analytical thinking breaks something down into parts so each part can be examined. That is useful when the problem can be understood through separation. Systems thinking looks at how the parts relate to each other. It is useful when the behaviour of the whole system cannot be explained by looking at each part in isolation.

What is systems thinking used for in organisations?

Systems thinking is used to understand complex organisational problems where simple cause and effect is not enough. This might include culture change, employee engagement, leadership behaviour, customer experience, service delivery, strategy execution or cross-functional collaboration.

Is systems thinking a methodology or a mindset?

It is both. As a mindset, systems thinking means being curious about relationships, patterns and consequences. As a methodology, it includes practical tools such as system maps, feedback loop diagrams, causal loop models, scenario testing and facilitated system modelling.

What is a simple example of systems thinking?

A simple example is staff turnover. A linear view might say, “People are leaving because pay is too low.” That may be true, but it may not be the whole system. A systems thinking approach would also look at workload, management behaviour, progression, recognition, hiring patterns, team culture, burnout, communication and trust – along with the factors influencing staff pay.

Systems thinking is useful because organisations are rarely as simple as their charts, plans and dashboards suggest. Most recurring problems are not caused by one broken part. They are produced by relationships between parts. Once people see that, they can stop chasing the same symptoms and start working with the system that creates them.