Communication

Email Signals

Clarity in the address line is clarity in the organisation.

An email is a meeting you run without leaving your desk. The sender sits at the head of the table, deciding who joins. Those in the “To” line are seated alongside, expected to listen closely and sometimes speak. Those in “CC” are chairs against the wall, present for awareness but not meant to drive the conversation. “BCC” is the hidden observer behind the glass. Mix the seating, or fail to make the roles clear, and the meeting collapses into noise before it begins.

Email underpins almost every organisation, but most people were never taught how to use it well. The result is cluttered inboxes, blurred responsibilities, and wasted time. The mechanics are simple. The intention often is not.

The “To” line signals priority. Sometimes it means act, sometimes it simply means pay attention, this matters. What matters is clarity. If you mix those who must act with those who are only being informed, and then fail to specify which is which in the body, you have created a problem for everyone. In practice, everybody’s problem means nobody’s problem.

“CC” stands for carbon copy, a hangover from the days when typing on paper with carbon sheets produced duplicates for record-keeping. The copy was never for the person to act on. It was for awareness. That is the spirit CC still carries today. At best, it keeps people in the loop. At worst, it turns email into theatre, with long lists of copied names adding no clarity. Many leaders now filter CCs into a separate inbox, treating them as background noise. If they go unread, that is not failure. It is triage.

“BCC” means blind carbon copy. On paper, the duplicate was created but invisible to others. In email, it serves the same purpose: protecting the privacy of a long distribution list, or looping someone in without signalling to the wider group. Used well, it is efficient. Used badly, it looks like secrecy. The difference between discretion and distrust is rarely visible in the moment, but it always colours how a message is received.

How we reply matters as much as who we write to. Top-posting, replying above the quoted thread, became the default. It keeps responses quick but often lazy, with long chains of untrimmed history burying the point. Better to cut the noise: quote only what is needed, and place answers where they add clarity. Every unnecessary screen of scrolling is another tax

Most email missteps do not come from malice. They come from good intentions and a lack of training. In large organisations, a simple act, choosing who belongs in “To,” who belongs in “CC,” and who does not need to be copied at all, can go a long way. As with Shouting in the Digital Office, this is about respect for others’ time and space to do deep work. Each clear signal reduces noise, and the compound effect is organisational focus.

Clarity is not just who you address but what you write. If it takes three exchanges to explain, sometimes the faster and kinder move is to pick up the phone. Not every problem belongs in an inbox. The choice of medium is as much a signal of respect as the choice of addressees.

Continue from here

Follow a related thread.

These essays continue the same argument.

Latest in this thread

Sweating the Bar and Raising the Details

Management meetings were built for an older information system. Poor writing keeps the machinery alive, and one calendar invitation can commit thousands before anybody acts.

5 min read · Communication

Show Your Working

Why visible fixes build knowledge, demonstrate competence, and strengthen trust.

2 min read · Communication

Signs Worth Reading

The backlog whispers, source control mumbles. Somewhere in between, the product gets built.

4 min read · Communication

Continue from here

Follow a related thread.

Selected automatically from shared topics, newest first.

Latest related essay

The Coordination Tax in Your Software Estate

Repository fragmentation turns shared work into internal transactions. Pricing those transactions reveals opportunities to move faster, release capacity and simplify control.

5 min read · Monorepo

Faux InnerSource

A contribution process is not InnerSource merely because another team can submit code. The test is whether repeated contributions build reusable engineering capability or repeatedly enter the same queue.

7 min read · InnerSource

Sweating the Bar and Raising the Details

Management meetings were built for an older information system. Poor writing keeps the machinery alive, and one calendar invitation can commit thousands before anybody acts.

5 min read · Communication

Browse by question

What are you trying to decide?

Find an argument

Search the shelf.

Search all published essays by title and standfirst.

New arguments, occasionally

Worth sending.

No cadence theatre. No filler. Just new essays when the argument is ready.