# The Pigeon Test: Why Change Fails (selected chapters)

Chapter 7, chapter 12 and the appendix.

7
The Complexity Argument
Now we get to the crux of the matter. I’ve been gesturing at
complexity for the last few chapters, using it to help explain why
changefails. But I haven’t yet laid out the argument in full. What
is complexity, specifically? How does it apply to organisations?
And what does it actually mean for whether our change and
transformation plans are likely to succeed? Complexity is a fact
of life, and one we work very hard to ignore, which goes some
way to explaining why so many frameworks struggle when they
meet reality. Understanding it properly, as opposed to name-
dropping the C-word willy-nilly, requires giving up on certain
hopes about what we can predict and control. That’s daunting,
which is possibly why I failed to fully understand it for so long,
even though Sami had handed me the pigeon on a plate over
twenty years ago.
You Can’t Sweep Complexity Under the Carpet
It’s fair to say the field of complexity doesn’t excel at explaining
itself to Joe Bloggs, so I’ll lay it out as clearly as I can, drawing
75

=== page 88 ===

THE PIGEON TEST
heavily on Sami’s book. Firstly, I need to clarify that none of
this is Sami’s invention. It’s the accumulated work of scientists
across biology, physics, and mathematics who spent the twenti-
eth century figuring out that the so-called clockwork universe
had limits. Prigogine showed how systems hold their shape
by constantly burning energy. Kauffman developed fitness
landscapes. The Santa Fe crowd of the nineties briefly made
complexity famous. There are many others who contributed
greatly. Sami synthesised this work in 2002 to help explain
why nations don’t develop as per government, IMF, United
Nations, and World Bank plans, and I’m repurposing it for
organisations. Because, unfortunately, those in international
and organisational development alike tend to be oblivious to the
fact that nations and organisations don’t play by linear rules.
I should say that not everyone in the field thinks this move is
legitimate. Some complexity thinkers argue human complex
systems need a separate theory, because people have identities
and intentions in ways that molecules don’t. I don’t disagree.
But nothing people add to a system makes it easier to predict.
So here goes. Complex systems are composed of many interact-
ing parts, and these interactions produce behaviours that can’t
be predicted by understanding the properties of the parts alone.
It’s not enough to have many parts; linear systems can have
many parts too. The parts in complex systems are connected and
influencing each other in ways that create feedback loops and
emergent, unpredictable patterns. Picture water in a bathtub.
With the tap and plug both closed, the water sits perfectly still.
That’s order, every part of the system locked into a predictable
pattern. Open the tap fully and the water splashes and swirls
with no discernible pattern at all. That’s chaos, with no pattern,
76

=== page 89 ===

THE COMPLEXITY ARGUMENT
no stability and everything in flux at once, the territory of
pandemics and financial crashes. But set the tap flowing at
just the right rate with the plug removed, and something else
happens. The water finds a rhythm. New water constantly
enters, old water constantly drains, and yet the system as a
whole settles into a stable, recognisable pattern that nobody
designed. This is the third state, self-organised complexity,
where chaos and order interact to produce something that is
neither. Everything that follows applies to bathtubs and bird
flocks too. Organisations are worse, because their parts have
opinions.
Organisations can occupy any of the three states, and can
contain all three at once. Parts of any organisation should be
still bathwater. Payroll should be boring;nobody wants an emer-
gent, self-organising approach to being paid. But suffocating
bureaucracy is what happens when the whole organisation is run
that way, everything locked into place and nothing adapting. An
organisation in genuine crisis is the tap fully open. Bureaucracy
can be endured for decades. Crisis burns energy faster than the
organisation can replace it, so it doesn’t last. It resolves into
some new pattern, or it finishes the place off. But taken as a
whole, organisations function best in the third state, because
take nasa whole they are made of people who interact constantly,
forming relationships and making decisions that affect each
other. As much as consultancies and top brass like to pretend
otherwise, it’s these interactions that shape the emergence
and evolution of patterns, cultures, norms, ways of working.
Suggesting they are designed and implemented from above is
fantasy. And much like the bathwater, an organisation can look
stable on the surface while everything within it is in constant
77

=== page 90 ===

THE PIGEON TEST
motion, right up until a small blockage or a sudden burst of
flow tips the whole thing into a different state. There’s no
telling in advance which nudge will do it. The technical term
for systems like this is “complex adaptive systems”. Complex
because of the emergent behaviours. Adaptive because the parts
can learn and change in response to their environment. Complex
adaptive systems have certain properties that make them behave
differently from linear systems.
Telltale Signs
First, cause and effect are not reliably linked. In linear systems
the connection holds. Drop the ball, it falls. In complex systems
the link comes loose. A small change, a new hire or a casual
comment from a leader, can cascade through the system and
produce massive effects. A major intervention, an expensive
restructure or transformation programme, can be absorbed with
no effect at all. And the same cause can produce different effects
each time it occurs. This is why transformation programmes so
often disappoint. The intervention seems large and significant,
yet the system absorbs it. Endless meetings happen, the new
structure is unveiled, and a few months later everything seems
much as it did before. The effort wasn’t disproportionate to
the outcome; the two were never reliably connected in the first
place.
Second, the whole is not the sum of its parts. Patterns,
behaviours, and properties arise from the interactions between
parts, often out of the blue, and don’t exist in the parts them-
selves. Culture is emergent. It arises from how individuals
interact, not from anything located in one of them. Innovation is
emergent too, ideas combining and recombining across multiple
78

=== page 91 ===

THE COMPLEXITY ARGUMENT
minds rather than issuing from a single one. So is dysfunction. It
arises from interaction patterns, not from individual bad actors.
The behaviour emerges from relationships, and relationships
can’t be reduced to the properties of the people in them.
Third, taking the system apart doesn’t reveal much about
how it behaves as a whole. This is Chapter 4’s reductionist
pillar, inverted. A clock can be understood through its gears
and springs. An organisation can’t be understood through
its org chart, its processes, or its people examined one at a
time. You can know everything about the individual parts (and
people) in an organisation and still not be able to predict how
the organisation will behave, because the behaviour lives in the
interactions, not the components. This should trouble anyone
in the diagnosis business. Every audit, every diagnostic, is an
exercise in decomposition, and decomposition is precisely the
method that doesn’t work here. It’s also a snapshot, which is
the second problem. To know what a complex system is doing
you have to observe it in real time. All of it. This would be
laborious work and it wouldn’t invoice well. So the industry
sells the snapshot instead, a picture of what the system looked
like the week the consultants were in the building. I’ve sold a
few of those myself. The slide decks were glorious.
Fourth, outcomes cannot be predicted in advance. This follows
from the first three, but it deserves its own statement because
it’s the property the change industry most needs to deny. The
system is one thing;what we can know of it in advance is another.
In linear systems, if you do X, you get Y. In complex systems,
if you do X, you might get Y, or Z, or nothing, or something
completely unexpected. The outcome depends on the state of
thesystem at the moment of intervention, the history that led to
that state, and countless other factors that can’t be fully known
79

=== page 92 ===

THE PIGEON TEST
or controlled. This is why best practices don’t transfer reliably.
A practice that worked brilliantly in one organisation might fail
completely in another, even if both organisations look similar
on paper.
Something else follows from these. Complex systems are
path dependent. Where the system ends up depends on where
it’s been. History plays a leading role. Two organisations
that look identical today might behave completely differently
because they have different histories, different founding stories,
different crises survived. The past is embedded in the present
in ways that constrain and enable what’s possible. This is why
you can’t just copy successful organisations. Even if you could
replicate their current practices perfectly, you couldn’t replicate
the history that made those practices work. The practices
emerged from a specific path; transplanted to a different path,
they become something else. Complex systems only make sense
in hindsight. You can trace backwards and the story holds
together, the founding decisions, the market conditions, the
people who stayed, the wins that shaped the culture. But none
of it was available in advance. You couldn’t have predicted it,
and any attempt would have changed the path.
There’s another way to see this. Imagine organisations existing
on terrain such as hills and valleys. A peak means you’re well
suited to your current conditions, your market, your people,
your history, your constraints. A valley means you’re struggling.
This terrain, in complexity parlance, is your fitness landscape.
The linear assumption is that there’s one universal landscape
with one peak that every organisation should aim for. Find the
best practices and climb to the summit. What worked over there
will work over here. Organisational development doesn’t work
80

=== page 93 ===

