You are sitting at your desk, and your screen is a wall of passive-aggressive white space. You have a task that requires a specific sequence of permissions-something involving a legacy database and a budget code that hasn’t been valid since the merger in 2017.

You know there is a PDF for this. You know there is a wiki page with a title like “Inter-Departmental Procurement Protocols (Revised v4).” You even know, with a sinking sense of dread, that if you spend the next eleven minutes digging through the intranet, you will find a flowchart that looks like a map of the London Underground designed by someone who hates trains.

Instead, you look at the person sitting three feet to your left. You wait for them to finish a sentence on their headset, and then you say their name. You ask the question. They don’t give you a PDF. They don’t cite a protocol.

They say, “Oh, just use the old code but put a ‘Z’ at the end, then hit refresh twice. The system is buggy, so the first error message doesn’t count.”

Total elapsed time: ninety-second seconds. You are back to work. You have just participated in the most powerful, untraceable, and efficient economy in the modern world, and your boss has no idea it exists.

The Vending Machine Problem

Consider the office vending machine as a perfect closed system. It is a physical manifestation of a “Knowledge Base.” It has a clear interface: a glass front showing you exactly what is available, a keypad for input, and a slot for currency. It is designed to be self-explanatory.

If you want the salt-and-vinegar crisps, you press B4. The machine does not need to know who you are, it does not need to discuss your motivations, and it certainly doesn’t care if you’re having a bad day.

But the moment the spiral arm gets stuck-the moment the crisps are dangling by a plastic corner, tantalizingly out of reach-the system fails. The “documentation” (the keypad and the glass) offers no solution for a partial success. You cannot press B4 again to “nudge” it.

In that moment, the formal system becomes a prison. You don’t call the 1-800 number on the side of the machine. You look for the guy in the breakroom who knows exactly where to kick the base of the machine to make the motor vibrate just enough to release the bag.

Organizations spend millions building the vending machine. They spend nothing on the guy who knows where to kick it. They treat the “kick” as a failure of the machine, rather than recognizing that the kick is the only reason the machine is still tolerated.

The Ghost in the Spreadsheet

We measure what we can see. This is the fundamental trap of corporate investment. A Chief Knowledge Officer can point to a dashboard and show that the company has 4,200 unique articles in its internal library. They can show that these articles were “accessed” 15,000 times last month. This looks like productivity. It looks like a managed asset.

What they cannot show is the 184,000 “micro-consultations” that happened over coffee, via Slack DMs, or through a quick lean-over at a cubicle. If we were to actually map the data flow of a functioning office, the formal documentation would look like a few thin, icy streams trickling through a desert, while the informal peer-to-peer exchange would look like a Category 5 hurricane.

Every investment in a formal resource is, in reality, a bid to compete with a human who is standing right there. And the human wins every time because the human provides “contextual filtering.” A PDF tells you everything. A colleague tells you the one thing that matters.

The Rule of the Single Digit

Here is a statistic that feels wrong until you live it: in a system of 1,000 variables, the average human only ever interacts with 7 of them. When an organization builds a manual, they feel compelled to document all 1,000 variables because they are “being thorough.” They are creating a map where the scale is 1:1.

But when you ask a colleague for help, that colleague performs a brutal, beautiful act of data destruction. They delete the 993 variables that don’t apply to your specific problem. They aren’t giving you information; they are giving you the absence of irrelevant information.

“

If a player has to read more than twelve words to understand a puzzle, the puzzle is broken.

– Kai D., Escape Room Designer

In escape room design-something my friend Kai D. obsesses over-this is the difference between a “clue” and a “manual.” A manual explains how the lock works. A clue tells you why you should care about the lock right now. Most corporate documentation is a 50-page puzzle that nobody asked to solve.

The Pickle Jar Paradox

I tried to open a jar of pickles this morning. I am a grown man with reasonably functional hands, yet the lid refused to budge. I could have gone to YouTube. I could have searched for “torque techniques for vacuum-sealed glassware.” I could have read a physics paper on the expansion of metal under heat.

Instead, I handed it to someone else. They didn’t have more strength; they just had a different grip. They tapped the bottom of the jar with the palm of their hand-a trick I knew but had forgotten-and the seal popped.

In that moment, I didn’t need a “Knowledge Management System.” I needed a person who wasn’t currently frustrated by the jar. This is the “Emotional Proximity” factor. When you are stuck, your IQ effectively drops by twenty points because of the cortisol spike.

Documentation requires high-level cognitive processing to navigate. A colleague requires only the ability to listen. They act as an external hard drive for your brain when your own sectors are overheating.

The High Cost of Auditable Truth

Why do we keep building the manuals if nobody reads them? Because manuals are auditable. If a process goes wrong and a million dollars vanishes, the leadership needs to be able to say, “We had a protocol. Look, it’s on page 34.”

You cannot audit a shoulder-tap. You cannot put “Dave told me to add a Z” into a compliance report. Organizations value the record of knowledge more than the utility of knowledge. They would rather have a documented process that fails than an undocumented shortcut that works, because the failure can be blamed on “human error” (the failure to follow the manual), whereas the shortcut is “operational risk.”

This is why, in the world of regulated environments, the gap between “Work as Imagined” and “Work as Done” becomes a canyon. The people on the floor-the ones actually shuffling the cards or spinning the wheels-know the truth.

Take the world of high-stakes entertainment. If you are a player looking for a platform that feels real, you don’t want to read a white paper on Random Number Generators. You want to see the dealer’s hands. You want the human element that documentation can’t simulate.

This is why a platform like gclub survives and thrives; it recognizes that people trust the visible, human action over the invisible, “documented” software engine. It’s the difference between reading a flight manual and watching a pilot stick the landing.

The Efficiency of the “Wrong” Way

We are taught that the “correct” way to learn is through formal study. We are taught that the “wrong” way is to pester our coworkers. But if we define efficiency as “the least amount of energy expended to achieve a successful outcome,” then pestering our coworkers is the most “correct” thing we do all day.

The colleague who explains it in ninety seconds isn’t just saving you time; they are preserving your momentum. Every time you leave your workflow to “search” for an answer, you risk falling into the gravity well of your inbox or a news tab. The shoulder-tap is a tether. It keeps you at your desk, in your task, and focused on the finish line.

The archive is a graveyard of things we might need to know. The person next to you is a live feed of what you need to know now.

If we want to actually fix the “knowledge problem” in our companies, we should stop trying to make better manuals. We should start making it easier for people to talk to each other. We should stop measuring “clicks” on the intranet and start measuring “meaningful interruptions.”

The next time you see two people talking at a desk instead of looking at the official guide, don’t see it as a failure of your training program. See it as a victory of human intelligence over bureaucratic inertia. The ninety-second explanation isn’t a shortcut; it’s the destination. The documentation is just the long way around.