I stopped measuring my day by what I produced

For a long time I measured a day by what I could point to at the end of it. If I shipped something, closed something, sent something, it was a good day. If the list was short, I felt behind, even on days when I made a decision that mattered more than anything on that list ever could.

I did this for years without questioning it. A long list meant I had earned the day. A short list meant I had wasted it, no matter what actually happened inside it.

That way of judging a day was measuring the wrong thing. It counted what was visible and ignored what was actually true about the day: whether the work I did made things better, or left them the same.

how I used to judge a day

The way I judged a day was simple. I counted what I produced: emails sent, tasks closed, features shipped, meetings run. At the end of the day I would look at the list and decide how I felt about myself based on how long it was.

I liked this measure because it was countable. I could point to it. I could show it to myself and feel like I had proof that I worked hard that day. There was nothing to argue with. A long list was a good day. A short list was a bad one.

The problem is that a long list can still leave everything underneath it exactly as fragile as it was that morning. I could spend a full day producing output and go to bed with the same weak process, the same recurring problem, the same thing quietly breaking in the background, because I never actually touched it. I was busy. I was not necessarily building anything that would still be standing next week.

the day that didn't fit that measure

A while back I found out that an automated check I relied on, one meant to keep every document at the company formatted to a consistent standard, was not actually checking anything. It still ran. It still reported that everything passed, even though something underneath it had changed: the way files were laid out had shifted, and the check never noticed. It kept saying yes to everything, including documents that were nowhere close to the standard.

A check that silently passes is worse than no check at all, because I had been trusting it. I thought I had a standard being enforced across the company, and I did not. I had a piece of paper that said pass, and I never looked past it.

Once I saw that, I went looking at how much had actually drifted while I trusted that green light. It was not one document. It was however many had piled up while I assumed something was watching that was not watching anything.

I spent that day figuring out exactly what had gone wrong and how far the drift actually went, not fixing it. The fix is still open. I have not signed off on it yet, and I am not going to just because it is written. By the measure I used to keep, that was a slow day. Nothing shipped. Nothing was demo-able. If I had judged that day the way I used to judge my days, I would have gone to bed feeling behind.

I did not feel behind. I felt like I had found something that mattered more than anything else I could have worked on that day. I had spent time trusting a check that was doing nothing, and now I actually knew that. Knowing it is not the same as fixing it, but it is the thing that has to happen first.

what I measure now

The shift was from asking what did I produce today to asking do I actually know what's true about the systems I'm relying on. Those are different questions, and they can point in opposite directions on the same day.

To me, finding a problem that had been quietly costing me for a while beats a high-output day that leaves that same problem sitting there, unnoticed, for another month. The high-output day feels better in the moment because I can see the list. The day where I find out something I trusted was not actually working does not show up on any list, but it changes what I do next in a way the list never does.

For me, output is linear. I do the thing, I get the thing, and tomorrow I start from zero again. Finding a real problem does not reset overnight either. Once I know it is there, I cannot unknow it, and that is worth more to me than a full list I cannot really vouch for.

what this doesn't mean

This is not permission to stop shipping. I still have to close deals and ship work, and a system that never produces anything visible is its own kind of failure. I have caught myself using "I'm looking into it" as an excuse to avoid the harder, more exposed work of actually delivering something. That excuse is real, and I have to watch for it.

Output still counts. It is just not the whole picture anymore. Some days the right move is to produce. Some days the right move is to find out what is actually true about something I have been assuming is fine. I try to ask which kind of day it actually is instead of assuming every day should look the same on the list.

The day I am describing here would have looked wasted by my old measure: nothing shipped, and the thing I found still is not fixed. I would still rather have that day than a week of days that each look full but leave me trusting things I have not actually checked.