THE COMPLEXITY ARGUMENT
like that. It isn’t a rush to the nearest summit but a leisurely
exploration of the possibilities.
What’smore, the landscape isn’t universal. Each organisation
exists on its own terrain, shaped by its own coevolving systems,
with competitors, markets, regulators, suppliers and internal
teams all adapting to each other simultaneously. Your landscape
is different from mine. Another organisation’s peak might be
your valley. Their terrain was shaped by their sector, their
history, their particular people, their specific constraints. You
can’t transplant yourself onto their landscape. You’re stuck
on your own. Worse, the landscape shifts. What’s a peak
today can become a valley tomorrow. The conditions that made
something successful change. Markets move, people leave.
Today’s thriving creature is tomorrow’s dodo.
Survival of the Most Stable
The question the landscape leaves open is how anything survives
on it, let alone improves. Sami’s book keeps returning to a cycle.
An evolving system, whether an animal staying alive, acompany
struggling to grow, or a whole nation seeking development,
has to keep moving through cycles of survival, adaptation and
learning. To adapt successfully, a system first has to survive
long enough to evolve into its next stable pattern. Survival of
the fittest, he wrote, is really survival of the most stable. Not
the strongest, not whichever virtue this year’s operating model
promises. The most stable. Stability is what buys the time in
which adaptation can happen at all.
And stability doesn’t come free. The second law of thermody-
namics says that things left to their own devices drift towards
disorder; a pile of rubble never assembles itself into a building.
81

=== page 94 ===

THE PIGEON TEST
Keeping a system in a stable state takes continual energy from
outside, which in an organisation means the often tricky work of
people interacting, day after day, holding a recognisable pattern
together while the details churn beneath it. Too little of that and
the second law wins; the pattern dissolves. Too much and the
system is killed the other way, held so rigidly that nothing new
can happen. Learning is the third part of the cycle. The system
takes in its environment and spots regularities. It responds
in ways that help it survive long enough for the next round
of adaptation. Impair any part of that and the whole process
suffers. This holds for every complex adaptive system, from
immune systems to economies. Organisations aren’t exempt
because they have a strategy document.
Big-bang transformation works on the opposite assumption.
The programme’s logic is that the current stable pattern is the
problem, so the pattern must be broken. Restructure, redefine
the operating model, all at once, to a deadline. Sometimes the
pattern really is the problem. But it is also the thing doing
the surviving, the thing that holds the organisation together
while adaptation happens, and breaking it is the only part of
the plan that reliably works. Nobody can specify what comes
next. Deliberately destabilising at scale and at speed attacks
the part of the cycle everything else depends on. People stop
learning and start bracing. Energy that went into small daily
adjustments goes into protecting positions and updating CVs.
The programme damages the organisation’s ability to change,
then blames the people for resisting.
No Interactions, No Progress
82

=== page 95 ===

THE COMPLEXITY ARGUMENT
Complex systems tend towards self-organisation. This is the
third state of the bathwater. Given the right conditions, pat-
terns emerge without anyone designing them. Flocks of birds,
schools of fish, markets, ecosystems all exhibit self-organised
behaviour. No one is in charge. No one is coordinating. And yet
coherent, stable patterns arise. Organisations can self-organise
too. This is, in fact, what the self-management movement was
betting on. The bet is that if you remove the constraints of
traditional hierarchy, people will naturally organise themselves
into effective patterns. The bet isn’t wrong, exactly. Self-
organisation does happen. But it doesn’t happen reliably or
predictably. The conditions that allow it to emerge are context
specific and often fragile.
Sami was clear about what those conditions are. For self-
organisation to emerge, people must be free to interact with
each other, not constrained by rigid hierarchy, silos, or fear.
They must be capable of interacting, which means having
the skills, the time, and the information to actually engage
with each other meaningfully. And there must be simple
guiding principles that command broad support. Basic shared
understandings about how things work here, not elaborate
rulebooks that nobody follows. There’s a distinction here that
“simple guiding principles” doesn’t quite capture. In ordered
systems, constraints determine what must happen. The rules
on an assembly line aren’t suggestions; they’re the mechanism.
In complex systems, constraints work differently. They shape
what can happen without specifying what does. The philosopher
Alicia Juarrero worked this out in the late 1990s, a few years
before Sami’s book appeared, and Dave Snowden has taken
the work further since, distinguishing governing constraints,
83

=== page 96 ===

THE PIGEON TEST
which set limits on what happens, from enabling constraints,
which allow things to happen without determining them. The
conditions are the space within which something might emerge,
not a prescription. That’s why you can’t install them from
outside.
These conditions aren’t the point in themselves. They exist
for the sake of what goes on inside them, the interactions
between people, because that is where the energy comes from.
Volume is not the measure. Plenty of organisations are wall
to wall with interaction, meetings all day and messages all
night, and starving all the same, because the interactions carry
no trust and nothing much else. Hold most organisations up
against the conditions and you’ll see why self-management
is rare. Freedom to interact is usually partial, granted within
limits somebody else sets. Capability is patchy, since people are
overloaded, and often short of the information they’d need to
contribute. Shared principles either drown in a policy manual
(or handbook if trendy) nobody reads or never get agreed at
all. I’ve written a few of those manuals. Any one of these can
be present. All three at once, holding steady long enough for
something to emerge, is the rare part. Sami put it plainly. No
interactions, no progress.
Feuds and Full Calendars
One suppressor deserves naming on its own. Conflict. Some-
times it’s live, a feud everyone has learned to work around.
Sometimes it’s buried, a disagreement so carefully avoided that
half the team’s conversations are shaped by not having it. Either
way the effect is the same. People give each other a wide berth.
Conversations that should happen don’t. The interactions thin
84

=== page 97 ===

THE COMPLEXITY ARGUMENT
out, and the organisation runs on less, usually while everyone
involved insists things are fine. Leaders tolerate this more often
than they’d admit, because the person at the centre of it is a
friend, or frightening, or the conversation is one they’d rather
not have. And the damage outlasts the conflict. Interactions
run on trust accumulated slowly over time, and trust spent
doesn’t refill on demand. Even once the air is cleared, peoplecan
keep avoiding each other out of habit, and the interactions take
time to return. There are no shortcuts back to healthy human
interactions. And while they’re gone, the cost is bigger than a
bad atmosphere. Starved of the energy that interactions supply,
the cycle of survival, adaptation and learning is broken. The
team swings between flare-ups and frozen silence, chaos and
order, everything except the state in between, self-organised
complexity, where adaptation happens.
If interactions supply the energy, it would seem to follow that
more connectivity is always better. It isn’t. Connectivity has
a working range, like the tap. Too little and the system settles
into order, silos sealed, nothing reaching anything else. Too
much and everything is coupled to everything, and the system
tips towards chaos. When every team’s work depends on every
other team’s agreement, conflicting requirements can only be
resolved by compromise all round, and the compromises shed
variety. Teams that once suited different conditions converge on
the one shape everyone can live with, and the organisation ends
up fit for exactly one set of circumstances. And circumstances
change. Events, dear boy… There’s a name for this. Complexity
catastrophe, where progress grinds to a halt under repeated
local failures, everyone busy and nothing getting better. The
everyday version is not exotic. It’s the calendar. When the
85

=== page 98 ===

THE PIGEON TEST
meetings required to coordinate the work outnumber the hours
available to do it, that’s excessive connectivity, experienced one
dreaded invitation at a time.
Negotiating with a Hurricane
These conditions can’t be conjured up the way consultants
typically work. You can’t manufacture freedom to interact by
running workshops on psychological safety. You can’t create
capability with a new meeting format, or establish shared prin-
ciples by writing them on a poster. That’s treating conditions
like software you can install. What you can do is different, and
more limited. You can remove what suppresses interaction, the
policies that punish honesty, the leaders who hoard control. You
can stop doing what drains energy, the pointless reporting and
the performative meetings. And you can create space where
organic patterns might emerge, though you can’t force them to.
This work is slow, indirect, and often fails. The conditions might
never develop, or they might fade when circumstances change.
You’re removing obstacles and hoping something better grows
in the space you’ve cleared. That’s a very different promise from
transformation.
Recall the four properties. Cause and effect are not reliably
linked. The whole is not the sum of its parts. Taking the
system apart tells you little about how it behaves. And outcomes
cannot be predicted in advance. Systems like this can’t be
controlled the way linear ones can. You can nudge them, you
can try to create conditions in which better outcomes might
emerge, but there’s no formula for it, and you can’t engineer
desired results with confidence. The system is too sensitive to
conditions you can’t fully know or control. Path dependence
86

=== page 99 ===

