Systems Thinking

29. Mai 2017
Kategorien
Newsletter abonnieren

Sytems Thinking

A silo mentality is the biggest single impediment to achieving true business agility. Everyone involved in the creation and delivery of business solutions needs to collaborate across the breadth and depth of the organizational structure. Team-level agility in the delivery space alone will not deliver on the promise of the Lean enterprise; nor is DevOps enough. Business, IT and operations all need to break out of their silos and embrace Systems Thinking.

When you read about scaling agile you will notice that popular frameworks are using Systems Thinking. For example, one of the principles of LeSS is Systems Thinking (see here) and also SAFe says it is based on a number of newer paradigms in systems and software engineering, including Lean and Systems Thinking (see here).

So what is Systems Thinking? Here’s a definition from Barry Richmond, who coined the term in 1987:

Systems Thinking is the art and science of making reliable inferences about behavior by developing an increasingly deep understanding of underlying structure.

Cultivating this «art and science» leads to routine use of correct mental models that see the world as a complex system whose behavior is controlled by its dynamic structure, which is the way its feedback loops interact to drive the system’s behavior. The term Systems Thinking is preferred to holistic or whole systems, which have looser and more intuitive meanings and emphasize understanding the whole rather than the dynamic structure of the system.

Systems Thinking is not stepping back to look at the whole, the big picture, or a higher level. Nor is it realizing that when a butterfly flaps its wings in one place, that could cause a hurricane far away. This helps, but does not lead to the major insights that emerge when the feedback loop structure of the system becomes visible. When this happens night becomes day. Systems Thinking is the first step to an even higher level: System Dynamics, where instead of just thinking in terms of system structure you model it. See for example this system model from the LeSS website.

Sytem Dynamics Model

 Here is a definition from Peter Senge’s highly influential The Fifth Discipline Fieldbook:

Systems Thinking is a way of thinking about, and a language for describing and understanding, the forces and interrelationships that shape the behavior of systems. This discipline helps us to see how to change systems more effectively, and to act more in tune with the natural processes of the natural and economic world.

Event oriented thinkers and systems thinkers

Everyone in the world can be divided into two groups based on how they see the world around them: event oriented thinkers and system thinkers.

Most people are event oriented. They see the world as a big collection of parts and events. Each event has a cause and if you want to solve a problem, find the cause and fix that. How many root cause analysis you already have been part of? So for example, when applying this mindset to the global environmental sustainability problem, they see people’s misbehavior as the cause of the problem. The solution, then, is to get them to stop behaving so irresponsibly. This can be done with laws stating what to do and not to do, plus emotional appeals to be nice to the environment. When that solution fails, as it has for over 40 years, they just throw up their hands and call it a hard problem.

Systems thinkers see the problem entirely differently. They see immense positive feedback loops causing swarms of agents to exploit the earth for their own benefit and population growth. This mode becomes unsustainable when negative feedback loops finally start to push back as environmental limits are approached. They don’t see people’s misbehavior as the problem. Instead, they see the structure of the system as causing that misbehavior. To solve the problem, system structure must be understood and changed, so that feedback loops can be redesigned to cause people to behave sustainably as a natural part of their everyday existence. This takes far more work than writing a few quick new laws and pleading to save the world.

Defining a system

When defining a system you have to keep in mind the following:
– a system is composed of parts
– a system is other than the sum of its parts
– all the parts of a system must be related (directly or indirectly), else there are really two or more distinct systems
– a system is encapsulated (has a boundary)
– a system can be nested inside another system
– a system can overlap with another system
– a system is bounded in time, but may be intermittently operational
– a system is bounded in space, though the parts are not necessarily co-located
– a system receives input from, and sends output into, the wider Environment
– a system consists of processes that transform inputs into outputs
– a system is autonomous in fulfilling its purpose (a car is not a system. A car with a driver is a system)

Concepts of Systems Thinking

Systems thinking revolves around only a handful of concepts. The key concepts are:

1. All systems are composed of interconnected parts. The connections cause the behavior of one part to affect another. All parts are connected. A change to any part or connection affects the entire system.

2. The structure of a system determines its behavior. Structure is the pattern of part connections, which is how the system is organized. System behavior is at least a thousand times more dependent on connections than parts because that’s what determines how the parts work together. To understand a system’s gross behavior, understand its structure. To change a system’s gross behavior, change its structure.

3. System behavior is an emergent phenomenon. How a system behaves cannot be determined by inspection of its parts and structure. This is because parts are tightly coupled, the parts and structure are constantly changing, feedback loops are present, nonlinear relationships exist, behavior paths are history dependent, the system is self-organizing and adaptive, emergent behavior is counterintuitive, time delays exist, the human mind has very limited calculation abilities, etc. Once you realize how complex the behavior dynamics of even a simple system really is, you will never again assume you can look at a system and predict how it will behave.

4. Feedback loops control a system’s major dynamic behavior. A feedback loop is a series of connections causing output from one part to eventually influence input to that same part. This circular flow results in large amplification, delay, and dampening effects, which is what causes the gross behavior of the system. Every part is involved in one or more feedback loops. Systems have more feedback loops than parts, which causes unimaginable complexity. Feedback loops are the main reason a system’s behavior is emergent.

5. Complex social systems exhibit counter-intuitive behavior. The problems of such systems, therefore, cannot be solved using intuition and our everyday problem-solving methods. The use of intuitive methods to solve difficult complex social system problems is a common trap, so common the entire environmental movement has fallen into it. Only analytical methods using tools that fit the problem will solve difficult complex social system problems. The first such tool to adopt is true systems thinking. The second one is a process that fits the problem. The third one, unless it is an easy
problem, is system dynamics.

