Should you log why you did something, or just what you did?

You skip your run and go to write it down. "Skipped the run" feels incomplete sitting there on its own, so a reason gets added: raining, or too tired, or ran out of time. It seems like the more honest, more useful version of the entry. It is usually neither. The reason you reach for in the moment is not a fact about the day — it is the explanation you happened to be telling yourself when you picked up the pen, and those two things are not the same thing.

A reason written in the moment is a guess, not a record

You do not have privileged access to your own motives the way you have access to what actually happened. What happened is checkable: you skipped the run, you left the meeting early, you said yes to the thing. Why you did it is an interpretation, assembled on the spot from whatever explanation was closest to hand and least uncomfortable to write down. "Too tired" might be true. It might also be the first acceptable-sounding reason that arrived before a less flattering one — that you didn't want to, or you'd already half decided the night before — got a chance to surface. A log entry does not know the difference, and once it is written, it reads as settled fact either way.

This is not a claim that you are lying to yourself on purpose. It is that the why of a decision is genuinely harder to know than the what of it, and a log written at the speed of an entry does not have time to do that work honestly. It defaults to whichever reason is quickest, and quickest is rarely the same as correct.

One reason is a guess; a month of facts is an answer

Write "skipped the run — raining" once, and it is a small, plausible note. Write "skipped the run" twelve times over two months with no reason attached, and something more useful becomes visible: it happened on Mondays more than any other day, or it clustered in the same week as a string of late nights, or it stopped entirely for three weeks and you cannot immediately say why. None of that shows up in any single entry's reason field. It only shows up across many plain entries, once there are enough of them to have a shape. The real explanation for a recurring pattern is almost always something you could not have named correctly on any one of the days it happened — it takes the accumulation to reveal it, and the accumulation only works if the entries are facts rather than a pile of different one-off justifications for what turns out to be the same thing.

Put another way: the reason belongs to right now, and right now is usually wrong about the bigger picture. The pattern belongs to later, and later is where an honest answer actually tends to live.

A reason field quietly turns a log into a trial

There is a second cost to writing the why every time, separate from whether it is accurate: it changes what the log is for. A line that says what happened is neutral — it does not need anyone's approval, including your own. A line that also explains itself is answering to somebody. Once every skipped run, every late start, every hour lost to nothing in particular comes with a justification attached, the log has quietly become a place you defend your choices rather than a place you simply keep them. That is a heavier thing to sit down and write, and it is exactly the kind of weight that makes a log get abandoned — not because the habit was hard, but because it started feeling like an audit of yourself that you were required to pass.

What is worth keeping is context, not justification

The distinction that actually matters is not why versus what — it is whether an extra detail helps you recognize the entry later or defends the choice behind it. "Worked late — client demo moved to Thursday" is context: it tells future you what this evening actually was, so the line means something on a read-through six months from now. "Worked late because I should have finished this earlier" is not context, it is a verdict, and it adds nothing that the fact alone didn't already carry. The first kind of detail is worth the extra half-second. The second kind is worth skipping, every time, because it is not describing the day — it is grading it.

TimeMap only asks for the line and a category colour, at the moment something happens — there is no field asking you to justify it, so the habit of defending a choice never gets built into the interface in the first place. Read across a longer stretch, the AI review is built to find the pattern sitting underneath a string of plain entries — the day of the week, the cluster of weeks, the thing that kept recurring without ever once being explained correctly in the moment. You do not have to guess the why as you write it. Keep writing down what happened, and let enough of those add up to tell you.