THE COMPLEXITY ARGUMENT
and the tendency to self-organise deepen the trouble for anyone
trying to steer. The system is already shaped by where it’s been,
and it will organise itself around whatever you do, in patterns
of its own making rather than yours. This is the core of the
argument. Organisations are complex adaptive systems, and
therefore they don’t respond to intervention the way linear
systems do. The linear toolkit of diagnose, plan, implement,
and measure assumes a level of predictability and control that
complex systems don’t offer. It’s the wrong tool for the job, like
trying to negotiate with a hurricane.
Not Systems Thinking, Not Chaos
A word on what this isn’t. Systems thinking sounds like the
same territory, and the two get used interchangeably. They
are not the same. Systems thinking keeps the designer in the
picture. Map the feedback loops, locate the levers, the points of
maximum influence, intervene where the map says. Its best
thinkers knew the limits, and said so. But the practice sold
under the label kept the promise intact. Understand the system
well enough and you can steer it. Complexity thinking is more
sceptical, and for damn good reason. The map is always partial,
the levers won’t stay put, and the act of intervening changes the
system being intervened in. Read this book as systems thinking
and you’ll leave with a subtler way to steer, which is precisely
the move it’s warning you against. The design-and-control
assumption survives by redecorating. The opposite misreading
is just as available. Complexity doesn’t mean chaos. Complex
systems aren’t random; they have regularities, patterns that
recur and can be observed. Weather is the textbook nonlinear
system, famously hard to predict, yet short-term forecasts
87

=== page 100 ===

THE PIGEON TEST
are still useful. It’s the ten-day forecast you shouldn’t plan
a wedding around. Organisations have regularities too, and we
can work with them, run safe-to-fail experiments, and adapt
as we learn. Just don’t fall for the idea that any system this alive
can be understood well enough to be steered.
Chapter 4 set out what I believed, that the right practices
would reliably produce better organisations, that the patterns
found in progressive organisations could be extracted and trans-
planted, that practice was the bottleneck. Those beliefs assume
a reliable relationship between intervention and outcome, and
that understanding the parts (the practices) gives you control
over the whole (the organisation). Complexity theory says
otherwise. The patterns in progressive organisations might
be effects rather than causes. Emergent properties of specific
conditions, not transportable solutions. This doesn’t make the
practices worthless. They’re ingredients, not recipes. Whether
the possibilities they open up are realised depends on history,
culture, personalities, timing, luck, none of which can be
controlled or fully predicted.
Understanding this earlier would have changed how I talked
about the work and tempered my expectations about what could
beachieved. It would have prepared me, and the people I worked
with, for the messiness and unpredictability that are inherent in
complex systems. But taking complexity seriously means giving
up the hope that the right approach will produce reliable results.
Accepting that failure isn’t always fixable, that sometimes the
conditions just aren’t right. Sitting with uncertainty rather
than fighting it with confident frameworks. Most people in
the transformation business aren’t willing to do this. The
business model depends on confidence, on having answers.
88

=== page 101 ===

THE COMPLEXITY ARGUMENT
Complexity undermines all of that. So it gets acknowledged
superficially, yes, organisations are complex, yes, change is
hard, and then ignored in practice. The frameworks keep getting
sold and the results keep disappointing. I was part of this
pattern for years. I knew Sami’s work and I could explain,
albeit clumsily, the difference between linear and complex
systems. But when it came time to sell my services or course, I
reverted to linear assumptions. The market demanded it. Clients
wanted solutions, not philosophy lectures about the limits of
intervention.
Partial Answers
The question I couldn’t answer then, and still struggle with now,
is what it would actually look like to take complexity seriously
in practice, as a genuine orientation towards the work rather
than a framework. What would you do differently? What would
you promise? What would you refuse to promise? I don’t have
complete answers. But I have some partial ones, developed
through years of getting it wrong.
You’d be direct about uncertainty, and not in the “we can’t
guarantee outcomes” legal-disclaimer sense. I mean admitting
you don’t know what will happen. Clients don’t enjoy hearing
it, but they’re still better served by it than by false confidence.
You’d also ask what kind of problem you’re facing before
deciding how to act. Some of any organisation is still bathwater,
and still-water problems can be planned and implemented with
certainty. The payroll fix doesn’t need a hypothesis. Themoving
water is different. Everything there runs on interactions, nobody
can call the outcome in advance, and anything you try is an
experiment whether you admit it or not. So you’d admit it.
89

=== page 102 ===

THE PIGEON TEST
You’d measure what actually happens, not whether the thing
got delivered, and adapt as you learn. Your role would be a
modest one. You’re not the one who changes the organisation.
The people inside it do that, or don’t. At best, you can create
some space, introduce some ideas, maybe shift some conditions
slightly. But the work is always theirs, not yours. Most of
what you try won’t produce dramatic results, and you’d have to
accept that. The patient, modest work of creating slightly better
conditions might do more good than the big transformation
programme. But of course, it’s harder to sell and harder to take
creditfor. That won’t change until leaders genuinely understand
complexity. This book is my small nudge at those conditions.
Experiments are the learning leg of the cycle. Learning is how a
complex adaptive system finds its way to its next stable pattern,
and an experiment is learning made deliberate. It’s also the only
form of intervention that doesn’t pretend to know how things
will turn out. An experiment can fail, and often will. So sizing is
the discipline. Because a system has to survive long enough to
adapt, experiments must be sized so that failure never threatens
survival. Each one small enough that failure costs little, and
enough of them that some will land. The moment an experiment
becomes too big to fail, it has stopped being an experiment
and become a transformation programme with better branding.
Anyone can run an experiment, and it will usually teach the
person who ran it something. But without the freedom and
capability to interact, and without shared principles to make
sense of what happened, the system can’t read the result. The
learning stays where it landed, one person or one team slightly
wiser, and travels no further. Interactions are how learning
moves, and where they’re suppressed, even a good experiment
90

=== page 103 ===

THE COMPLEXITY ARGUMENT
is a letter nobody delivers.
The change industry has heard all this, and it has a product.
The pilot portfolio. Success criteria agreed up front, RAG
statuses reported monthly, a steering group deciding which
pilots scale. It’s a plan wearing a lab coat. The outcomes
are specified before anything runs, failure is a red status to
be explained away rather than information to be used, and
whatever learning occurs travels upwards to the steering group
instead of outwards through the organisation. And any process
that promises to reliably deliver the right experiments is the
recipe moved one level up.
These orientations don’t add up to a methodology. They can’t
be packaged and certified. They’re more like a stance, a way of
approaching the work that takes complexity seriously instead
of paying it lip service. Whether this stance is commercially
viable, I don’t know. The market for tentative uncertainty is
smaller than the market for confident solutions. But complexity
is insistent. You can ignore it, but the tap keeps running and
the water keeps finding its own pattern, whatever the slide deck
says.
91

=== page 104 ===

12
What Remains
After everything I’ve argued in this book, it would be foolish
to end with a new methodology or framework.
Here’s what
actually works. Follow these steps.
That would undermine the
whole book. But it would also be strange to end with nothing.
Almost everyone in this space, myself included for most of my
career, treats complex systems as if they were linear. That’s the
category error this book has been about, and this goes a very
long way to explaining why change fails. If you close this book
clear about that, and able to catch yourself before you make the
next one, it has done its job. Knowing about the error doesn’t
stop you from making it.
I knew the theory. I could tell a ball from a pigeon, and
look at what I did with that. I watched the practices fade in
one engagement after another and blamed implementation
every time, and in coaching I reached for yet another linear
intervention. All the while, I kept telling myself that if we could
just get the leader to change, the rest would follow. I’d been
trying to engineer emergence, while knowing, intellectually,
that you can’t. I’d been making thesame mistake as every leader
139

=== page 152 ===

THE PIGEON TEST
I’d ever gently confronted about their blind spots. The linear
paradigm had been running in me the entire time, and when
that finally dawned on me, it was a crap epiphany.
When I shared the first chapters with my newsletter, I’d been
sitting on them for twelve months. The chapters were ready,
but I wasn’t ready to release them into the world. Sharing them
felt like the final nail in the coffin of my consulting career, and
the first time I’d been fully honest about what I’d seen. It was
daunting, and I expected pushback and loads of unsubscribes.
Instead, people were relieved someone had said it, and nobody
asked me for solutions. One reader wrote, “This made me
feel nauseous, and like someone had finally said what needed
to be said.” Most of the people who replied had been doing
what I’d been doing, trying to make emergence happen and
blaming themselves when it didn’t stick, assuming they were the
only ones struggling with the gap between what the movement
promises and what actually happens.
Knowing this doesn’t mean giving up the work. Whether you run
the workshops yourself, or lead the people they’re for and pay
someone else to run them, the work itself might look much the
same, though what you expect of it shouldn’t. Whatever the plan
says, the people who’ll live with the result decide what actually
happens to it, which bits they keep and which they quietly drop,
the way that team in the kitchen had worked out the rounds
thing would last until I stopped coming. Once you accept that,
you can stop overselling what’s possible, and stop carrying the
guilt when it doesn’t stick, because the outcome was never yours
to guarantee.
140

=== page 153 ===