Laws of The Fifth Discipline

The Fifth Discipline: The Art and Practice of the Learning Organization is a book by Peter Senge (a senior lecturer at MIT) focusing on group problem solving using the systems thinking method in order to convert companies into learning organizations. The five disciplines represent approaches (theories and methods) for developing three core learning capabilities: fostering aspiration, developing a reflective conversation, and understanding complexity. His 11 laws of the fifth discipline are a nice summary of insights provided by Systems Thinking.

1. Today’s problems come from yesterday’s ‘solutions.’
2. The harder you push, the harder the system pushes back.
3. Behavior will grow worse before it grows better.
4. The easy way out usually leads back in.
5. The cure can be worse than the disease.
6. Faster is slower.
7. Cause and effect are not closely related in time and space.
8. Small changes can produce big results…but the areas of highest leverage are often the least obvious.
9. You can have your cake and eat it too—but not all at once.
10. Dividing an elephant in half does not produce two small elephants.
11. There is no blame.

Further Reading

If you would like to read more about Systems Thinking I would start with the book The Fifth Discipline: The Art and Practice of the Learning Organization, by Peter Senge. Work through to the fifth chapter, titled A Shift of Mind. There Peter does indeed shift the mind with a great introduction to Systems Thinking, one so good the book turned much of the American business world onto systems thinking in the 1990s, when it was first published. In this chapter Peter defines systems thinking as «a discipline for seeing the ’structures‘ that underlie complex situations, and for discerning high from low leverage points.»

And then, if you also want to read about System Dynamics, try John Sterman’s Business Dynamics: Systems Thinking and Modeling for a Complex World. As the title suggests, this will not only turn you into a systems thinker. It will also turn you into a modeler, using system dynamics.

Tags

Das könnte Sie auch interessieren

The Five Elements of a Strong Governance Structure for Critical Projects

16. Januar 2025

Every executive has nightmares about that project—the one that spirals into an unmitigated disaster.  In general there are four ways a project can end up in a boardroom-shaking failure that can destroy value, reputations, and trust in one fell swoop. 1. The Titanic Failure: The project chugs along, oblivious to the iceberg ahead, burning millions

Weiterlesen

Why Every Critical Project Needs Independent Reviews

14. Januar 2025

«Trust, but verify.» That timeless adage applies as much to critical projects as it does to diplomacy. Without an independent review, even the best-run projects can veer off course, leaving organizations blindsided by delays, cost overruns, or outright failures. Here’s the uncomfortable truth: internal stakeholders are often too close to the project to see the

Weiterlesen

Why Every Critical Project Needs an Executive Sponsor

13. Januar 2025

Launching a critical project without an executive sponsor is like sending a ship to sea without a captain—good luck steering through the storm. Projects don’t fail because of bad intentions. They fail because of a lack of alignment, authority, and support.  That’s where the executive sponsor steps in—not just as a figurehead but as the

Weiterlesen

Why Every Critical Project Needs a Dedicated Project Manager

12. Januar 2025

Far too often, organizations assign critical projects to people who already have full-time roles or, worse, delegate management to a loosely organized team with no single point of accountability. The results? Missed deadlines, blown budgets, and a whole lot of finger-pointing. Here’s the hard truth: if the project is important, it deserves a dedicated project

Weiterlesen

Case Study 21: The Australian Securities Exchange (ASX) $250 Million CHESS Blunder

6. Januar 2025

The Australian Securities Exchange (ASX) embarked on an ambitious journey to replace its 25-year-old Clearing House Electronic Subregister System (CHESS) with a state-of-the-art, blockchain-based platform.  Initially envisioned as a groundbreaking project to enhance efficiency, security, and scalability, the CHESS replacement project quickly turned into a cautionary tale.  The initiative faced repeated delays and escalating costs

Weiterlesen

Project Recovery

2. Januar 2025

  Projects fail for a variety of reasons. Especially technology projects have a low success rate. Typically more than half of them are considered a failure. If your current in-house or outsourced software or web development project is off track, chances are I can bring the necessary input and expertise to get the job done. Troubled projects

Weiterlesen

When $100 Million Technology Projects Fail, It’s the Board’s Fault—Every Single Time

2. Januar 2025

In Switzerland, rumors suggest that both Bank Julius Bär and Raiffeisen Schweiz are grappling with failed technology projects, each costing over $100 million so far. Bank Julius Bär is reportedly trying to replace its existing core banking system for the Swiss booking center with Temenos, while Raiffeisen Schweiz is attempting to build a modern e-banking

Weiterlesen

10 Essential Questions Every Board Should Ask About Technology

16. Dezember 2024

Board members play an important role in steering organizations through the complexities of technology initiatives.  To fulfil this role effectively, it’s essential to ask the right questions that probe the strategic, operational, and risk aspects of technology projects.  Here are ten critical questions every board should consider: 1) How does this technology initiative align with

Weiterlesen

Independent Board Advisory

16. Dezember 2024

Effective boards provide clarity, governance, and oversight to steer organizations toward success. However, large technology initiatives, digital transformations, and innovation efforts often challenge even the most seasoned boards.  My Board Advisory service empowers boards and board members to navigate the complexities of modern technology decisions with confidence and precision. As a trusted advisor and experienced

Weiterlesen

Case Study 20: The $4 Billion AI Failure of IBM Watson for Oncology

7. Dezember 2024

In 2011, IBM’s Watson took the world by storm when it won the television game show Jeopardy!, showcasing the power of artificial intelligence (AI). Emboldened by this success, IBM sought to extend Watson’s capabilities beyond trivia to address real-world challenges.    Healthcare, with its complex data and critical decision-making needs, became a primary focus. Among

Weiterlesen
Next