The document is just the receipt

Why the visible half of knowledge work keeps eating the valuable half.

You can spend three days on a specification. Every field mapped, every edge case caught, acceptance criteria that would survive an audit, a version history clean enough to be proud of. You send it out on Wednesday feeling like you’ve done the best work of your month.

Then someone asks in standup why we’re building this at all, and it becomes clear that nobody knows.

Those three days did nothing. Not because the document was bad. The document was excellent. They did nothing because the understanding never moved, and the understanding was the entire point.

Visible work beats invisible work, every time, automatically

If your job involves a lot of meetings, a lot of emails and a lot of documents, it’s easy to confuse the admin with the work. I did it for years and I still catch myself.

The mechanism is simple enough to be boring. Admin is visible. You can point at it, attach it, forward it. Here’s the doc, here’s the deck, here’s the email with everyone copied in. Thinking is invisible. It happens somewhere behind your face and produces no artefact, so at the end of a week where you thought very hard and changed the direction of a project in a fifteen minute conversation, you have nothing to show that a manager could scan.

So we drift toward the part that can be seen, because being seen feels like proof of value. And the drift is self-reinforcing, because the visible work is also the work that gets acknowledged, which trains you to produce more of it.

What most corporate jobs are really paying for is the other thing. Working out what needs to happen and why. The judgment about which problem is real, which one is a symptom, and which one is somebody’s anxiety wearing a business case. The document is how you package that judgment so other people can act on it.

I could write the most thorough specification on earth, and if the engineers still don’t understand why we’re building what we’re building, I’ve produced a nicely formatted file.

The failure has a shape you can recognise

Once you’re looking for it, over-invested admin has a consistent signature.

It’s usually complete rather than clear. Every field populated, every section present, no gaps. Completeness is the quality you optimise for when you’re worried about being caught out, and clarity is the quality you optimise for when you’re trying to move someone’s understanding. They pull in different directions more often than people expect, because clarity requires you to decide what matters most, and deciding means leaving things out.

It’s also usually solitary. The three-day spec gets written alone, at a desk, in a flow state that feels wonderful. The version that actually works usually involves being interrupted, arguing with someone, and finding out in minute four that your entire framing was wrong. That second experience is considerably less pleasant and much more productive.

And it tends to arrive late. Documents produced to establish understanding show up early and messy. Documents produced to demonstrate diligence show up polished and close to the deadline, when it’s too late for anyone to disagree with the thinking inside them.

The honest exception

Some roles are paid for the artefact, and I don’t want to be glib about that.

If you’re a consultant, the deliverable is the deliverable, and the craft of it is a real part of the value. If you work anywhere with genuine regulatory obligations, documentation is the control itself rather than overhead, and treating it casually is how organisations end up in serious trouble. The same applies to anything that has to survive being read by someone who wasn’t in the room, six months after everyone involved has left. That document is doing a job that no conversation can do, and it deserves the three days.

So this is less a rule than a question worth asking honestly about your specific role. Which one are you being paid for, and does your calendar reflect that?

For most people I’ve worked with, including me, the honest answer is that we over-invest in the visible half. Not because we’re confused about what matters. Because the visible half is safer, and safety is very hard to argue yourself out of at four in the afternoon.

The check

Before I polish anything further now, I ask one question. Do the people who need to act on this understand what needs to happen, and why?

If the answer is yes, I stop. Anything I do after that point is for me, and I try to be honest with myself about that rather than filing it under diligence.

The thinking is the work. The admin just proves you did it.