WHAT REMAINS
When things don’t go to plan, it should surprise you less.
You’ll be slower to blame implementation or reach for the next
framework, and less likely to wonder whether you should have
focused on the practices or the people or the culture or the
leadership or the inner life. You’ll have a better idea what you’re
looking at, and more patience with the organisation in front
of you, because you’ll recognise what it’s doing. It’s surviving,
adapting where it can, learning when the conditions let it. That
cycle is slow and it can’t be skipped, and the quick fixes sold as
shortcuts can impair it. The organisation that’s still standing
has at least got the first part right, which is more than the
transformation programme can say.
I know what you’re thinking. Because I’m thinking it too.
Okay,
so what the fuck do I do now?
The urge is immediate. You want something actionable. But
offering you a fix would require me to pretend I know your
context and your actual room for manoeuvre. I don’t. Any
prescription I gave would be linear thinking applied to your
complex situation, which is precisely what got us here in the
first place. Someone external, telling you what to do next. Me,
still carrying the toolkit.
That urge is what helps smuggle the category error in. What-
ever you do next, the trouble starts when you decide in advance
what it will deliver. Expecting the transformation programme
to fix collaboration by the end of the year, or squads and tribes
to make you agile because they seemed to work at Spotify,
is marking a cross on the floor for a pigeon. When it lands
somewhereelse, the implementation takes the blame. Changing
the vocabulary doesn’t help. “We’re creating the conditions”
141

=== page 154 ===

THE PIGEON TEST
sounds humbler, but it’s the same prediction if you’ve already
told the board what will grow in them. Even now, finishing this
book, I feel the pull, and it will turn up for you again the next
time someone hands you a complex problem and a deadline.
Sami’s check against that pull was what he called a funda-
mental requirement. “Before we rush in with solutions to the
problems, we have to determine first the nature of the system
in question.” So I’ll leave you with the question he left me with,
in a lecture hall in Liverpool, twenty years before it finally sank
in: am I launching a ball, or am I launching a pigeon? Payroll
is a ball. Whether a new way of working takes hold is a pigeon.
Ask the question before you promise anyone what a change will
deliver. The answer is often obvious. Sticking with it when
someone wants a delivery date is the hard part.
The consultant always leaves. Now so does the author. Sami
showed development economists the same error in nations and
international development, and most of them, as he’d predicted,
weren’t for changing. But you can see it now, in organisations.
A linear solution applied to a complex problem, with the result
predicted in advance. That’s what his pigeon was for.
The pigeon has landed. I hope.
142

=== page 155 ===

VI
Appendix

=== page 156 ===


=== page 157 ===

13
The Pigeon Test: Structures
I nearly left these out. One argument in this book is that we
keep applying linear recipes to complex situations, and that the
people selling the recipes, me included, keep doing it because
recipes sell. So there is something off about arriving at the end
and handing you five workshop structures. Here comes the next
framework, dressed up as the cure for frameworks.
I have two defences, and I’m not certain that either holds. The
first is that they don’t tell you what to do. Each one starts from
your own work, in your own handwriting, and asks a question
your group answers from its own evidence. There’s no need for
me in the room, or this book. Nobody has to have read a word
of it and nobody has to utter the word complexity. Whatever
comes out of it says something about your context, and I don’t
supply any answers (or patterns).
The second is that they refuse what the recipes promise.
There’s no end state in any of them. No roadmap, no date,
no maturity model, no report. Two of them finish by making
something smaller than anyone wanted it to be, and one finishes
by asking a group to protect something nobody ever planned.
145

=== page 158 ===

THE PIGEON TEST
Whether that adds up to honouring the argument or quietly
breaking it, I don’t know. I’ll let you be the judge of that.
They’re in an appendix rather than a chapter because they’re
reference material and not argument–that finished a few pages
ago. They’re also early in their development. They’ve been
tested with teams, and the testing continues. Each time a group
uses one I learn something, usually that a timing doesn’t work
or a question invites flattering answers, and now and then that
a step had too much instruction or too little. So they’ll keep
being adapted, and the versions printed here will soon be out
of date. The latest are at thepigeontest.com, where they get
corrected as groups run them and tell me what broke. They’re
free and always will be. If you try one, I’d love to hear how it
went, especially the bit that didn’t work. My email is on the
website too.
Where to start, and what’s here
Five workshop structures for groups who want to work out,
from their own evidence, what kind of work they are actually
doing. Start with Same Plan, Ten Times. It needs no preparation
or reading, and it hands a group the distinction every other
structure here assumes, between work that gives thesame result
twice and work that doesn’t. If you only ever run one of these,
run that one.
1.
Same Plan, Ten Times
(60 min.) Sort the work your
organisation does by whether the same plan would give the
same result twice, then mark how much of it was planned
as though it would.
146

=== page 159 ===

THE PIGEON TEST: STRUCTURES
2.
As It Arrived
(60 min.) Trace what your organisation did
to the practices it imported from elsewhere, and find out
which of them people still follow when nobody is looking.
3.
Smaller Than That
(50 min.) Help each other move on a
change that’s stuck, in threes, under a rule that forbids
adding anything new.
4.
Several at Once
(60 min.) Run several small ideas for a
challenge side by side instead of choosing between them,
and let time and energy do the selecting.
5.
Without Being Asked
(60 min.) Find the places where
people already talk to each other usefully without anyone
arranging it, then work out what is keeping those places
energised.
Before you run one
Three things share the pigeon’s name, and it’s worth separating
them before you start. This book is the argument. The Pigeon
Test is a free tool that helps you read a situation. You answer
a set of questions about something you’re about to do, and it
comes back with simple, complicated or complex, and what that
reading means for the move you were planning. It tells you
where you are rather than what to do, and the reading expires,
because situations move. It’s at thepigeontest.com/tool. The
Pigeon Test Structures are for groups and none of them hands
back a reading. Same Plan, Ten Times comes closest to the tool,
sorting a team or organisation’s work by the distinction the tool
reads one situation at a time. The other four work with what
follows from it.
The pigeon itself, which all three are named after, is the
147

=== page 160 ===

THE PIGEON TEST
metaphor this book is built on. Launch a ball and you can
work out where it will land; launch a pigeon and where it lands
cannot be predicted. Simple and complicated work is the ball,
and complex work is the pigeon. Three of the structures are
run standing up at a wall, sorting sticky notes (Same Plan, Ten
Times; As It Arrived; Without Being Asked). Two are run seated,
in small groups (Smaller Than That; Several at Once). The walls
deliver their finding once per group; the seated ones give you
something different every time. Pick from them like a menu,
and don’t run more than two in a day.
You don’t need to be a facilitator to run these. Somebody keeps
time and asks the questions in the instructions, and that’s the
whole job. Foursomes are two pairs joined; a leftover pair or
single folds into the nearest foursome, and a five or six just
argues harder. Each has a variation, under
Riffs and Variations
,
for groups who have read this book. If they haven’t, skip it;
the structures work without the book’s argument. Notes on
running them well, including timings, the most senior person
in the room and running them online, come after the five sets
of instructions.
Where the format comes from
The format is borrowed from Liberating Structures, a fantastic
free collection of ways to run a room, put together by Henri
Lipmanowicz and Keith McCandless. I’ve been using them for
years and I can’t name anything that has done more for healthy
human interactions in the groups I’ve worked with.
They’re inspired by complexity science, which I’d argue helps
explain why they work so well. Their authors describe them
148

=== page 161 ===

THE PIGEON TEST: STRUCTURES
as starting from a hunch that what we know about how living
systems organise themselves might translate into how people
work together. Complexity isn’t the only ingredient, and several
of the individual structures take influence from other fields, but
it’s a foundation.
A Liberating Structure sets a handful of simple rules about
who talks to whom and for how long, then gets out of the way
and lets a group produce something nobody in it designed. The
formats we tend to use in rooms don’t do that. A presentation
or a managed discussion holds people too tightly, while an open
discussion or a brainstorm can be a free-for-all. In different
ways, all of them tend to limit who gets to participate and how.
Crucially, they don’t need a professional facilitator, which is
the best part of their design. They’re deliberately simple, so that
anyone can run one without training. That was the standard
I tried to hold these five to. Mine are written in the style of
Liberating Structures but aren’t part of the official repertoire,
and any flaws are my own. Each structure ends with a note
saying where it came from.
Attribution
The Pigeon Test Structures, by MarkEddleston, made in the style
of Liberating Structures, developed by Henri Lipmanowicz and
Keith McCandless. Not part of the official Liberating Structures
repertoire. Licensed under Creative Commons Attribution-
ShareAlike 4.0 International (CC BY-SA 4.0), the same licence
as Liberating Structures.
Current versions at thepigeontest.com.
149

=== page 162 ===

