I’m scrolling through the ‘Onboarding_Process_FINAL_v17.docx’ and the blue light from the monitor is starting to make my retinas ache. It is 7:07 PM. The office is that kind of quiet where you can hear the hum of the vending machine two hallways over. I just spent 47 minutes looking at a flowchart that describes how to request a new stapler, a process that apparently involves 7 distinct levels of approval. I know, with a bone-deep certainty, that the new hire starting on Monday-let’s call him Marcus-will never open this document. He will sit down, find that his stapler is empty or missing, and he will ask the person sitting next to him, ‘Hey, how do I get a stapler?’ And that person will say, ‘Oh, just grab one from the cabinet behind the breakroom fridge.’

We are addicted to the artifact of the answer, rather than the act of answering. We build these digital cathedrals of information, 237 folders deep, convinced that we are preserving knowledge, but all we are really doing is burying it. It’s a form of corporate taxidermy. We take a living, breathing process, kill it, stuff it with jargon, and mount it on a SharePoint site where it collects digital dust. I found myself googling the woman I met at the coffee shop earlier today, Sarah. I wanted to see if her online presence matched the intensity of her handshake. She has 777 followers on a platform dedicated to obscure architectural sketches. Seeing her digital footprint felt more like ‘documentation’ of her soul than any resume could ever provide. It was messy, fragmented, and utterly human.

The Therapy Animal Trainer’s Perspective

My friend Noah S., who spends his days as a therapy animal trainer, once told me that the hardest part of his job isn’t the dogs. It’s the owners who come in clutching 47-page manuals they bought online. Noah S. watches them try to follow ‘Step 17: Establish Dominance via Proximity’ while the golden retriever is busy eating a discarded gum wrapper. Noah S. told me that documentation in his world isn’t a book; it’s the tension in the leash. It’s the micro-expression on the trainer’s face. If you have to look at a page to know how to respond to a living being, you’ve already lost the moment. We do the same thing in software, in marketing, in every corner of the modern workspace. We prioritize the safety of the written word over the efficacy of the shared understanding.

I remember a project where I was tasked with documenting a legacy codebase. There were 107 legacy modules, each one more tangled than the last. I spent 87 hours writing what I thought was a masterpiece of technical prose. I used diagrams. I used color-coded legends. I felt like a god of organization. Six months later, the lead architect resigned. The new guy, a frantic genius with 7 pens in his pocket, never even looked at my directory. When I asked him why, he said, ‘I didn’t have time to read a novel. I just read the tests.’ The tests were the only documentation that mattered because the tests were the only thing that actually functioned. Everything else was just a ghost of what I hoped the code would be.

The Paradox of Thoroughness

This brings me to the fundamental contradiction of our work. We want to be thorough, but thoroughness is often the enemy of utility. When a document exceeds 17 pages, it ceases to be a guide and becomes a barrier. It’s like a wall of fog. You know there’s a mountain behind it, but you can’t see the path, so you just stay at the base and hope for the best. I’ve made this mistake 37 times in my career, at least. I’ve written the ‘Comprehensive Strategy’ that was really just a way for me to feel important, to prove that I had done the thinking so that no one else had to.

Think about the last time you actually learned something complex. It wasn’t through a static PDF. It was through a series of failures, a few well-timed hints from a mentor, and perhaps a frantic search for a specific solution to a specific problem. We need ‘just-in-time’ information, not ‘just-in-case’ information. The ‘just-in-case’ vault is where productivity goes to die.

I’m thinking about this as I look at my own bathroom renovation plans. I spent 7 hours researching the exact specifications for a glass partition. I wanted that feeling of openness, that specific clarity you only get when the lines are sharp and the materials are honest. I looked at the duschkabine 100×100 because they represented a certain kind of structural transparency. But even then, the manual for the installation was 27 pages long. The installer didn’t look at it once. He felt the weight of the glass, checked the level 7 times, and just… knew. He had the ‘leash tension’ that Noah S. talked about.

The Map vs. The Territory

We confuse the map for the territory. The map is a representation, a simplified version of reality designed to help us navigate. But if the map is so detailed that it’s the size of the territory itself, it becomes useless. There’s a story about a kingdom that created a map so perfect it covered the entire land, and the citizens eventually just lived on the map while the actual soil beneath them turned to desert. That is our corporate wikis. We are living on the map.

