Is it better to log what you did, or track how long it took?

The question usually arrives wrapped in a different one: which app should I use? But underneath it is a choice about what kind of record you actually want, and it deserves an answer of its own before you download anything. A log tells you what you did. A tracker tells you how long it took. They are not two ways of answering the same question — they are answers to two different questions, and most people only ever need one of them.

What each record actually holds

A tracked hour holds a number and, if you were careful, a label: "2h 15m — Client A." The number is precise and defensible. It is also silent about everything that made the two hours what they were — whether the work went well, whether someone interrupted it, whether you were dreading it before you started. A logged hour holds none of that precision and most of that substance: a line like "finally finished the proposal, felt good to send it" carries no duration at all, and tells you more about the hour than the number would.

Neither record is more honest than the other. They are just keeping track of different things.

Why "how long" feels like the responsible question to ask first

Duration has a head start because it sounds measurable, and measurable sounds rigorous. If you can put a number on something, it feels like you have understood it — three hours on email this week, forty minutes of exercise yesterday. But a number is only useful once you know what you plan to do with it. An invoice needs a number. A comparison against a budget needs a number. A memory of your own week does not need a number nearly as much as it needs a description, and duration is usually the thing people reach for by habit, not because it is what the situation actually calls for.

What logging what you did gives back that a duration cannot

Ask yourself what you actually want to know a month from now, and it is rarely "how many minutes." It is closer to: did I see my friends this month, was work actually as bad as it felt, what happened to the week I can barely remember. None of those questions have a numeric answer. They have a descriptive one, and only a record of what happened — not how long it took — can answer them. A log of forty-two lines across a week will tell you, at a glance, that twelve of them mention the same unfinished project and none of them mention the person you keep meaning to call. A stopwatch total for the same week will tell you none of that; it will tell you the project ate eleven hours, and leave you to guess at the rest.

Sampling a day instead of measuring it

Tracking asks you to account for the whole day, continuously, or the total is wrong. Logging does not carry that obligation. A handful of lines — what you were doing at a few points across the day — is enough to reconstruct its shape later, the way a few photographs are enough to remember a trip you did not film. You are not trying to prove the day happened for eight full accounted-for hours. You are taking samples of it as it goes, and trusting that a handful of honest samples say more about a day than one exhaustive, unbroken number ever will.

How the two get sold as one thing

Part of why this feels harder to decide than it is comes from how it gets marketed. Many apps promise both: track the duration and add a note, as if a note bolted onto a number gives you the better half of each. In practice it usually gives you the worse half of both — a timer you have to remember to run, and a note field most people leave empty, because their attention already went into starting and stopping the clock. Pick the one you actually need, and the other one is rarely missed.

The cases where duration genuinely is the answer

None of this is an argument that duration never matters. If someone downstream — a client, an employer, an accountant — needs a defensible number, track it, for exactly that slice of the day, and nothing more. The mistake is applying that standard to a life that nobody else is going to audit. Most of a week does not need to survive a dispute. It just needs to be remembered accurately enough to be useful to you later, and a description does that job better than a number every time the only reader is you.

TimeMap is built for that second case. You write a line about what you were doing, give it a colour, and move on — nothing runs in the background keeping a total, because a total was never the point. What comes back later is a shape you can compare across weeks, not a number you have to defend.

So the honest way to answer the original question is to ask a second one first: is anyone but you ever going to read this? If the answer is no, you already know which one you actually wanted.