Something that comes up in almost every communication session we run: the silent BCC. Everyone’s seen it used. Most people have done it. And almost no-one has stopped to ask what message it actually sends.

We’ve all been there. You send an email to a colleague raising a concern about a project. The reply comes back, reasonable enough. What you don’t know (what you can’t know) is that your colleague just forwarded the whole thread to your manager. Or worse, they BCC’d them on the original response. You’re having what you thought was a direct conversation. In reality, someone else has been watching from the shadows the whole time.

Welcome to the email BCC problem.

What BCC was designed for.

Blind carbon copy (BCC) was a genuine innovation when email arrived. It was a way to loop in a third party without cluttering a recipient list, or to protect privacy in bulk sends. You BCC the whole mailing list so strangers can’t harvest each other’s addresses. Sensible. Useful. Boring.

That’s not how it gets used in most workplaces. In most workplaces, BCC is a surveillance tool with a veneer of plausible deniability.

Think of it like a one-way mirror in an interrogation room. The person being questioned thinks they’re in a private conversation. The observers on the other side have a completely different view. There’s nothing wrong with the conversation itself, but the dynamic is built on asymmetric information. That asymmetry is the point.

“In most workplaces, BCC is a surveillance tool with a veneer of plausible deniability. And we’ve all stopped noticing.”

The passive aggressive architecture of it.

Here’s what makes BCC specifically passive aggressive rather than just sneaky: it allows the sender to maintain the fiction of a direct, honest exchange while simultaneously undermining it. They’re not lying, exactly. But they’re not being transparent either. They’re having their cake (the appearance of open communication) and eating it too.

Passive aggression, at its core, is indirect hostility. It’s the difference between saying “I disagree with this decision and here’s why” and quietly ensuring someone senior knows about it without that conversation ever happening.

BCC is the digital architecture of avoidance. It lets people act on a concern, or register a complaint, or cover their backs, without ever having to own it.

And it works. That’s the problem. It works precisely because nobody knows it’s happening. The recipient can’t respond to being watched. They can’t address a concern that was never raised. They just wonder why the atmosphere changed.

The psychological safety cost.

Amy Edmondson’s research on psychological safety is clear: people perform better, speak up more, and take more creative risks when they believe they won’t be punished for doing so. The core ingredient is trust; specifically, trust that your words won’t be weaponised.

BCC corrodes that trust at the root. Not dramatically. Quietly. The way damp gets into a wall before you see any damage.

If people in your organisation suspect (even occasionally) that their emails might be seen by someone who wasn’t supposed to be reading them, they start self-censoring. They hedge. They choose the safe option over the honest one. They stop raising difficult things in writing, which often means they stop raising them at all. The organisation loses access to exactly the information it most needs: the stuff that’s hard to say.

Ironically, the people who rely on BCC most are usually trying to protect themselves from precisely this kind of dynamic. “I need a record.” “I want someone to know what I’m dealing with.” These are the symptoms of an environment where people don’t feel safe being direct. BCC doesn’t fix that. It deepens it.

So, what’s the alternative?

Mostly, it’s just being honest. “I’m copying my manager on this as it’s a formal matter.” “I want to flag this to the team; happy to move this to a group thread.” Even “I’d like HR to be aware of this” is honest in a way that a silent BCC never is.

If you want to keep someone informed, CC them and say why. If you want to document a conversation, keep a personal record. If something needs escalating, escalate it, but as a conscious act, with your name attached.

None of this is comfortable. It requires a culture where directness is valued over self-protection. It requires leaders who don’t reward the covert over the courageous. It requires us to notice a behaviour so normalised it’s almost invisible, and decide it isn’t acceptable any more.

The BCC button isn’t going anywhere. But we can choose when we click it, and why. That choice says something about what kind of workplace we’re building.

Questions to sit with:

• When did you last use BCC – and why?
• Have you ever discovered you were BCC’d on something? How did it feel?
• What would need to be true for you to say the thing directly instead?
• Does your culture reward transparency or protect those who play it safe?

If you’d like more information on our communication sessions, psychological safety or if you have further questions on this blog then feel free to contact me on email or LinkedIn.