Your Managers Are Not a Distribution List

If a rule governs thousands of people, its owner should not whisper it through the organisation chart.

Consider a common failure, generalised from experience. In a large organisation, urgent work was delayed because a team waited for a control that the policy did not require. The case was resolved, the policy clarified and the lesson considered important enough to share widely.

It was sent to a few dozen senior people with an instruction to cascade it through the organisation.

Thousands of people needed the authoritative answer.

This is how a modern company communicates when it has mistaken hierarchy for infrastructure. The policy owner tells a group of leaders, who tell their leaders, who tell their managers, who mention it during a weekly meeting to whichever employees have not taken leave, changed role or lost consciousness. By the time the message reaches the person doing the work, it has acquired local interpretation, lost inconvenient detail and become impossible to trace to its author.

If it reaches them at all.

The alternative is not louder communication. The owner should publish one authoritative message where the affected audience can find it, usually without tagging anybody. Rules used repeatedly should be enforced or presented in the workflow wherever possible. Managers add local context where it helps.

Publish broadly enough to establish one truth. Notify narrowly enough to protect attention.

Why Cascades Fail

The cascade made sense when communication was scarce. A chief executive could not address ten thousand people directly, so instructions travelled through the chain of command. The organisation chart was the communications network.

Large companies now have distribution lists, announcement channels, searchable intranets and systems that can target the people affected by a rule. The owner can write once, publish to the right audience and answer questions at the source. Corrections remain attached to the original. New colleagues can find the decision later. Nobody has to reconstruct official policy from a screenshot of something their manager remembers being told on a call.

Yet we continue to cascade through several layers. Nobody can say with confidence whether the final audience received the message, understood it or can find it later. The policy owner knows who received the first version, not who received the last or what it said when it arrived.

Owning a policy means ensuring that the people governed by it can find, understand and apply it. Sending it to one's peers with an instruction to pass it on retains authority while outsourcing delivery.

We would not accept a message bus in which every node rewrote the payload and delivery could not be observed. Nor would we declare an incident fixed because the first service had acknowledged it. In corporate communication, this architecture is called alignment.

A field study of enterprise social networking suggests that visible conversations can help colleagues discover who knows what, learn from exchanges they did not join and avoid duplicating work. A public exchange leaves useful knowledge. A cascade leaves only the last retelling.

Direct Does Not Mean Loud

I have argued before that shouting in the digital office destroys attention. The answer to a bad cascade is not an indiscriminate @channel, or its nervous cousin @here.

Direct communication means publishing at the source, not interrupting everybody at once. The owner should post in the channel used by the affected audience, say who is affected, explain what changed and link to the authoritative detail. People can read it when convenient unless they must act now.

Use @channel only when every member of the channel needs timely information or action. Use @here when an immediate response is needed from somebody active now, most plausibly during an operational incident. Neither tag makes an ordinary announcement more important; it merely makes the interruption harder to avoid.

For everything else, publish the message and leave the siren alone.

People sometimes forget to post directly, do not know which channel to use or feel uneasy addressing thousands of colleagues. A large audience makes every imperfect sentence feel permanent. Give owners clear announcement channels, sensible guidance and help with consequential messages. Do not replace one nervous author with several layers of unreliable couriers.

Questions whose answers would help others belong beside the original message. Managers may explain how the rule applies locally or notice that somebody has misunderstood it. That is useful leadership, not a substitute for direct publication.

The owner publishes the rule. The system preserves the authoritative version. Managers explain local consequences and handle exceptions. Context enriches the source; it does not replace it.

A Channel Must Deserve Attention

Direct publication fails if the chosen channel has become a corporate attic. Once every initiative, survey, celebration and amended expense policy is declared important to everybody, nothing in the channel is important to anybody. People mute it, skim it or rely on colleagues to tell them when something real has happened. We have recreated the cascade as a coping mechanism.

This is the serious counterargument to publishing broadly. A survey of enterprise social-media users found that information overload was associated with strain, and that greater visibility strengthened the relationship. A workplace study of notifications found the trade-off in miniature: alerts create awareness but disrupt the task already under way.

The answer is editorial discipline. Choose the smallest audience that includes everyone governed by the message. Use a channel with a clear purpose. Keep the post short, link to durable detail and state whether action is required. Do not use an engineering announcement channel for executive tourism, motivational wallpaper or news that belongs in the canteen.

A useful channel earns attention by refusing most of what people would like to put in it. If leaders fill it with material that does not concern its audience, they cannot complain when the one consequential message disappears into the upholstery.

Put the Rule Where the Work Happens

There is a more important question than who should send the correction: why did thousands of people need to remember the rule during urgent work?

Where a rule can be enforced safely, put it in the workflow. If an emergency change does not require an approval, the emergency process should not request one. If a repeatable security check is mandatory, the tooling should run it. Where judgement remains necessary, show the current rule, its owner and the route to an exception at the moment of need.

The workflow should enforce what is mechanical and present what requires judgement. It must agree with the written policy, or the company will possess one rule in prose and another in software.

An announcement corrects what people know. A well-designed workflow changes what happens next.

Establish the authoritative rule, then correct the affected audience at once if people might otherwise continue doing the wrong thing. Reflect the rule at the point of work, publish the completed change and notify only those who must act now. Managers can then reinforce it where local context helps.

Most organisations begin with the reinforcement and wonder why the incident repeats.

Leaders Must Own the Words

The duty to make consequential reasoning discoverable grows with seniority. A Principal Engineer's explanation may guide several teams; an executive policy may govern thousands. The wider the effect, the less defensible it is to leave the reasoning inside a private meeting and appoint the hierarchy as courier.

Writing reveals whether an instruction can stand without its author in the room. A vague proposal can survive a meeting because everybody leaves with a different interpretation and calls the gathering a success. Writing makes the owner choose the words and confront the exceptions.

This is one reason meetings and cascades remain popular. One can arrive at a meeting without having decided exactly what one means. A written announcement is less accommodating. It leaves evidence.

Some subjects belong in private: personal circumstances, individual performance, confidential investigations and information restricted for a real reason. A rule governing how thousands of engineers should perform their work does not.

Stop Cascading and Start Owning

The cascade persists because it flatters the organisation chart. Every layer receives something to repeat, while the original owner can believe the message is moving without discovering whether it arrived.

Publish the authoritative message to the people it governs. Enforce or show repeatable rules in the workflow. Use managers for context and judgement, not distribution.

Own the rule, the words, the audience and the mechanism by which it becomes true.

Please do not cascade this message.