Two different failures wear the same name
You did not search this to find out what it means. You already know what it is like to look up and find that a great deal more of the afternoon is gone than should be, and to be genuinely surprised by it every time. Yet nearly every page on the subject spends itself on the definition and then offers a clock.
The definition is not the useful part. What is useful is that the word covers two separate problems, they fail at different moments, and the thing that fixes one does nothing for the other. Sorting out which one is costing you is the whole of this page.
Losing the hour and misjudging the hour are not the same thing
The first failure happens while you are working. Time passes and nothing in you registers it passing, so there is no point at which you could have chosen to stop, because stopping was never presented as an option. This is the one that eats afternoons.
The second happens before you start. Asked how long something will take, you answer confidently and you are wrong, usually in the same direction and often by a lot. That failure costs you differently: it is why the day was overcommitted before it began, and it is why arriving on time keeps failing even on the days nothing absorbed you.
They need opposite responses. The first one needs something in the room. The second one needs a record, because it is a knowledge problem rather than a perception one.
A clock reports the time, it does not interrupt you
The standard suggestion is to keep a clock visible. It rarely helps, and the reason is worth being precise about. A clock answers a question. It sits there holding the correct answer and waits to be asked, and during the stretch where time is not being registered, the question does not occur to you.
So the requirement is not visibility. It is that something changes on its own, in your field of view, without needing to be consulted. Anything that only works when you decide to check it is depending on the exact function that is currently unavailable.
Make duration take up space
The single most effective change is to stop displaying time as a number and start displaying it as an amount. A number has to be read, subtracted from another number and interpreted. A shrinking wedge, a draining bar or a moving hand is understood without any of that, and it can be understood from the edge of your vision while your attention is elsewhere.
That is why an analogue face works better here than a digital one for a lot of people, and why a visual timer that colours in the remaining slice works better still. The point is not the device. The point is that duration becomes a shape that is visibly getting smaller.
- Show elapsed time as well as remaining. Remaining time creates a cliff you are surprised by. Elapsed time answers the question you actually keep failing to ask, which is how long have I already been here.
- Put it in the same visual field as the work, but not in the same window. Something you can see without looking, and cannot close without meaning to.
- Prefer something that is already running to something you have to start. A timer that only helps when you remember to set it fails on exactly the days you needed it.
Stop estimating and start collecting
The second failure does not respond to any of that, because nothing in the room can tell you how long a thing you have not started will take. What fixes it is having actually measured the last few times you did it, which almost nobody has, because the estimate feels reliable from the inside.
Keep the smallest possible record. The name of a recurring task and how long it really took, written down at the end rather than guessed at the start. A handful of entries is enough to be useful, and the pattern that shows up is more specific than the general advice to add extra time: most people are close on the tasks they enjoy and badly out on the tasks they have been avoiding.
The other half of this is that the estimate is usually made for the wrong thing. You are estimating the work and quietly excluding everything wrapped around it. Getting there, finding the file, changing clothes, waiting, and the flat ten minutes afterwards where you are not yet doing anything else. Those are part of the duration whether or not you counted them.
Anchor things to events rather than to times
A time is a piece of information you have to be tracking to act on. An event is something that happens to you. Anything you can hang on the end of something else stops depending on time perception entirely, which is the cheapest available win and the least written about.
After lunch rather than at one. When the call ends rather than at half past. As soon as I get in rather than in the evening. Each of those replaces a moment you have to notice with a moment that announces itself, and the ones that arrive through another person are the most reliable of all.
The two cases this is not
Sorting is worth doing before you buy a timer, because two adjacent problems look identical from the outside and neither is solved by anything above.
One is absorption. If the hours went because you were deep in something and could not be reached, the useful frame is a scheduling one and the boundary has to be able to interrupt you rather than inform you, which the hyperfocus guide works through in full.
The other is not knowing what the next move is. Sitting in front of a task with no visible first step will consume an afternoon that looks exactly like a lost one, and no amount of time awareness helps, because being sharply aware of how long you have been stuck is not an improvement.
Where Focable fits, and where it stops
Focable takes one task you are stuck in front of and breaks it into steps small enough to begin, then runs against the step you are on rather than against the whole task. That matters here for a plain reason: a step you can see the end of is a duration you have some feel for, and an undefined task is one you have none for at all.
It is not a diagnosis, a treatment or a substitute for talking to somebody who can offer either. It does not track your day, and it does not make time perceptible on its own. It handles the definition problem, which is the case in the previous section that a timer cannot reach.
Try it now
Questions
Why can I not feel time passing when I am working?
Because nothing is registering it, so there is no moment where you choose to ignore the clock. That is what makes it different from procrastination and why willpower is the wrong lever. Something has to change in your field of view on its own, rather than sit there waiting to be checked.
What kind of timer actually helps with time blindness?
One that shows duration as an amount rather than a number, so it can be read from the corner of your eye without being interpreted. A shrinking coloured wedge or a draining bar works where a digital readout does not, and showing elapsed time matters as much as showing what is left.
Why am I always wrong about how long something will take?
Usually because the estimate covers the work and quietly leaves out everything around it, and because it is a guess rather than a memory. Writing down what a recurring task really took, a few times, replaces the guess with something specific to you.
Is time blindness the same as procrastination?
No, and treating them as one is why so much advice misses. Procrastination is not starting something you can see. This is not registering time while you are already working, or misjudging a duration before you begin. They can happen together, and they need different responses.