The Time You Can't See

The time you can't see is every small answer only you can give: a doorway question, a message at 4pm, that never lands on a calendar and so never gets counted. It adds up quietly. And when nobody wrote the answer down, you find out later, usually the hard way, what assuming it cost you.

I can tell you how many working sessions are behind this company. More than three hundred, across two businesses, every one of them written down.

That isn't a boast. It's the only reason I can write this honestly, because most owners cannot answer the same question about themselves. Not because they're careless. Because the thing I'm about to describe leaves no trace.

The time you never scheduled is still time you spent

Here's the question. How much of your week goes to answering things only you can answer?

Nobody knows. And nobody knows because that time never lands anywhere you could count it. It isn't a meeting. It doesn't get an invite. It's a message at 4pm, a question in a doorway, a call you take because the alternative is a client who feels ignored. Each one costs a few minutes and a broken thought. None of it appears on a calendar, so at the end of the week there's nothing to point at. Just the feeling that you did not get to your own work again.

A scheduled hour you can see. You can move it, shorten it, hand it to someone else. Forty scattered minutes you cannot do anything with, because you never knew you spent them.

Well. Let me show you what it looks like when you can see it.

We caught this failure in our own copy

We log every working session at this company. What got decided, why, and what was still unresolved at the end. It started as discipline and turned into something more useful: a record of exactly where our own thinking was thin.

This week that record caught us out.

We found a line of copy sitting in about ten scheduled posts, telling people to start with a thing our own website does not sell. Not a typo. A whole product tier that existed in our heads, in our notes, in months of internal shorthand, and nowhere a customer could find it. Nobody wrote that on purpose. Somebody assumed it once, early, and it got repeated until it looked like a fact.

That is the same failure as the doorway question. An answer lived in one place, in somebody's head, and every downstream use of it was a guess wearing a confident face.

The difference is that we caught this one, and it cost an afternoon. Uncaught, it would have cost us every click from every post for six weeks, and we'd have blamed the copy.

What changes when the answer has somewhere to live

So here is what I actually believe, after three hundred of these.

The fix is not working harder at documentation. Everyone has already written more down than they think. The problem was never that it isn't written. It's that nothing can find it, and nothing marks which parts somebody actually decided versus which parts somebody guessed once on a Tuesday.

Three things change when you fix that.

The questions stop arriving one at a time, because the answer has somewhere to live. New people stop needing you to be available to be useful. And you find out, sometimes uncomfortably, what your business has been quietly assuming.

I'd rather know.

A few questions this raises

Isn't this just better documentation?

No. Everyone has already written more down than they think. The problem isn't that nothing gets written, it's that nothing can find it afterward, and nothing marks which parts were actually decided versus guessed once and repeated.

How do you know which parts were decided and which were guessed?

By writing down the decision and the reason at the time, not reconstructing it later. That's what the working-session log is: what got decided, why, and what was still unresolved, recorded as it happened rather than remembered afterward.

What does it actually cost when this goes wrong?

In our case, an afternoon to catch and fix a line of copy repeated across ten scheduled posts. Left uncaught, it would have cost every click from every one of those posts for six weeks, with the copy taking the blame instead of the real cause.