I admit, I’m guilty of the very thing I’m criticizing. I’m writing this, aren’t I? I’m adding to the pile of words. But maybe if we recognize the futility, we can change the form. What if documentation was just a series of 7-second videos? What if it was a single sentence written in Sharpie on the side of a monitor? ‘If the server screams, pull the red cord.’ That is 107 times more valuable than a 67-page disaster recovery plan that no one can find when the power goes out.

The Power of Brevity

Noah S. told me about a therapy dog he trained that would only sit if you hummed a specific note. It wasn’t in any manual. It was a quirk of that specific animal’s history. You could write ‘Hum at 440Hz’ in a document, but until you felt the dog settle under your hand, the instruction was hollow. We treat our coworkers like machines that can be programmed with text, but they are more like Noah’s dogs. They are driven by context, by culture, and by the desperate need to not feel like they are wasting their time.

When I googled Sarah, I wasn’t looking for her resume. I was looking for her ‘why’. I was looking for the things she cared about that didn’t fit into a bulleted list. We need to start writing our documentation with that same spirit. We need to stop documenting what things are and start documenting why they matter. If Marcus knows *why* we have a 7-step approval process for staplers (perhaps a traumatic incident involving $777 worth of unauthorized office supplies in 2017), he might actually respect the process. Or, more likely, he’ll help us realize the process is stupid and we can finally delete those 67 pages.

There is a certain bravery in brevity. It takes 17 times more effort to write a one-page summary than it does to vomit out a 50-page report. The 50-page report is safe. It covers your tracks. It proves you were working. The one-page summary is dangerous. It requires you to make a choice about what is important. It requires you to leave things out. And we are terrified of leaving things out. We think that if we don’t include every edge case, every ‘what if’, and every historical footnote, we are being negligent. But the real negligence is producing something that no one can consume.

The most useful page is the one you don’t have to turn.

“

The Currency of Time

We forget that every word we write is a debt we are asking someone else to pay in time. And time is the only currency that never experiences inflation; its value only ever goes up as we have less of it. To hand someone a 237-page manual is to hand them a bill for 7 hours of their life. You better be sure that what you’ve written is worth the cost. Most of the time, it isn’t. Most of the time, we are just talking to ourselves, trying to quiet the anxiety of our own disorganized minds. Noah S. understands this. When he trains a dog, he doesn’t use 77 words when a single click will do. The click is the documentation. It’s clear, it’s immediate, and it’s impossible to misunderstand.

I remember an old developer I worked with who had a single sticker on his laptop. It said: ‘Code doesn’t lie, comments sometimes do.’ It was a reminder that the artifact-the document-is always a step removed from the truth. The further we get from the source, the more the signal degrades. By the time a process reaches the 17th version of a Word document, it’s no longer a reflection of reality. It’s a reflection of what we wish reality looked like during a meeting three months ago.

Embracing Silence and Clarity

So, here is my confession. I have written thousands of pages that have served no purpose other than to satisfy a manager who wanted to see ‘progress.’ I have contributed to the noise. I have built walls of text that blocked the view of the actual work. But tonight, at 8:07 PM, I am stopping. I am going to embrace the architecture of silence. I am going to trust that if a process is good, it will be visible. If a culture is strong, it will be felt. And if someone really needs to know how to get a stapler, they’ll find the cabinet behind the fridge. They always do.

We don’t need more documentation. We need more clarity. And clarity usually involves a delete key and the courage to stand by the few words that remain. I think about those 777 followers Sarah has. They aren’t following a manual. They are following a vision. They are following something that resonates without needing a table of contents. That is the goal. To make the work so resonant that the instructions become an afterthought. To train the dog so well that the leash goes slack. To build the space so clearly that the glass is invisible, yet undeniably there, holding the structure together with nothing but its own inherent strength.

I’ll close the laptop now. The hum of the vending machine is the only thing left. I’m going to walk out past the 7th-floor security desk, say goodnight to the guard whose name I finally memorized (it’s Ray, and he’s been here 17 years), and I’m going to leave the 67-page document exactly where it belongs: in the trash bin of history. Marcus will be just fine. He’s smarter than the manual anyway.