The Town Hall That Was Cancelled

The Architect’s Essays · No. 0

An essay on why an organization cannot stay silent.

A chief executive has a restructuring on the table. Two units will probably merge. Nothing is final and the numbers are still moving. The quarterly town hall is ten days away, and the advice is unanimous and sensible: do not stand in front of four thousand people with half an answer. Say nothing until there is something to say. So the town hall is cancelled. The calendar invitation disappears on a Tuesday afternoon with no explanation, because any explanation would itself be a statement.

By Thursday, the organization has held its town hall anyway. It just didn’t invite the chief executive.

Hold onto that cancelled meeting. It shows the principle every other part of this work stands on more clearly than anything else. It also shows the error almost every leadership team makes about that principle, usually on the best advice money can buy.

If you take nothing else from this: an organization has no off switch for communication. Leadership can choose whether to design it, but not whether it happens. The communication nobody designed still builds the organization.

That is axiom 0: all is communication. It sounds like a slogan, but it works the other way. A slogan asks for more of something. This one says where to look.

The model everyone runs

Ask a leadership team what communication is and they will describe a pipe. Decisions are made upstream, in rooms, by people with authority. Communication carries them downstream to the people who need to know. It can be done well or badly, clearly or vaguely, on time or late, but it always comes second. First the organization decides and acts; then it communicates. That is why “we’ll communicate when we have something to say” sounds like discipline rather than a gamble.

The pipe model is why the town hall was cancelled. If communication is transport, an empty truck should not leave the depot. Nothing sent, nothing received, nothing damaged.

The model is wrong at the center, not at the edges. The truck never carried the message. The cancellation did.

What the silence said

Researchers of human interaction, working out of psychotherapy, stated it in 1967 as a tentative axiom: when people are in each other’s presence, one cannot not communicate. Silence, delay and withdrawal have consequences. They do not have a fixed meaning. That second part should worry a leadership team most, because when the sender declines to supply the meaning, the receivers supply it themselves.

So the cancelled town hall was read. One unit read it as confirmation: it’s happening, and it’s bad. Another read it as contempt: they don’t think we are owed an explanation. A third read it as confusion: they don’t know what they are doing. Each reading was plausible, and the person who cancelled the meeting chose none of them. The one thing the chief executive did control, whether to speak, produced exactly what the silence was meant to prevent: four thousand people interpreting a half-finished plan without the plan in front of them.

Watch it build

The deeper effect is not the rumor. It is what the rumor builds.

A person. The best engineer in the unit expected to merge takes a recruiter’s call she has ignored for a year. Nothing has been decided about her, but she has made a decision about the organization.

A team. Two teams on either side of the rumored boundary stop lending each other people. Nobody gave an instruction. Coordination redraws itself around a line that exists only in what people now say to each other.

The organization. Within three weeks there are two organizations. One is on the chart, unchanged, waiting for an announcement. The other has already reorganized itself: who is in, who is on the way out, who still gets the difficult call, who can be trusted with what. Researchers of organizational communication describe exactly these processes (membership, structuring, coordination and external positioning) as the flows through which an organization is continually produced. The flows kept running. Leadership had simply stepped out of them.

The market. A supplier’s account manager hears it from a site lead and adjusts a renewal. A candidate turns down an offer. The company’s position outside is renegotiated in conversations it will never see.

The structure is the same at every size. A person reads the silence and acts. A team coordinates around what it hears informally. An organization rebuilds itself through the flows left running, and the people around it adjust. When the plan is finally announced, the organization it was written for has already been replaced by the one the silence produced.

The trap inside the trap

The careful leader has already learned this lesson, or believes so: never go silent, communicate early and often. So next time there is a weekly update, an FAQ, a dedicated channel and a pulse survey. Volume goes up. The organization still drifts, because the careful leader has made the opposite mistake and confused communication with messages.

Luhmann drew the distinction precisely. What reproduces an organization is not how much is said. It is communication that connects, above all decisions communicated in a form later decisions can build on. A weekly update saying “the steering group continues to evaluate options” is communication about the absence of a decision. Nothing connects to it. Each week it confirms again what the cancelled town hall confirmed: what matters is happening somewhere else.

So there are two ways to lose control of what the organization becomes. Silence hands the building work to the corridors. Noise without decisions also hands it to the corridors, with a newsletter attached. Either way, the communication that builds the organization is the one nobody designed.

What it costs

Look at how the aftermath gets diagnosed. The engineer’s resignation is a retention problem. The teams that stopped sharing are a culture problem. The supplier is a commercial problem. The slow steering group is a governance problem. That makes four problems with four owners and four budgets, each treated separately. Each treatment misses, because these are not four problems. They are one decision, to treat communication as transport, showing up at four sizes. Each owner will do competent work on the wrong problem.

That is the price of the pipe model. It is not one bad message. It is one misdiagnosis, repeated at every scale and paid for four times.

What to do instead

Start from the axiom, not the pipe. The organization is always communicating, and the only question is what. Before any significant change, the question is not “when do we communicate?” It is “what is the organization already saying, through what it does and doesn’t do, and what will that build if left alone?”

Then design three things:

• What will be said, and by whom, especially when the answer is incomplete. “Nothing is decided; here is what is known and when the rest will be” is a statement. A cancelled meeting is a verdict.
• Which decisions will be made and communicated so that people can build on them, rather than reinterpreting the silence every week.
• Which daily practices will say the same thing as the words: who is hired, who is consulted, who still gets called. When practice and words disagree, practice wins.

None of this is about talking more. It is about recognizing that there is no neutral position to retreat to. The choice was never between communicating and not communicating. It was between building the organization on purpose and letting it be built by default.

The town hall was cancelled so that nothing would be said. Everything was said, and the only voice missing was the one that had cancelled the meeting.