The System Is Bigger Than My Part

Local success can hide a system failure

Specialists need clear ownership. The risk appears when each team measures only its own component. A handover becomes someone else’s problem, an exception sits between systems or a customer receives the consequence of several individually reasonable choices.

In complex programmes, people often understand the process diagram but not the lived dependency. Parts of a Whole creates a simple physical experience of needing every contribution to connect.

I like it because the group cannot solve the task through explanation alone. People must look at what already exists, find a useful gap and adjust when the whole shape changes.

My part can be correct and still make the whole less useful.

The source and the original practice

Parts of a Whole appears in Yes, And by Kelly Leonard and Tom Yorton, with the exercise indexed at print page 80. A group uses their bodies to create the different parts of one object, then progresses to more complex shared pictures.

Leonard and Yorton frame the practice around ensemble work and the willingness to play one useful part rather than control the whole result.

Leaders, Are You Ready To Take The Creative Leap Into The Future? Leadership with Applied Improvisation by Theodore Klein adds principles including awareness, connection, value and creation. Those principles help me translate the physical image into a system conversation.

What the group discovers

Some participants choose the most obvious or central component immediately. Others wait because they cannot yet see a perfect role. Several people may create the same part while an essential connection remains empty.

The useful shift occurs when participants stop asking, ‘What part do I want to be?’ and begin asking, ‘What does the whole need now?’ That is a small but powerful change in attention.

A second round with a work process makes hidden functions visible. Reconciliation, exception handling, customer communication and operational monitoring often appear only after the obvious system steps have been claimed.

Use the debrief to examine handovers

I ask each participant what information their part needed and what it produced for someone else. This turns a sculpture into a conversation about interfaces, timing and shared outcomes.

The exercise does not replace process design. It creates curiosity before the diagram returns. People are often more willing to question a weak handover after they have felt how difficult it is to join a whole that nobody is watching.

• Which part could not function without another contribution?
• Where did two people solve the same need while another need remained empty?
• Who noticed the customer or final outcome?
• Which invisible activity keeps the real process working?