Systems Thinking

Systems thinking moved from engineering into management through Peter Senge

The roots are in system dynamics, which Jay Forrester developed at MIT to model how feedback and delays drive the behaviour of complex organisations. Donella Meadows later made the ideas accessible in Thinking in Systems.

Peter Senge brought systems thinking to a management audience in The Fifth Discipline (1990). He called it the discipline that integrates the other four he described: personal mastery, mental models, shared vision and team learning. His point was that organisations struggle to learn when people see only their own part of the system.

Leaders use systems thinking to stop solving the same problem twice

In practice, systems thinking is a set of questions you ask before you act, especially when a problem has come back for the third time.

• ✦What pattern is this event part of? One late project is an event; late projects every quarter are a pattern.
• ✦What structure rewards this behaviour? Incentives, reporting lines and targets often explain more than personalities do.
• ✦Where are the delays? Actions taken today may only show results months later, which tempts leaders to overcorrect.
• ✦Who sits outside my org chart but inside the system? Customers, regulators and other departments often hold the key.
• ✦Where is the leverage? A small change in a rule or a meeting can matter more than a big programme.

A hypothetical example: the sales target that created a service backlog

Imagine a retail bank in the Gulf where the sales team is rewarded for opening new accounts. Sales rise, the onboarding team falls behind, complaints grow and the executive team decides the onboarding manager is the problem. A replacement arrives and the same backlog returns within months.

A systems view looks at the loop instead of the person: the incentive that speeds up sales has no link to onboarding capacity. Once the two teams share a target, the pressure changes shape. The guide on how to break down silos between departments covers the practical side of that conversation.

Systems thinking has limits when it becomes an excuse

Systems thinking can turn into endless mapping with no decision at the end. It can also dissolve accountability, where every failure is blamed on "the system" and nobody owns their part of it. A good systems thinker holds both: the structure shapes behaviour, and each person still chooses how to act within it.

The iceberg model is a simple tool for moving from events to the structures and beliefs beneath them. In coaching, the same lens becomes systemic coaching, which treats a leader or team as part of a wider set of relationships. I hold certifications in Systemic Coaching and Systemic Team Coaching, and with leadership teams this often becomes systemic team coaching.