Every workplace has that moment when frustration turns into a rule. Not a thoughtful policy or a well-tested process, but a reaction, something said loudly enough in a meeting that it suddenly becomes official.
For one engineering firm, that moment came after a minor sync error caused some lost work. It wasn’t catastrophic, but it was enough to set their manager off.
What followed was a decision that sounded decisive, even reasonable if you didn’t think about it too long.
He wanted everything on paper.
“If It’s Not Printed, It Doesn’t Exist”
The manager had always been skeptical of digital systems. Cloud logs, dashboards, automated reports, none of it felt real to him. In his view, data only truly existed if you could hold it, flip through it, and see it stacked in front of you.
So after the incident, he made it official.
From now on, every automated system log and error report had to be printed and placed on his desk every morning for manual review.
No summaries. No dashboards. No filtering.
Just raw data. On paper.
The IT team tried to explain what that actually meant. Thousands of lines of logs every hour, most of it routine system chatter. But the explanation didn’t land.
“Paper doesn’t lie,” he said.
And that was that.
Following the Rule, Exactly
The person responsible for coordinating project logs didn’t argue.
He complied.
Completely.
Instead of sending reports to internal dashboards, he redirected them to the office printers, including a heavy-duty laser printer and a large-format plotter typically used for engineering drawings.
Then he disabled the filters that normally removed repetitive system messages, the constant “heartbeat” signals that servers send to confirm they’re still running.
What remained was everything.
Every ping. Every update. Every line of activity.
Unfiltered.
Unstoppable.
The Morning the Printers Took Over
He came in early the next day to collect the results.
The laser printer had already burned through multiple reams of paper. The plotter had produced a long, continuous strip of logs, stretching across the floor like a receipt from a machine that had no idea when to stop.
It wasn’t a report.
It was a physical manifestation of the system.
He gathered it all, stacked it carefully, and brought it into the manager’s office. The pile was so large it took up most of the desk, pushing aside everyday items just to make space.
Then he delivered it simply.
“These are the raw logs from the last twenty-four hours. I’ll have the next batch ready tomorrow.”
When the Rule Meets Reality
At first, the manager stuck to his decision.
He spent the day going through the logs, page by page, the sound of paper shifting echoing through the office. But it didn’t take long for the scale of the problem to become clear.
There was too much.
Not just a lot, but an overwhelming amount of information, most of it repetitive, most of it meaningless without context or filtering.
By the afternoon, the question finally came.
“Is there a way to just get a summary?”
The answer, of course, was no.
Not anymore.
Because summaries were exactly what he had banned.
The Slow Collapse of a Bad Idea
Over the next few days, the situation only got worse.
More logs. More paper. Larger piles.
By Thursday, the manager’s desk was no longer usable. The reports had taken over completely, forcing him to work from a small side table while the mountain of paper continued to grow.
And then, quietly, the rule changed.
An email went out reinstating the digital dashboard and encouraging employees to “use their best judgment” when deciding what needed to be printed.
Which, as everyone knew, was exactly how things had worked before.
Why This Happens So Often
There’s a pattern here that shows up in a lot of workplaces.
A problem occurs. Leadership reacts quickly, often emotionally. A strict rule is introduced to prevent it from happening again. But the rule doesn’t account for how the system actually works in practice.
Instead of solving the problem, it creates a new one.
Workplace research and discussions, including those often referenced by the Harvard Business Review, highlight how overcorrection can lead to inefficiency by removing context and flexibility from decision-making.
In this case, the desire for control replaced the need for clarity.
And the result was exactly what you would expect.
Here’s the input from the Reddit crowd:
Many joked about how common it is for managers to demand visibility without understanding the volume of information they’re asking for.
Others pointed out how long it took for the realization to happen, noting that the outcome was obvious from the start.
Some appreciated the precision of the response. There was no argument, no defiance, just perfect compliance that allowed the flaw in the rule to reveal itself.
He didn’t push back.
He didn’t ignore the rule.
He followed it.
Exactly as it was given.
And sometimes, that’s all it takes.
Because when a bad idea is allowed to play out fully, it doesn’t need to be challenged.
It explains itself.