14
Structure #1: Same Plan, Ten Times
Find the two kinds of work your organisation plans as one
(~60 min.)
What Is Made Possible
A group puts its own work on a wall and sorts it by one question,
whether the same plan would give the same result twice. Then
it marks which pieces of work were planned as though it would.
If the marks pile up on work that wouldn’t give the same result
twice, the group sees that for itself, in its own handwriting, and
nobody has to persuade anyone of it.
Five Structural Elements (Min Specs)
Structuring Invitation.
Invite the group to think of all the actual
work the organisation does, and to sort it twice to see what the
wall says. The wording is in the Intro step, below.
150

=== page 163 ===

STRUCTURE #1: SAME PLAN, TEN TIMES
Space and Materials.
A wall with two zones marked in tape, left
and right, unlabelled. Sticky notes, pens, dot stickers, and room
for everyone to stand at the wall together.
Participation Distribution.
Everyone writes, sorts and dots, and
nobody’s stickies carry more weight than anybody else’s. The
facilitator asks the questions and otherwise stays out of it. Best
with eight people or more; below that the wall is too quiet to
argue.
Group Configuration.
Alone, then pairs, then foursomes, then
everyone, then foursomes again.
Steps and Time Allocation.
•
Intro
(2 min.). Give the invitation: “Think of the actual
work your organisation does. All of it, from fixing servers
to merging teams. We’re going to sort it, twice, and see
what the wall says.” Point at the two taped zones without
explaining them; the sort question comes later. Say once,
plainly, that some of the work going on this wall was
planned by people standing at it, and that nobody is here to
be blamed for it.
•
Write alone
(4 min.). Each person writes real pieces of work,
one per sticky. E.g. Fix a server, deliver a service, launch a
product, restructure a department, merge two teams.
•
Pairs
(5 min.). Combine your stickies and keep the eight
most specific.
•
The sort
(15 min.). Pairs join into foursomes and take their
stickies to the wall. Ask the question this one is named after:
“If you did this ten times with the same plan, would you get
151

=== page 164 ===

THE PIGEON TEST
the same result every time?” Left zone, yes. Right zone, no.
Two minutes of argument for the borderline ones, then they
go where the foursome lands. Draw a line under any sticky
that used the full two minutes; the wall should remember
what was fought over.
•
Second pass
(8 min.). Still in foursomes, nothing moves.
Ask the foursomes to put one new question to every sticky
in both zones: “When your organisation last did this, was
there a plan that promised a particular result by a particular
date?” If yes, it gets a dot.
•
Stand back
(12 min.). Everyone. Ask: “What do you notice
about where the dots are?” Then set a timer for twominutes
of silence for everyone to think and write one thing they
notice on a sticky. Then go round the room, each person
reading theirs out, with no commentary.
•
Live inside it
(9 min.). Back into the same foursomes. Each
foursome picks one dotted sticky from the right zone, apiece
of work its members are involved in. Ask: “What does its
plan pretend that everyone at this wall knows isn’t certain?”
Then look at the right zone again and ask: “Is anything there
working without a plan?”
Call it an hour once people have moved about.
Practice Insights
Tips.
The sort question has to stay that concrete. “Is this
predictable?” lets people answer with their self-image instead
of their experience. The argument is half the point; the two-
minute timebox stops it eating the whole session. Dots in
the left zone are fine, they belong there; watch whether the
152

=== page 165 ===

STRUCTURE #1: SAME PLAN, TEN TIMES
right zone collects just as many. Let the timer hold the silence
after the stand-back question. If the right zone comes back
clean, let it stand. Either the organisation really doesn’t plan its
unpredictable work as though it were predictable, or the room
believes more of its work is predictable than it is, and either is
worth knowing.
Someone may ask why there is no middle zone for work that’s
hard but knowable. Because the question doesn’t need one. A
rocket launch is about as hard as work gets and it still goes in the
left zone. Simple and complicated both give you the same result
twice, which is all the sort is asking. The other reason is that a
middle zone is where the argument goes to die, since hard-but-
knowable is the flattering answer and given the option the wall
fills up with it.
Riffs and Variations.
For a group that has read this book, name
the zones at the end. Left is the catapult and the ball. Right is
the pigeon.
Practical Applications.
Before annual planning, or at the kick-off
of anything with transformation in the title. Retrospectives that
keep concluding the plan was fine and the people weren’t.
Optional Liberating Structures String.
Carry each foursome’s
chosen sticky into 15% Solutions, or into Creative Destruction
(TRIZ).
Where it came from.
The official repertoire already sorts work this
way in Agreement and Certainty Matrix, which maps challenges
by how much people agree and how much is known. This one
asks a blunter question and puts the answer on a wall.
153

=== page 166 ===

15
Structure #2: As It Arrived
Find out what your organisation did to the ways of working it
imported (~60 min.)
What Is Made Possible
An organisation’s import history ends up on one wall, sorted
into three zones: kept as itarrived, changed into its own version,
or gone. Then the room marks which parts of it people still do
when nobody is looking.
Five Structural Elements (Min Specs)
Structuring Invitation.
Invite the group to think of the practices,
frameworks and ways of working the organisation brought in
from somewhereelse, and to find out what this place did to them.
The words to use are in the Intro step.
154

=== page 167 ===

STRUCTURE #2: AS ITARRIVED
Space and Materials.
A wall with three zones marked in tape, left,
middle and right, unlabelled. Sticky notes, pens, dot stickers.
Room for everyone to stand at the wall together.
Participation Distribution.
Writing, sorting and dotting are
everybody’s, and nobody’s stickies outrank anybody else’s. The
facilitator asks the questions and then keeps out of the way.
Eight people up.
Group Configuration.
Alone, then pairs, then foursomes, then
everyone, then foursomes again.
Steps and Time Allocation.
•
Intro
(2 min.). Give the invitation: “Think of the practices,
frameworks and ways of working this organisation brought
in from somewhere else. Things like stand-ups, Agile, the
engagement survey, the operating model with a Scandina-
vian name. We’re going to find out what we did to them,
and which ones are still going.”
•
Write alone
(4 min.). Each person writes practices that
arrived here from somewhere else, one per sticky. Only
things that were adopted. E.g. retros, the nine-box grid, the
survey, the framework a consultant brought.
•
Pairs
(5 min.). Combine your stickies and keep the eight
most specific. Before a sticky goes up, write two things on
it: where it came from, and the year it arrived. A guess at
the year is fine. No source, no sticky.
•
The sort
(16 min.). Pairs join into foursomes and take
their stickies to the wall. Ask: “Is it done today the way
it arrived?” Left zone, yes. Middle zone, changed into your
155

=== page 168 ===

THE PIGEON TEST
own version. Right zone, gone, nobody does any version
of it at all. Between left and middle, ask whether whoever
sold it would recognise what you do now. Between middle
and gone, if any corner still does a version, it’s middle.
Contested ones get two minutes and then they land. Draw a
line under any sticky that used the full two minutes.
•
Second pass
(7 min.). Still in foursomes, nothing moves.
Ask a new question of every sticky in the left and middle
zones: “Do people do it when nobody is checking?” Only
sightings count; if the only evidence is the calendar invite
or the dashboard, that’s checking. If yes, it gets a dot.
•
Stand back
(12 min.). Everyone. Ask: “What do you notice
about where the dots are?” Then set a timer for twominutes
of silence for everyone to think and write one thing they
notice on a sticky. Then go round the room, each person
reading theirs out, with no commentary.
•
It came from here
(9 min.). Back into the same foursomes.
Each foursome picks one dotted sticky from the middle
zone. Ask: “What does your version know that the original
didn’t?” Name it, and name who worked it out, because it
didn’t change by itself.
An hour, allowing for movement and stragglers.
Practice Insights
Tips.
Keep the sort question concrete. Ask “Was the rollout suc-
cessful?” instead, and people defend practices they championed
rather than report what happened to them. The same discipline
holds on the dots, where “people love it” is an intention and
the question asked for sightings. A left-zone sticky with no
156

=== page 169 ===

STRUCTURE #2: AS ITARRIVED
dot is done exactly as it arrived, but only while somebody is
checking. Don’t point it out; the room will notice it at the stand
back. And if the gone zone comes back nearly empty, don’t
celebrate, look at the years. Organisations delete their failures,
and a wall where nothing is older than three years is a graveyard
with the headstones taken out.
Riffs and Variations.
For a group that has read this book, point at
the left zone at the end and say: “Everything here was worked
out by another organisation to fit its own situation. What arrived
was a snapshot, and theirs has probably changed since. We’re
still running the snapshot.”
Practical Applications.
When the next import is being proposed,
before it’s rolled out. When a practice is about to be scrapped
for not being done properly, because the wall may show it has
been changed into the organisation’s own version rather than
failed.
Optional Liberating Structures String.
Carry a dotted middle-zone
sticky into Shift & Share, so the people who rebuilt it can show
the room how it actually runs. Or take a contested sticky into
Simple Ethnography and go and watch the thing before anyone
rules on it.
Where it came from.
Not built on anything in the official reper-
toire.
157

