Chapter 4: Systems Thinking

Learning Objectives

By the end of this chapter, you should be able to:

recognise relationships between different parts of a business problem

distinguish symptoms from root causes

identify unintended consequences

understand how decisions in one area can affect another

recognise feedback loops and reinforcing or balancing relationships

consider the broader system when developing recommendations

Why This Matters

Business problems rarely exist in isolation. A decline in sales may appear to be a marketing problem. But perhaps the real issue is product quality, customer service, pricing, distribution, or a competitor's new offering, or a combination of several factors. Organisations are systems.

Customers, employees, suppliers, competitors, technology, finances, operations, and leadership all interact.

When you change one part of the system, you can create consequences somewhere else. That is why a recommendation that looks excellent in isolation can sometimes create a new problem. Systems thinking helps you see the connections.

Discover Your Mad Skills Principle

Don’t just look at the problem. Look at the system that created the problem.

A strong case solver asks: "What is causing this?" A systems thinker goes one step further: "What relationships are causing this, and what will happen when we intervene?"

Deciphering Case Characteristics

Systems thinking becomes particularly important when:

multiple stakeholders are involved;

problems have several interacting causes;

changing one variable affects another;

the organisation operates in a complex environment;

the case involves sustainability;

implementation creates significant downstream consequences.

A simple problem may not require a complex systems analysis. But when the case contains interconnected problems, treating each issue independently can lead you in the wrong direction.

Understanding Systems Thinking

A system contains:

Elements: The individual parts.

Relationships: How the parts interact.

Purpose: What the system is trying to accomplish.

Consider a restaurant. Its elements might include:

customers;

employees;

kitchen;

suppliers;

technology;

pricing;

management.

But simply listing those elements doesn't help you understand the system. You need to understand their relationships. For example:

Higher demand à Longer wait times à Lower customer satisfaction à Lower repeat visits à Lower revenue

The system creates a feedback loop.

From Symptoms to Root Causes

One of the most useful applications of systems thinking is understanding the difference between a symptom and a cause. Suppose a company has declining profitability. Possible symptoms include:

lower revenue;

higher costs;

declining margins;

customer churn.

But these may be consequences rather than root causes. Ask: Why is this happening? Then ask again: Why? This simple process can reveal relationships that aren't obvious at first.

The Systems Map

A simple systems map can help your team visualise:

Cause → Effect → Consequence

For example:

Understaffing à Longer customer wait times à Customer dissatisfaction à Lower retention à Lower revenue à Reduced ability to hire à Understaffing

The final relationship brings you back to the beginning. You now have a reinforcing cycle.

Coach's Lens

One of the most common mistakes I see in case-solving competitions is teams identifying several problems and then creating a single solution for each.

Problem: Customers are leaving.

Solution: Improve customer service.

Problem: Costs are increasing.

Solution: Reduce costs.

Problem: Employee morale is declining.

Solution: Improve employee engagement.

The problem is that these may not be three independent problems. There may be three symptoms of the same underlying system. Your job is not to solve every symptom separately; it is to understand the system well enough to find the leverage point where an intervention can create the greatest impact.

Common Mistakes

Treating Problems as Independent

Connected problems often require connected solutions.

Ignoring Unintended Consequences

A solution can create new problems.

Focusing Only on the Immediate Result

Some interventions create short-term benefits but long-term damage.

Overcomplicating the Analysis

Systems thinking does not mean drawing a diagram with fifty variables.

The objective is clarity.

Forgetting the Human Element

Employees, customers, communities, and other stakeholders are part of the system.

Competition Example

A company wants to reduce delivery costs. The obvious solution is to reduce the number of delivery routes. But fewer routes create longer delivery times. Longer delivery times reduce customer satisfaction. Lower satisfaction increases churn. Churn reduces revenue. The cost-saving initiative may therefore improve one metric while damaging the overall business. A systems thinker asks, "What happens next?"

Mad Skills Drill

Choose a problem from a previous case. Write the problem at the centre of a page. Add:

three likely causes;

three consequences;

two relationships between causes;

two possible unintended consequences of solving the problem.

Then identify where to intervene to create the greatest positive impact.

Reflection Questions

Did your team ever solve a symptom rather than a root cause?

What unintended consequence could your recommendation have created?

Which stakeholders were part of the system?

What relationship did your team initially overlook?

Chapter Summary

Systems thinking helps you move from: Problems to Relationships to Root Causes to Leverage Points. The goal is not to understand everything. It is to understand enough of the system to make a better decision.

Key Takeaways

✓ Problems rarely exist in isolation.

✓ Look for relationships, not just individual factors.

✓ Distinguish symptoms from root causes.

✓ Consider unintended consequences.

✓ Look for leverage points where an intervention can create disproportionate impact.

Looking Ahead

Systems thinking helps you understand how the pieces connect. Analytical Thinking helps you break complex problems into manageable pieces and determine what the evidence is actually telling you.