Some workplace rules sound reasonable at first, until someone follows them exactly as written. That’s when the cracks start to show.
At a busy marketing agency, communication had always been a bit messy. Threads got lost, decisions weren’t always clear, and one director had a habit of jumping into conversations late and claiming he hadn’t been kept in the loop. His solution was simple, at least in theory.
Everyone must be copied on every email. No exceptions.
It was meant to create transparency. Instead, it created chaos. Because one employee didn’t just follow the rule. They followed it to the letter.
And within days, the entire system began to collapse under its own weight.
















Ron, the director, wasn’t subtle about his frustrations. He liked control, especially when it came to communication. If something went wrong, his first question was always why he hadn’t been informed. It didn’t matter if he had been copied earlier. If he didn’t remember it, it didn’t count.
So during one team meeting, he introduced a new rule. Everyone had to cc the entire team on every email. No exceptions.
At first, it sounded like he was talking about client work. Project updates, important decisions, anything that might affect the broader team. That made sense.
But then someone asked a simple follow-up. Did this include internal emails too?
Ron didn’t hesitate. Yes. All of it. Full visibility, across the board.
That’s where things took a turn.
One employee decided to follow the rule exactly as stated. No interpretation, no filtering, no “common sense” adjustments. Just pure compliance.
An email to IT about a malfunctioning mouse? Sent to the whole team.
A quick message to the office manager about printer paper? Everyone copied.
A small $40 invoice question to a vendor? Fourteen inboxes received it.
Even a quick note to Ron himself about being five minutes late because of a slow elevator? Yes, the entire team got that too.
It didn’t take long for the volume to spiral.
By the third day, Ron’s inbox had turned into a flood. Messages stacked on top of each other, most of them completely irrelevant to his role. Tiny administrative details, minor requests, everyday office chatter.
The very visibility he demanded had become noise.
Eventually, he pulled the employee aside. The tone had shifted. Less authoritative, more strained. He pointed out that this behavior was “ridiculous” and clearly not what he intended.
But intention wasn’t the point anymore.
The employee calmly opened their meeting notes and showed him exactly what had been said. Every email. No exceptions. Even internal ones. That had been his instruction, word for word.
There wasn’t much Ron could argue with.
By the end of the week, the rule had quietly changed. Now it only applied to project and client updates. No announcement, no apology, just a subtle rewrite.
The system returned to normal.
Mostly.
Because for another month, that same employee kept cc’ing Ron on one specific type of email. Requests for printer paper. Just to make sure, as they put it, he had full visibility.
REFLECTION
There’s something oddly satisfying about moments like this. Not because someone got embarrassed, but because it highlights a common workplace dynamic.
Leaders often create rules to solve a problem they don’t fully understand. In this case, the issue wasn’t a lack of information. It was how that information was processed, or ignored. Adding more visibility didn’t fix that. It just buried everything under a pile of noise.
The employee’s response wasn’t rebellion. It was precision. They followed instructions exactly, without adding interpretation. And that’s what exposed the flaw.
It also says something about communication itself. Clarity isn’t about including everyone in everything. It’s about knowing what matters, and making sure the right people see it at the right time.
Too much information can be just as useless as too little. Sometimes even worse.
See what others had to share with OP:
A lot of people loved the classic “malicious compliance” angle, pointing out that this is exactly what happens when vague rules meet literal execution.




Others joked that they’d seen similar situations play out in their own workplaces.



At the same time, a few commenters rolled their eyes, saying the story felt familiar, like a scenario that pops up again and again with slightly different details.




Still, whether repeated or not, the appeal is obvious. There’s something universally relatable about watching a poorly thought-out rule unravel in real time.
In the end, no big confrontation was needed. No dramatic fallout. Just a quiet adjustment and a lesson learned the hard way.
Sometimes the best way to challenge a rule isn’t to break it, but to follow it so perfectly that it breaks itself.
And maybe the real takeaway is this. If you ever feel tempted to say “every email, no exceptions,” it might be worth thinking twice.


















