The projector hummed with a low, agonizing frequency that seemed to vibrate right against my molars, and I could feel the rhythmic thump of a bassline from a song I haven’t heard in five years stuck on a loop in my head. I think it was a disco track. Or maybe just the sound of my own pulse. I sat there, watching the dust motes dance in the beam of light, while the Project Manager tapped a digital pen against the glass table. ‘The full brief, all 105 pages of it, is on the wiki,’ she said, her voice bright with the false confidence of someone who believes they have successfully offloaded a burden. I looked around the room. There were 15 people in that meeting. Every single one of them nodded. They offered that specific, professional half-smile-the one that signals compliance without commitment. I knew, in that moment, with a clarity that felt almost violent, that not one of them would ever click that link. Not even the person who would eventually be blamed when the project inevitably veered off course 35 days from now.

I had spent nearly five weeks of my life crafting that document. I’d researched the edge cases, the technical debt, the user personas, and the contingency plans. I had sourced 25 different data points to justify our architectural shift. It was a masterpiece of corporate literature, a cathedral of information. And yet, it was destined to be a tomb. This is the central lie of the modern workplace: we pretend that writing is the same thing as communicating. We treat the act of documentation as a ritual of completion rather than a tool for understanding. We are all participants in a grand, silent theater where the script is written but the actors never bother to read their lines.

Cora L.M., a clean room technician I once worked with in a sterile manufacturing facility, understood the weight of a word differently than the average office dweller. In her world, documentation wasn’t a suggestion; it was a physical barrier against chaos. If Cora didn’t log the humidity levels every 55 minutes, or if she failed to document the exact serial number of a particulate filter, the entire batch-worth upwards of $85,555-was legally considered trash. She lived in a world where the document was the reality. But in the soft-pixel world of project management and software development, we’ve lost that tether. We write because we are afraid, not because we are helpful.

The Insurance Policy: CYA and Liability

This is the ‘Cover Your A**’ (CYA) methodology of documentation. It’s an insurance policy written in the blood of our wasted hours. We create these artifacts so that when the fire starts, we can point to a timestamped file and say, ‘I told you so on page 45.’ It’s not about guidance; it’s about liability. We are building paper shields to protect ourselves from the consequences of poor verbal communication. It’s a defense mechanism that has metastasized into a full-blown culture of bureaucracy. We’ve traded the efficiency of a 5-minute conversation for the safety of a document that takes 15 hours to write and 0 hours to read. It’s a staggering waste of human potential, a black hole where creativity goes to be archived and forgotten.

“

We are all participants in a grand, silent theater where the script is written but the actors never bother to read their lines.

I remember one specific project where I decided to test this theory. I was tasked with writing a 65-page operational manual for a system that only five people used. About halfway through, on page 35, I inserted a paragraph in a bright red font that said: ‘If you are reading this, please email me a picture of a duck, and I will give you $15.’ I sent the document out to the entire department of 105 employees. I waited. I checked my inbox every 5 minutes for the first hour. Then every 45 minutes for the rest of the day. A week passed. Then a month. Not a single duck arrived in my inbox. My boss even complimented me on the ‘thoroughness’ of the manual during my performance review. He hadn’t reached page 35 either. He had reached the ‘Table of Contents’ and decided that the mere existence of the document was proof of my productivity.

The Audit vs. The Reality

This creates a dangerous feedback loop. Because we aren’t reading, we stop writing for the reader. We start writing for the ‘Audit.’ We use jargon to sound authoritative and length to signify depth. We become like the very systems we try to document: bloated, redundant, and increasingly disconnected from the ground truth. The real work-the actual decision-making-has migrated to the ephemeral spaces. It happens in Slack channels that disappear into the free-tier abyss, or in whispered conversations by the coffee machine, or in the frantic, undocumented heat of a ‘war room’ meeting. We are living in a bifurcated reality: the official record, which is beautiful and dead, and the unofficial reality, which is messy and alive.

I’m guilty of it too. I once spent 15 days arguing over the phrasing of a ‘Mission Statement’ that eventually got printed on posters that 45% of the staff used as makeshift coasters. I felt important while I was doing it. I felt like I was ‘aligning stakeholders.’ In reality, I was just rearranging the deck chairs on a ship that was already sailing in the right direction without my help. We have a compulsive need to formalize the obvious. We take a simple truth and wrap it in 25 layers of corporate-speak until it’s unrecognizable, then we wonder why the junior developers are confused.

Cora L.M. used to say that a clean room is only clean if you stop bringing things into it. Every time you enter, you bring skin cells, hair, and the invisible debris of the outside world. I think documentation is the same. We keep bringing more words into the ‘room,’ thinking we are cleaning up the process, but we are actually just adding more dust. We are cluttering the intellectual workspace with artifacts of our own anxiety.

If we want to fix this, we have to embrace the discomfort of brevity. We have to admit that a three-bullet-point email that gets read is infinitely more valuable than a 75-page PDF that acts as a digital paperweight.

The Hard Question

We need to stop rewarding ‘thoroughness’ and start rewarding ‘clarity.’ We need to acknowledge that the ‘Wiki’ is often the place where information goes to die. I’ve started a new habit: whenever I’m asked to produce a major document, I ask, ‘Who is the one person whose life will be harder if this doesn’t exist?’ If I can’t name that person, or if that person is ‘The Auditor’ or ‘Future Management,’ I push back. I try to find a way to communicate the information in a way that actually hits the brain of the recipient, rather than just filling a slot in a folder. It’s hard. It’s much easier to hide behind 125 pages of text than it is to stand behind 5 clear sentences. The sentences require you to be right. The 125 pages only require you to be busy.

Looking back at that project kickoff, I realize I was the problem as much as anyone else. I was proud of that 105-page brief. I wanted the recognition for the effort, even if the utility was zero. I was a performer in the theater. I sat there with that song still playing in my head-I think it was ‘I Will Survive’ now that I recall the rhythm-and I watched the project fail in exactly the ways I had predicted on page 75.

When the post-mortem happened, no one went back to the wiki. We just sat in another room, with another projector, and started writing a new document to explain why the old one didn’t work. We had 15 new people this time. They all nodded. The cycle began again, $45,555 worth of collective salary time evaporated into the hum of the air conditioning, and I just hummed along with the disco beat in my skull, wondering if I should have just sent everyone a picture of a duck.