=== page 170 ===

16
Structure #3: Smaller Than That
Get unstuck without adding anything new (~50 min.)
What Is Made Possible
People help each other move on changes that aren’t going
the way the plan said, under a rule that bans adding anything
new. Everyone leaves with one probe they can start without
permission. And everyone notices how often they were about to
hand somebody a solution.
Five Structural Elements (Min Specs)
Structuring Invitation.
Invite the group to bring a change that
isn’t going the way the plan said, their own or one they’re
watching others struggle with, and to help each other move
on it without adding anything new. The wording is in the Intro
step, below.
158

=== page 171 ===

STRUCTURE #3: SMALLER THAN THAT
Space and Materials.
Chairs in threes, no tables. One card per
triad, where all three can see it, with this written on it and
nothing else:
•
No new things. No new practice, tool, meeting or frame-
work.
•
Questions only, three kinds.
•
Smaller
: what is the smallest version that could teach you
something by Friday?
•
Remove
: what could you stop, or loosen, without asking
anyone?
•
Watch
: how would you know whether what you try is
working, or making things worse?
•
About to suggest something? Ask one of these instead.
Participation Distribution.
Everyone presents once and helps
twice. The facilitator states the rule and keeps time; the card
does the policing. Three people or more; a bigger group runs
several triads at once. A leftover pair runs two rounds with
one helper each time. A spare person joins a triad to make a
foursome, which runs four shorter rounds in the same time (2,
5 and 2 minutes).
Group Configuration.
Triads, three rounds, roles rotating. Every-
one together at the end.
Steps and Time Allocation.
•
Intro
(3 min.). Give the invitation: “Think of a change
you’re part of right now that isn’t going the way the plan
said. If nothing springs to mind, bring something you’re
159

=== page 172 ===

THE PIGEON TEST
watching others struggle with; it works just as well. We’re
going to help each other, and nobody is allowed to add
anything. Help has to make the thing smaller, take away
something that’s holding it back, or work out how you’d
notice whether it’s working. Everything else, keep to
yourself.” Then read the card aloud once.
•
Tellit
(3min.). In each triad, one person presents first. They
describe the change and say what’s happening, notwhythey
think it’s happening. The other two listen.
•
Three questions
(6 min.). The two helpers ask questions
only, the three on the card. A helper who catches themselves
about to suggest something keeps it to themselves, asks
one of the card’s questions instead, and remembers the
suggestion for the end.
•
Commit
(3 min.). The presenter names one probe, either a
smaller version of the change or something they’ll stop or
loosen. It has to be small enough to start without permission
and stop without a meeting. They also name the sign they’ll
watch for to tell whether it’s working, and the sign that
would make them stop it. No date, no promised end state.
Then they name somebody outside this room they’ll tell
about it.
•
Rotate
(24 min.). Two more rounds, roles rotating, so
everyone presents once.
•
The almost-saids
(7 min.). Everyone together. Ask: “What
did you almost say?” Go round the room: each person says
how many suggestions they swallowed, and names one. No
solving, no defending. Keep a running total where everyone
can see it, on fingers if there’s nothing else. Say the total
back to the room and ask: “What would have happened if
you’d said them?” Then say nothing.
160

=== page 173 ===

STRUCTURE #3: SMALLER THAN THAT
Call it fifty minutes with chair shuffling.
Practice Insights
Tips.
The ban is the structure, and when it slips the triad turns
into free consulting and the presenter leaves with homework
instead of a probe. The presenter may ask the helpers what
to do; the only answer the card allows is another question.
Watch for additions wearing question marks, because “have
you considered a retro?” is a suggestion. In Commit, the sign
that would make the presenter stop the probe often gets skipped
because it sounds defeatist. Hold the presenter to it.
Riffs and Variations.
For a group that has read this book, say what
the card is doing: “Every new practice, tool or framework is
another lever. The card stops anyone pulling one.”
Practical Applications.
Wherever a room has just seen a problem
clearly and is now hungry for a method. It works well straight
after Same Plan, Ten Times, with each presenter bringing a
dotted right-zone sticky from that wall that they’re part of.
Optional Liberating Structures String.
Reconvene with What,
So What, Now What once the probes have had time to show
something; suggest a fortnight, but let the group choose. For
a situation that needs advice rather than shrinking, hand it to
Troika Consulting, this one’s more generous sibling.
Where it came from.
Built on Troika Consulting, which runs the
same rotation without the ban. The rule that you can start a
probe without permission comes from 15% Solutions.
161

=== page 174 ===

17
Structure #4: Several at Once
Try several small experiments at once instead of picking one
(~60 min.)
What Is Made Possible
A challenge the group is stuck on gets a mix of small experiments,
instead of a meeting picking one solution and backing it. Every-
one’s private bet on which will work goes into a sealed envelope,
and at the reconvene the room can put what it expected next to
what happened.
Five Structural Elements (Min Specs)
Structuring Invitation.
Invite the group to pick a challenge it’s
stuck on and come up with several small, deliberately different
experiments to start at once. The wording is in the Intro step,
below.
162

=== page 175 ===

STRUCTURE #4: SEVERALAT ONCE
Space and Materials.
Chairs, index cards, pens, and an envelope
for each group. Somewhere to write the challenge sentence
where everyone can see it, and a flat surface for laying out cards;
the floor will do. One card per foursome with the four tests from
The tests step written on it.
Participation Distribution.
Everyone writes, tests and bets, and
anyone may end up owning an experiment, as long as it’s one
they can start without asking anyone. The facilitator writes up
the challenge sentence and keeps time, and leaves judging the
experiments to the four tests. Four people or more.
Group Configuration.
Everyone, thenalone, then pairs, thenfour-
somes, then everyone, with a moment alone for the envelope.
Steps and Time Allocation.
•
Intro
(3 min.). Give the invitation: “Think of a challenge
this group is stuck on. We’re going to come up with several
small experiments, as different from each other as we can
make them. We’ll meet again, probably in a fortnight or so,
to see what they’re showing us. Nobody picks a winner today.
At the end you’ll each write down, privately, which one you
think will work. That doesn’t decide anything, because they
all still run, but when we meet again we’ll see how good our
guesses were.”
•
The challenge
(5 min.). Ask the room to agree one sentence
describing the challenge it’s stuck on, and write it up. If
more than one challenge comes up, write each one up in a
different part of the room and ask people to go and stand by
the one they’re stuck on. With eight or more people, split
163

=== page 176 ===

THE PIGEON TEST
into one group per challenge that has at least four people
standing by it; anyone else joins their second choice. Each
group runs the rest of the structure with its own sentence,
spread and envelope. With fewer than eight, go with the
challenge that has the most people standing by it. Test
the sentence aloud: “Does it already contain a solution?”
“People are drowning in meetings” passes. “How do we get
everyone using the new system?” fails, because the new
system is already the answer. Rewrite until it passes.
•
Write alone
(5 min.). Each person writes as many experi-
ments as they can, one per index card, each starting “We
couldtry…”,each small enough to start. Range beats quality,
so include one you don’t quite believe in.
•
Pairs
(5 min.). Pool your cards. Merge true duplicates only.
Keep the strange ones.
•
The tests
(15 min.). Pairs join into foursomes and pool their
cards. Read each one aloud and run it through the four tests
on the foursome’s card: “Small enough that losing it costs
little? Fast enough to teach us something by the time we
meet again? Stoppable without a meeting? Would we notice
it working, or making things worse? If it fails a test, shrink
it until it passes, or bin it.” Put binned cards in a pile where
everyone can see them.
•
The spread
(7 min.). Everyone together. Lay all the surviv-
ing cards on the flat surface. Two volunteers build the spread
while the room watches, starting with the two cards most
unlike each other and laying out every other card between
them, nearer whichever it’s more like. Any two that turn
out to be the same experiment get merged. No votes, no
ranking. The only objection allowed is “Those two are too
alike.” If someone asks which is best, the answer is “Ask
164

=== page 177 ===

