Why is it so hard to track time when you have time blindness?

You sit down to answer one email. The next time you look up, ninety minutes are gone, and no part of you experienced them passing — not as a stretch of time you were vaguely aware of, not as a background hum you ignored. It is simply missing. If this happens often enough that "I'll just be five minutes" has stopped meaning anything reliable, you already know the shorthand for it: time blindness, the gap between what the clock says and what time actually feels like from the inside.

It is not about forgetting the time exists

Time blindness gets described as forgetfulness, but that is not quite what it is. Someone who has it usually knows perfectly well that clocks exist and that time is passing somewhere. What is missing is the felt sense of duration while it happens — the quiet internal tally most people run without noticing, the one that nudges you after twenty minutes even before you check anything. Without that tally, five minutes and ninety minutes can feel identical from the inside, distinguishable only by checking something external. And checking something external is itself a step that has to be remembered, at a moment when nothing internal is prompting you to remember it.

A timer assumes the exact sense it is supposed to replace

This is where a timer quietly stops making sense as a solution. A timer is only useful if two things happen on schedule: you remember to start it before the thing begins, and you notice, at some point, that it is still running. Both of those depend on the same internal sense that was missing in the first place. Pressing start requires catching the moment a task begins, before it has absorbed your attention — which is precisely the window that disappears first. And once it is running, a timer gives you no signal of its own; the little clock in the corner looks the same at minute four as it does at minute ninety, so noticing it has kept going requires the very awareness the tool exists to make unnecessary. A stopwatch does not compensate for a missing sense of duration. It just hands the same missing sense a button to forget to press.

"Just set a reminder" moves the problem, it does not solve it

The usual advice is to bolt a reminder onto the timer — an alarm at the twenty-minute mark, a buzz every half hour. This helps for exactly as long as the reminder is still novel enough to notice, and it has its own blind spot: setting a reminder for the right interval means already knowing how long the task will take, which is the one thing that was never knowable from the inside to begin with. You cannot pre-schedule an alert for "however long this actually turns out to take." And a reminder you have to configure, silence, snooze, and eventually mute because it went off during the wrong meeting is one more small administrative task layered on top of a system that was already asking too much.

A record of moments does not need the sense that is missing

A written log sidesteps the entire problem, not by fixing the internal clock but by never depending on it. Nothing has to be started when a task begins, so there is no early window to miss. Nothing runs in the background that you are responsible for noticing later, so there is no ninety minutes quietly accumulating unwatched. The only thing a log asks is what you are doing right now, whenever "right now" happens to occur to you — which could be the moment something starts, twenty minutes in, or after it has already ended and you only just resurfaced. Each of those is still a true, complete entry. None of them required you to catch a beginning, monitor a middle, or remember an end.

• Write when it occurs to you, not on a schedule. A reminder that says "log now" is still asking you to notice a moment. Writing whenever you happen to surface is more reliable than any external cue, because it does not depend on the cue arriving at the right time.
• Do not try to reconstruct how long anything took. "Answering one email, no idea how long, looked up and it was afternoon" is a complete entry. The gap itself is worth naming rather than guessing away.
• Let entries land hours apart with nothing in between. A log with silence in it is not a log with mistakes in it. There is nothing to backfill and no duration owed for the stretch you did not notice passing.
• A short, honest line beats a precise one. "Still on this, longer than I meant" says everything a start and stop time would have tried and failed to say more exactly.

What this actually changes

None of this makes time pass any differently. What it removes is the second problem stacked on top of the first — not just losing track of time, but also being handed a tool that punishes you for losing track of time by needing you to catch it at both ends. Once the record no longer depends on noticing a beginning or a middle, the only thing left to do is write down what is true right now, which is the one thing that was never actually hard.

TimeMap does not have a start button or a running clock, because there is nothing to start and nothing to keep watching. You write a line about what you are doing and give it a colour, whenever you happen to think of it — five minutes in or three hours late makes no difference to whether the entry is honest. Nothing accumulates silently in the background waiting for you to remember it exists.

If every timer you have tried has quietly stopped working for the same reason — not because you were careless, but because it needed a sense of duration you do not reliably have — that is worth taking as information about the tool rather than about you. A record built from moments instead of intervals was never asking for that sense in the first place.