Business Analysis Notes

Systems thinking

System Archetypes and Leverage

4 min read · Updated

In short Many different management situations share a small number of underlying structures. Peter Senge calls them system archetypes. Recognizing one tells you why “trying harder” is not working and where a small change could have a lasting effect.

Based on: P. Senge, The Fifth Discipline: The Art and Practice of the Learning Organization, ch. 6–7 (archetypes), with leverage also in ch. 4 and escalation in ch. 5.

On this page

Key ideas#

What an archetype is#

If reinforcing loops, balancing loops and delays are the nouns and verbs of systems language (see The Language of Systems Thinking), archetypes are its recurring plots: the same story with different settings and characters. Senge argues that a relatively small set, around a dozen, accounts for a great variety of situations. He develops two in detail in the archetype chapters and summarizes the rest in an appendix.

Limits to Growth#

The pattern. A growth process produces success, but also side effects that eventually slow the growth. Structurally, a reinforcing growth loop meets a balancing loop that kicks in at some threshold.

What managers usually do. Push harder on what worked before. That only strengthens the balancing process.

What to do instead. Leave the growth engine alone and find and remove the limiting factor. Expect several limits: removing one restores growth only until the next.

Senge’s examples include a technology company whose growing R&D staff pulled its best engineers into management, slowing new products, and a supplier partnership in which growing trust led the supplier to demand exclusivity, which the manufacturer refused.

Build your own story: 1. Find the reinforcing process: what is improving, and which action drives it? 2. Find the limiting factor, often a hidden goal, a norm or a scarce resource, and the balancing process it triggers. 3. Look for leverage in weakening that limit, not in pushing the original action.

Shifting the Burden#

The pattern. An underlying problem causes symptoms. Fixing it directly is hard, unclear or expensive, so people apply a quick symptomatic fix. The symptoms ease for a while, the underlying problem grows, and the system’s ability to solve it fundamentally weakens.

Three warning signs. Things get gradually worse despite periods of relief; the overall health of the system declines; and a sense of helplessness grows, as early relief turns into feeling like a victim.

Build your own story: 1. Identify the symptom, the squeaky wheel. 2. Identify the fundamental solution: lasting but slower or harder. 3. Identify the symptomatic solution: fast and easy, but temporary. 4. Identify the side effects of the symptomatic fix that create dependence on it.

Leverage lies in strengthening the fundamental response and weakening reliance on the symptomatic one.

Escalation#

In his chapter on the language of systems, Senge also names escalation: two parties each respond “defensively” to the other, forming a reinforcing loop that hurts both, as in advertising wars for market share.

Leverage#

Systems thinking looks for the point where a small, well-placed action produces a significant and lasting improvement. Senge borrows Buckminster Fuller’s image of the trim tab, a small rudder on the rudder that helps turn a large ship. Leverage is hard to see because it is usually separated from the symptoms in time and space. Finding it means looking at structures rather than events, and at processes of change rather than snapshots.

How to apply it#

  1. Write down the recurring problem as behavior over time.
  2. Ask: is something growing and then mysteriously stalling? Test Limits to Growth.
  3. Ask: does an easy fix keep working, while the problem keeps coming back worse? Test Shifting the Burden.
  4. Tell the archetype’s story with your own variables and draw the loops.
  5. Look for leverage at the limiting factor or the fundamental solution, and propose it alongside any short-term relief.
  6. Agree how you will tell whether the leverage is working, allowing for delays.

Example#

Limits to Growth at The Workshop. Online booking raises demand, revenue grows and marketing increases. Then reviews start to complain about rushed repairs, and bookings flatten. The limiting factor is mechanic capacity during peak weeks, not marketing. The leverage is capacity planning and pre-booked spring services, not more advertising.

Shifting the Burden. When parts run out, managers order by express courier. It works every time, so nobody forecasts demand any more, express costs climb, and the supplier treats every order as urgent. The fundamental solution is minimum-stock rules agreed with the supplier. The plan keeps express orders for genuine emergencies and tracks how often they are used.

Pitfalls#

  • Pushing harder on what used to work → find the limit.
  • Celebrating every quick fix → check for growing dependence on it.
  • Forcing every problem into an archetype → test the fit against the observed pattern.
  • Expecting instant results from leverage → allow for delays.

Sources and further reading#

  • P. Senge. The Fifth Discipline: The Art and Practice of the Learning Organization. Doubleday, 1990, ch. 6–7 (system archetypes), ch. 4 (leverage) and ch. 5 (escalation).