STRUCTURE #4: SEVERALAT ONCE
me when we meet again.”
•
The envelope
(3 min.). Alone, each person writes on an
index card the one experiment in the spread they privately
expect to work. Their own is allowed, and so is “none of
them”. Put the cards in the envelope and seal it. One person
keeps it, and it’s opened at the reconvene before anyone
reports.
•
Claim and watch
(7 min.). Every experiment in the spread
gets an owner who can start it without asking anyone, and
two signs: one that would say it’s working, and one that
would say it’s making things worse. Write the owner and
both signs on the card. Agree one reconvene date for all of
them. Suggest a fortnight, but let the group choose a date
by which every experiment could be showing something.
The reconvene isn’t a verdict; any experiment that isn’t
making things worse keeps running. Each owner names
somebody outside the room they’ll tell about it. No owner,
no experiment.
An hour with movement.
Practice Insights
Tips.
The challenge sentence is where this succeeds or fails, so
hold the room to the test. The four tests are pass or fail, and
a full bin means they’re being applied properly. If the spread
comes out samey, the room has used “too alike” to vote without
admitting it; split the merged cards back out. There is no dot
passhere, deliberately, because dots pick winners. Opened early,
the envelope turns into lobbying. A “none of them” card is a bet
like any other. At the reconvene, watch for the room treating
165

=== page 178 ===

THE PIGEON TEST
early results as final; a slow starter can look like a failure at the
first look. If nothing survives Claim and watch because nobody
can start anything without permission, stop, and spend the rest
of the session on why.
Riffs and Variations.
For a group that has read this book, point at
the spread at the end and say: “Nobody picked. The choosing
has moved from this meeting to what happens next, and the
envelope will show whether we’d have chosen well. A system
with plenty of variety can cope with conditions nobody saw
coming. One that picks a single answer only has that answer.”
Practical Applications.
Straight after Same Plan, TenTimes, when
one right-zone sticky is the one everyone’s stuck on. When a
stalled programme is about to be relaunched bigger.
Optional Liberating Structures String.
At the reconvene, open the
envelope first, then go through what happened with What, So
What, Now What.
Where it came from.
15% Solutions, for the rule that every
experiment has to be something its owner can start without
permission. The sizing comes from Chapter 7: each experiment
small enough that failure costs little, and enough of them that
some will land.
166

=== page 179 ===

18
Structure #5: Without Being Asked
Find where the talking already happens, and what keeps it
alive (~60 min.)
What Is Made Possible
Somewhere in this organisation, people already talk to each
other usefully without anyone arranging it. A group finds as
much of it as it can and works out what is keeping those places
alive. None of it was anybody’s idea, so none of it is in anybody’s
plan.
Five Structural Elements (Min Specs)
Structuring Invitation.
Invite the group to think about where
people in the organisation talk to each other usefully without
anyone organising it, and to work out what keeps that alive. The
wording is in the Intro step, below.
167

=== page 180 ===

THE PIGEON TEST
Space and Materials.
A wall with two zones marked in tape, left
and right, unlabelled. Sticky notes, pens, dot stickers in one
colour. Room for everyone to stand at the wall together.
Participation Distribution.
The whole room writes, sorts and dots.
The facilitator asks the questions and otherwise stays out of it.
Eight people up.
Group Configuration.
Alone, then pairs, then foursomes, then
everyone, then foursomes again.
Steps and Time Allocation.
•
Intro
(3 min.). Give the invitation: “Think about where in
this organisation people actually talk to each other usefully,
without anyone organising it. The corridor. The group chat.
The two teams who sort things out between themselves. The
person everybody rings. We’re going to find all of it, and
then work out what’s keeping it alive.” Point at the two
taped zones without explaining them. Before anyone writes,
say that some of what goes on this wall is happening in spite
of an arrangement somebody standing here made, and that
this is what we came to find.
•
Write alone
(5 min.). Each person writes places where
people talk usefully without being asked to, one per sticky.
Name the actual thing: who, where, aboutwhat. Notgeneral
words like “collaboration”. E.g. the Tuesday coffee, or the
two engineers who ignore the ticketing system and just ring
each other.
•
Pairs
(5 min.). Combine your stickies and keep the eight
most specific. One test before a sticky goes to the wall:
168

=== page 181 ===

STRUCTURE #5: WITHOUT BEING ASKED
nobody set this up. If somebody did, leave it off.
•
The sort
(14 min.). Pairs join into foursomes and take their
stickies to the wall. Ask: “If this organisation reorganised
next month, with new managers and new tools, would this
survive?” Left zone, would survive. Right zone, wouldn’t.
Two minutes for the contested ones, then they land. Draw a
line under any sticky that used the full two minutes.
•
Second pass
(8 min.). Still in foursomes, nothing moves.
Ask the foursomes to put one new question to every sticky in
both zones: “What is keeping this alive?” They’re looking
for what protects it, not who is in it. For example, somebody
senior who shields it, a budget nobody has noticed, a room,
a shared history, or the fact that nobody upstairs knows it
exists. Write the protector on the sticky. If they can’t name
one, itgetsadot. A do there means unprotected and nothing
more.
•
Stand back
(10 min.). Everyone. Ask: “What do you notice
about where the dots are?” Then set a timer for twominutes
of silence for everyone to think and write one thing they
notice on a sticky. Then go round the room, each person
reading theirs out, with no commentary.
•
Keep one alive
(8min.). Back into thesame foursomes. Each
foursome picks one dotted sticky. Ask: “What is the smallest
thing somebody here could do to make it more likely to
survive the next reorganisation, without formalising it,
naming it, funding it or putting it on a slide?” Name who
will do it, and that person names somebody outside this
room they’ll tell about it. No date.
An hour once people have shuffled about.
169

=== page 182 ===

THE PIGEON TEST
Practice Insights
Tips.
The nobody-set-this-up test keeps the wall from filling
with guilds and communities of practice, which are somebody’s
initiative and belong somewhereelse. Say twice that a dot means
unprotected rather than important, because the room will read
it the other way round the first time. Within about a minute
of the second pass, somebody will want to take one of these
places and roll it out across the organisation. Once it’s rolled
out, it’s an import like any other, and As It Arrived shows what
happens to those. If the room can’t name a protector for most of
the wall, it has found an organisation one reorganisation away
from losing most of the conversations it runs on. Encourage the
sticky somebody hesitates over; it’s usually the best one on the
wall.
Riffs and Variations.
For a group that has read this book,
give them Sami’s line from Chapter 7, “No interactions,
no progress”, then ask: “What keeps this organisation’s
interactions going?” The wall is the answer.
To come at thesame question from the opposite direction, run
Creative Destruction (TRIZ) instead: design the organisation
where nobody can usefully talk to anybody, go down the list
marking everything you already do, then stop one of them. It
works on a wall too. Build the design in one zone, then physically
move into the second zone everything that turns out to be true,
which lands harder than writing a second list. It’s a much harder
conversation than this one, so know your group before your each
for it.
Practical Applications.
Before a reorganisation is drawn, while
170

=== page 183 ===

STRUCTURE #5: WITHOUT BEING ASKED
there’s still time to draw it around these places rather than
through them. When somebody proposes a communications
workstream, or when two organisations are being integrated
and nobody has asked what the merger will step on.
Optional Strings.
Run it straight after Same Plan, Ten Times,
starting from whatever that structure’s last question found
working without a plan. Or take a dotted sticky into Liberating
Structures’ Discovery and Action Dialogue, so the people in it
can say what they do that keeps it going.
Where it came from.
It stands near Discovery and Action Dialogue
and Appreciative Interviews without being built on either. The
idea of going to look for what already works, rather than for
what is broken, belongs to the positive deviance tradition of
Jerry and Monique Sternin.
171

=== page 184 ===

19
Running Them Well
The room
Set it up before anyone arrives, the way the structure asks.
People who walk into the same layout as their last meeting
behave as if they’re still in it.
The moves
The set is built from the same handful of moves, so practising
one of them improves several. The escalation, alone to pairs to
foursomes, borrowed wholesale from1-2-4-All. The timeboxed
argument that then lands, with contested stickies marked so
the wall remembers what was fought over. The second pass,
where nothing moves and a new question gets asked of the same
stickies. The stand back, one question and then two minutes
of silence on a timer, with everyone writing before anybody
speaks. The claim, where somebody takes on one thing they can
do without permission and tells one person outside the room,
withnodate. And naming the exposure at the start rather than at
172

=== page 185 ===

RUNNING THEM WELL
the reveal, because some of the work on these walls was planned
or imported by people standing at them, and saying so in the
first minute is cheaper than repairing it in the last.
The sceptic
Somebody in the room did not choose to be there and thinks this
is a waste of a morning. Usually that person is an asset rather
than a problem. The sort questions reward their instinct, and
at a wall a cynic is usually the most accurate person present.
Smaller Than That asks for disclosure, but even there they can
bring something they’re watching somebody else struggle with.
The most senior person
Watch the most senior person instead. They’re usually the one
who most needs to hear what the wall says, and the one most
likely to stop it saying anything. Everyone’s stickies weigh the
same on the page; they don’t weigh the same in the room. So
talk to them beforehand. Ask them to write alone like everyone
else and to speak last when the room comes together. If they
start explaining the wall back to the group, go straight to the
stand back step. If they can’t manage any of that, run it without
them and show them the photograph of the wall afterwards.
Timings
The numbers on each step are what it takes when a room is
warm and nobody is being difficult, which is not most rooms.
Hold them anyway. The sort will always ask for more, and the
timebox makes it land. The overrun comes between the steps.
173

