Nobody Used the Suggestion Box. Then He Moved Three Chairs.

Before the chairs, three things had already failed.

In Chapter Six, David has finally got the diagnosis right. He has spent a fortnight filling a journal with patterns, and he can name what each person on his team actually needs. Jason needs creative ownership rather than firefighting. Zoe needs foundational stability rather than rushed deadlines. Linda needs strategic wins rather than excuses. The team, as he puts it, needs psychological oxygen.

Knowing that turns out to be worth very little.

His first attempt is evidence. He builds Linda a structured case showing how rushed releases damage long-term quality — the sort of analysis that ought to end an argument. She reads it and calls it “a beautifully packaged excuse.”

His second attempt is relief. He goes and removes some of the small bottlenecks that have been grinding the team down. They shrug. The book's explanation of the shrug is the part worth sitting with: they were too burned out to trust the gesture.

His third attempt is the one almost every organisation reaches for. He puts out an anonymous suggestion box.

It fills with jokes. “Can we get a time machine?” “Fix the system, not us.”

Three interventions, three entirely different mechanisms — proof, relief, anonymity — and three failures. I have watched all three fail in real organisations, usually in that order, usually by someone competent who genuinely wanted the answer.

The Sentence That Changed the Method

Rajiv, hearing all of this on their next call, laughs at him.

“You're still playing by the old rules,” he says. “Stop asking permission to do the right thing. Create realities where the right thing is impossible to ignore.”

That last sentence is the hinge of the chapter, and it is easy to read as motivational when it is actually procedural. It is not telling David to be braver. It is telling him that he has been trying to change what people feel, when he should have been changing what the room makes possible.

Three Chairs

The test arrives at an ASEAN planning session the following week.

It is the sort of meeting everyone reading this has sat in. A crowded conference room. Senior leaders speaking over one another. Slides moving faster than anyone can absorb. VPs defending regional agendas as the conversation heats up.

And at the edge of the room, three junior analysts. Attentive, absorbing everything, contributing nothing.

David watches them and something tightens, because he remembers being that person, sitting quietly while the real decisions were made somewhere in the middle of the table.

Then, without warning, he stands up, walks to the empty space at the side of the room, and drags three chairs forward.

The room falls silent. The VPs look at him as though he has briefly lost his mind.

“Before we finalize anything,” he says, “I want to hear from the people who haven't spoken yet.” He gestures at the analysts. “Your turn.”

For a moment nobody moves. The seniors are irritated. The juniors are terrified.

Then the first analyst clears her throat and starts — halting, then steadier — and points at a compliance flag buried so deep inside a minor workflow document that the room gasps.

The second describes a peak-load scenario none of the senior leaders had considered: an infrastructure failure waiting to happen.

The third offers a small interface change that would cut manual support contacts by double digits.

The strategic direction of the meeting changes. A multimillion-dollar compliance risk is avoided. Processes get rewritten. By the end, the VPs are thanking the analysts, and one of them asks for their notes.

The book's own summary of what happened is the line I would put on a wall. Silence in the room wasn't absence of insight — it was absence of invitation.

Why the Suggestion Box Was Always Going to Fail

Go back to that box for a moment, because its failure is more instructive than the chairs' success.

Anonymity is offered as protection, and it does protect. The difficulty is what it costs on the way.

An anonymous concern arrives stripped of the thing that makes a concern usable — who saw it, in what context, and what they would do about it. You cannot ask a follow-up question of a note. The compliance flag that analyst found was not a sentence. It was a sentence, then four more in response to “where exactly?”, then a document reference. None of that survives the box.

And there is a harder problem underneath. An anonymous channel is a public statement that saying this openly is unsafe. It does not repair that; it confirms it, then institutionalises it. The box is evidence of the culture, not a treatment for it.

Which is why the jokes were the honest answer. A team that has already concluded nothing will change will use the only safe register available to say so.

Some of the Silence Is Mechanical

There is a finding here I did not expect to be as relevant as it turned out to be.

In 1987, Michael Diehl and Wolfgang Stroebe published four experiments in the Journal of Personality and Social Psychology on a puzzle in group creativity. The comparison is between real groups working together and what researchers call nominal groups — the same number of people, working separately, their ideas pooled afterwards.

Of the twenty-two experiments they tabulated from earlier work, eighteen found the separated groups produced more ideas than the interacting ones.

Their fourth experiment went after the cause, and landed on something unglamorous: production blocking. In a real group only one person can talk at a time. Everyone else waits. And while you wait, you forget the thing, or it starts to sound less relevant than it did, or the conversation moves and the moment for it closes.

A laboratory brainstorming task is not an ASEAN planning session, and I would not push the comparison further than it goes. But the mechanism travels, and it travels worst in exactly the meeting David was sitting in: crowded, fast, senior voices competing, slides moving.

What it means practically is that some of the silence in your meetings is not fear and it is not disengagement. It is queueing. People with something to say are losing it while they wait for a gap that never widens.

That is worth knowing because encouragement does nothing whatsoever about queueing. “Speak up if you have anything” is addressed to a person's confidence. The problem is in the traffic.

The Version I Know From Engineering

The equivalent I have watched most often is a design review or an FMEA workshop.

The room is full of senior technical people, and the agenda is long. The person who actually runs the process being assessed — who knows precisely which step goes wrong on a wet Tuesday when the line is behind — is usually in the room, usually at the end of the table, and usually gets the least airtime of anyone present.

Nobody is silencing them. The meeting is simply built so that the people with the most formal seniority absorb the available speaking time, and the failure mode that actually bites is the one held by somebody whose turn never came.

What Actually Transfers

The chair in this scene is not a metaphor. That matters more than it sounds, because metaphors are easy to agree with and hard to implement.

What made it work was three properties, and any mechanism with the same three will do.

It was public. The opposite of the box. The junior analysts were heard by the same VPs whose agendas their findings complicated, which is the only way a finding actually changes a decision.

It was specific. Not “does anyone have anything to add?”, which is an invitation addressed to nobody and reliably answered by nobody. He gestured at three named people and said “your turn.”

It happened before the decision. Input gathered after a direction is set is a courtesy. Input gathered before it is set is the only kind that can change anything — and people can tell the difference, which is most of why they stop offering.

The Part I Keep Coming Back To

He did not ask anyone's permission to move the chairs.

There was no proposal, no pilot, no approval to run a new meeting format. He stood up in a room full of people more senior than him and rearranged the furniture, and the book's description of what followed is almost offhand: he practised it until other people imitated it.

That is the quiet argument underneath the whole scene. Most of what we want to change about how our organisations behave does not actually require authority. It requires someone willing to be briefly strange in a meeting.

David writes the line in his notebook on the walk back to his desk. Silence is a leadership failure.

I would only add the part that makes it useful rather than merely true. It is a failure of design, not of nerve — and the people it fails are rarely the ones being asked to fix it.