Chain of Command

See it in action

What it is

Chain of Command is a deceptively simple line-up game. The whole team stands single file on a narrow “log” — a strip of material, a crack in the sidewalk, two lines of tape — everyone facing the same way, each person staring at the back of the head in front of them. Then comes the catch: without talking, without turning around and without stepping off, they have to rearrange themselves into a specific order the facilitator names. Birthdays. Middle initials. Hair length, darkest to lightest. Distance travelled from home. The order changes; the constraints never do.

It usually starts as an icebreaker and quickly becomes something more. Within a minute the group discovers that the person who instinctively stepped to the front — the natural leader — is now facing away from everyone and can’t see a thing, while the quietest person at the back has the only clear view of the whole line. That single twist is what makes Chain of Command punch so far above its weight.

How it works

The team lines up in random order on the log, all facing one end. The facilitator gives them an order to sort into — say, by date of birth — with three rules: no talking, no turning around, and no stepping off. If anyone touches the ground, the whole group starts over. Once they crack it, the facilitator simply names a new sorting rule and the scramble begins again. A wrapped storyline (you’re a spy team learning to read each other’s minds in cramped quarters) adds fun, and the close quarters make this one of those rare activities that gets people comfortably into each other’s space. (Full step-by-step setup, storyline, sorting prompts and debrief questions are in the downloadable guide below.)

What it reveals: communication

A single-file line is a terrible communication network, and that is exactly the point. You can talk easily to the one or two people beside you, but the person six spots up the line might as well be in another building — and you can’t even use words. So the group fractures into little clusters of three or four, each solving its own local piece of the puzzle, and somehow the whole thing gets sorted. It works, but it was left almost entirely to chance. The question that lands in the debrief writes itself: where else are we leaving important communication to chance? When information in an organization only travels a few desks in either direction and the rest is left to sort itself out, that is not organizational strength — it is happenstance dressed up as a system.

What it reveals: leadership and change

Chain of Command builds a leadership paradox right into its rules. The people most eager to lead go to the front, because that is where leaders go — but facing forward and unable to turn, the front of the line can do nothing but follow. The person with the best view of everyone is stuck at the back, and whether they step up — and whether the group lets them — is one of the richest things to watch. Then the facilitator changes the sorting rule and the whole calculus resets. Leadership has to move: sometimes by group decision, sometimes because someone simply starts leading. Teams that cling to the first person who took charge stall out; teams that let the right person lead for this task, from this position fly. It is a live demonstration that leadership is a role the situation assigns, not a seat somebody keeps.

What it reveals: trust and shifting perspective

Because no one may step off the log, sorting into a new order means physically letting teammates edge past — giving up personal space and accepting a little contact with people you may barely know. That small act of allowing someone into your space is the seed of trust, and doing it to reach a shared goal is what makes it stick. Meanwhile every reshuffle literally changes what each person can see. A perspective that made you the most useful voice a moment ago can vanish on the next round, and the group has to notice who can see clearly now — and hand them the wheel. Great teams do this instinctively; struggling ones keep listening to whoever was right last time.

Interesting things to watch for

• Who steps to the front — and how it feels for them to realize the front of the line is powerless to lead.
• Whether the group notices that the person at the back has the best view, and whether they actually let that person lead.
• How the line breaks into small clusters each solving their own piece, and whether anyone tries to connect the clusters.
• How leadership shifts — or fails to shift — the moment the facilitator changes the sorting rule.
• Who is fuelling the fun, and who quietly disengages when the close proximity or the constraints get uncomfortable.
• How much the team plans before moving versus diving straight in, and whether a quick huddle would have saved a dozen false starts.

Variations

• Blindfolds. Blindfold some or all participants, at random, and lift the impairment only when you choose — frequent blindfolding and un-blindfolding creates a chaotic scramble that groups tend to find even more fun.
• Enforced silence. Randomly “silence” some or all of the team (hospital face masks work well, and land especially hard with medical groups) so they lose even their non-verbal shortcuts.
• One-legged. Tell some or all participants they may now only stand on one leg — and take that away again at will.
• Two groups. Split a large group in two and run them side by side. You never have to say “race” — they will compete instantly, even though, facing sideways, they could actually see more and help each other if they chose to cooperate.
• Beat the clock. Time the first attempt, ask “can you do it faster?”, then change the sorting rule on them — a pointed reminder that life keeps asking for something different in the same amount of time.

Who it's for

Chain of Command suits groups of roughly 8 to 16, indoors or out, and needs almost no equipment. It works beautifully as an opening icebreaker for a group that doesn’t know each other yet, and just as well as a pointed conversation-starter about leadership, communication and adapting to change for an intact team. Reach for it when you want a low-setup, high-insight activity that gets people talking — and moving — fast.

Questions to spark the debrief

The activity is the vehicle; the debrief is where the lesson lands. Questions we ask:

• How much pre-planning did you use — or need?
• Was a leader identified? If so, why that person, and did leadership stay put or move around?
• What strategies emerged that actually proved helpful?
• What new things did you learn about each other through this?
• Where do you see similarities between this line-up and how you communicate and lead at work?

Frequently asked questions

How many people is Chain of Command for?
Chain of Command is built for 8–16 people. We can scale the setup up or down to fit your group.

How long does Chain of Command take?
Allow about 45–60 min (incl. debrief). Most of the real value comes from the debrief that follows.

Can Chain of Command be run indoors or outdoors?
Indoor and outdoor.

What does Chain of Command teach a team?
It focuses on change, communication, critical thinking, ice breaker and problem solving, and the debrief connects what happens in the activity directly to how your team works day to day.

Is there a free guide for Chain of Command?
Yes. You can download a free step-by-step facilitation guide (PDF) for Chain of Command from this page and run it yourself.

Want a facilitator to run Chain of Command for your team? Explore our team building experiences and ongoing programs.