=== page 186 ===

THE PIGEON TEST
Moving people between pairs, foursomes and the wall costs a
minute or two every time, and the read-round at the stand back
costs ten seconds a head. Budget more than the page says and
expect to use it. If you are short of time, drop a structure rather
than compressing one, because a rushed sort produces a wall
nobody in the room believes.
Online
They work online, and online is often all you’ve got. But the
same holds here as for every Liberating Structure I’ve used.
Most of the magic happens in an actual room rather than a
Zoom room, and it’s worth some travel to get one. A wall works
partly through peripheral vision. You see where other people are
putting their stickies while you place your own, and the room
reads itself as it goes; a shared whiteboard gives you your own
cursor and not much else. Silence doesn’t survive a call either,
where a pause reads as a technical fault.
So tell the group what’s missing rather than pretending it’s a
straight swap, then compensate. Smaller Than That ports nearly
intact, with the card in each breakout’s chat. Several at Once
needs the envelope to become a form only the facilitator can
open. The three walls want a shared whiteboard with the zones
drawn on it and breakout rooms for the pairs and foursomes. Put
each step in writing before you send people out; they can’t hear
you in a breakout, and they forget the instruction on the way in.
When you reach the stand back, put a two-minute timer where
everyone can see it, say out loud that the time is for thinking
and writing, and mute yourself.
Afterwards
174

=== page 187 ===

RUNNING THEM WELL
Photograph the wall before anyone touches it, then again close
enough to read the handwriting. The dots and the contested
marks are the finding, and a wall peeled into a bin bag at five
past twelve takes the finding with it. Online, export the board
before anyone closes the tab. Several at Once needs the same
care: photograph the spread with every owner and sign readable
before people take their cards away, and keep the envelope safe,
since it’s the only record of what the room expected.
175

=== page 188 ===

A Note on Sources
This book draws largely on two things. The first is Samir Ri-
hani’s
Complex Systems Theory and Development Practice: Under-
standing Non-linear Realities
(Zed Books, 2002), and wherever
I’ve quoted or paraphrased Sami, the ideas are his and any
distortion in carrying them across to organisations is mine.
The second is my own practice, the courses, consulting and
years inside organisations, so the figures and stories from that
work, including the seven hundred experiments and how many
of them lasted, come from my own records and memory rather
than published research.
Works drawn on or mentioned along the way:
Beck, Kent, et al.
Manifesto for Agile Software Development
. 2001.
agilemanifesto.org
Dignan, Aaron.
Brave New Work: Are You Ready to Reinvent Your
Organization?
Portfolio, 2019.
Edmondson, Amy C.
The Fearless Organization: Creating Psycho-
logical Safety in the Workplace for Learning, Innovation, andGrowth
.
Wiley, 2018.
Gallup.
State of the Global Workplace
. Annual report series.
176

=== page 189 ===

A NOTE ON SOURCES
Glouberman, Sholom, and Brenda Zimmerman.
Complicated
and Complex Systems: What Would Successful Reform of Medicare
Look Like?
Discussion Paper No. 8. Commission on the Future
of Health Care in Canada, 2002.
Hamel, Gary. “First, Let’s Fire All the Managers.”
Harvard
Business Review
, December 2011.
Hamel, Gary, and Michele Zanini.
Humanocracy: Creating
Organizations as Amazing as the People Inside Them
. Harvard
Business Review Press, 2020.
Heffernan, Margaret.
Uncharted: How to Map the Future
. Simon
& Schuster, 2020.
Juarrero, Alicia.
Dynamics in Action: Intentional Behavior as a
Complex System
. MIT Press, 1999.
Kauffman, Stuart A.
At Home in the Universe: The Search for the
Laws of Self-Organization and Complexity
. Oxford University
Press, 1995.
Kauffman, Stuart A.
The Origins of Order: Self-Organization and
Selection in Evolution
. Oxford University Press, 1993.
Kegan, Robert.
In Over Our Heads: The Mental Demands of Modern
Life
. Harvard University Press, 1994.
Kniberg, Henrik, and Anders Ivarsson.
Scaling Agile @ Spotify:
With Tribes, Squads, Chapters & Guilds
. Crisp, 2012.
177

=== page 190 ===

THE PIGEON TEST
Kuhn, Thomas S.
The Structure of Scientific Revolutions
. 2nd ed.,
enlarged. University of Chicago Press, 1970.
Laloux, Frédéric.
Reinventing Organizations: A Guide to Creating
Organizations Inspired by the Next Stage of Human Consciousness
.
Nelson Parker, 2014.
Lipmanowicz, Henri, and Keith McCandless.
The Surprising
Power of Liberating Structures: Simple Rules to Unleash a Culture of
Innovation
. Liberating Structures Press, 2014.
Meadows, Donella H.
Thinking in Systems: A Primer
. Edited by
Diana Wright. Chelsea Green Publishing, 2008.
Minnaar, Joost, and Pim de Morree.
Corporate Rebels: Make Work
More Fun
. Corporate Rebels Nederland B.V., 2020.
Nicolis, Grégoire, and Ilya Prigogine.
Exploring Complexity: An
Introduction
. W. H. Freeman, 1989.
Pascale, Richard, Jerry Sternin, and Monique Sternin.
The Power
of Positive Deviance: How Unlikely Innovators Solve the World’s
Toughest Problems
. Harvard Business Press, 2010.
Reynolds, Craig W. “Flocks, Herds, and Schools: A Distributed
Behavioral Model.”
Computer Graphics
, vol. 21, no. 4, 1987, pp.
25–34.
Rihani, Samir.
Complex Systems Theory and Development Practice:
Understanding Non-linear Realities
. Zed Books, 2002.
178

=== page 191 ===

A NOTE ON SOURCES
Robertson, Brian J.
Holacracy: The New Management System for a
Rapidly Changing World
. Henry Holt and Company, 2015.
Semler, Ricardo.
Maverick!: The Success Story Behind the World’s
Most Unusual Workplace
. Century, 1993.
Snowden, David J., and Mary E. Boone. “A Leader’s Framework
for Decision Making.”
Harvard Business Review
, vol. 85, no. 11,
November 2007, pp. 68–76.
Snowden, Dave, and Alessandro Rancati.
Managing Complexity
(and Chaos) in Times of Crisis: A Field Guide for Decision Makers
Inspired by the Cynefin Framework
. Publications Office of the
European Union, 2021.
Stacey, Ralph D.
Strategic Management and Organisational Dy-
namics: The Challenge of Complexity
. 6th ed. Pearson, 2011.
Taylor, Frederick Winslow.
The Principles of Scientific Manage-
ment
. Harper & Brothers, 1911.
Waldrop, M. Mitchell.
Complexity: The Emerging Science at the
Edge of Order and Chaos
. Simon & Schuster, 1992.
179

=== page 192 ===

Over to You
If you’d like to try the book’s question on something real, the
Pigeon Test tool is free at thepigeontest.com/tool, and it will
help you work out whether the problem in front of you is a ball
or a pigeon before anyone starts pulling levers.
The structures in the appendix are yours to run without me.
If you’d rather have someone in the room who doesn’t work
there, I facilitate them with groups, and you can reach me at
thepigeontest.com.
And if this book has been useful to you, or has annoyed you in a
useful way, a short review on Amazon or wherever you bought it
helps it reach the readers it was written for. I’d especially value
one from anyone who came to it sceptical and is willing to say
where it changed their mind and where it didn’t.
Thanks for reading,
Mark
180

=== page 193 ===

About the Author
I was born in Accrington and grew up in Clitheroe, Lancashire,
and despite the county and the book title, I’m not a pigeon
fancier, which in my part of the world means breeding and racing
pigeons while talking about very little else. So I’m from the hills,
but home is now Bristol, where I live with my partner Ysatis, our
dog Nico and our daughter Aoife, who was just one when this
book went to print. It’s my ninth and last city before I excitedly
return to the hills, hopefully one day soon. Our happy place is
camping in a farmer’s field in Devon.
I studied Politics at the University of Liverpool, where I was
taught by the wonderful Samir Rihani. I then spent a decade
in the charity sector and government before a law firm in
Wellington, New Zealand, introduced me to self-management
in 2015. Two more self-managing organisations followed. I
co-founded Reinventing Work, a meetup that started in Bristol
and ran in twenty-five cities across five continents, then built
a consulting and training practice cheerleading new ways of
working, with clients including Pfizer and the United Nations.
In an old version of my bio, I wrote that once you taste this way
181

=== page 194 ===

of working, it’s impossible to go back. This book is what going
back looks like.
