ADHD time blindness and the 10-second log

Time blindness is the reduced ability to sense the passage of time and to estimate how long things take. With ADHD it is one of the more consistently reported experiences, and it quietly breaks two things in habit tracking that nobody warns you about.

The first is clock-based habits. The second is logging itself.

Why clock-based habits fail

"At 8am, stretch" looks like a habit and is actually an appointment. It depends on you noticing that it is 8am, which depends on you checking a clock at roughly the right moment and registering what it says.

If your internal sense of elapsed time is unreliable, that check does not happen on schedule. Twenty minutes and ninety minutes feel similar from the inside, especially inside anything absorbing. You look up and it is 10:40, and the 8am habit did not fail because of motivation — the cue never fired.

The usual fix offered is an alarm. Alarms work for a while and then stop, for a reason worth understanding: an alarm that fires when you cannot act on it gets dismissed, dismissal becomes the learned response, and within two weeks you are swiping away notifications without reading them. The alarm has trained you to ignore it.

What works better is anchoring to events rather than to times. Events are self-announcing — you cannot fail to notice that you have got into bed. "After I get into bed" is a stronger cue than "at 10:30pm" even though they describe nearly the same moment, because one of them requires time perception and the other does not. Habit stacking with ADHD covers how to choose anchors that hold.

Why retroactive logging destroys your data

This is the failure that matters more, and it is less obvious.

Time blindness interacts badly with memory for when things happened. Asked on Thursday whether you exercised on Monday, you will often produce a confident answer that is wrong — not because your memory is poor in general, but because the temporal ordering of a week is exactly the thing that is hard to reconstruct. Monday and Wednesday blur.

So if logging is deferred, your record becomes a reconstruction. And a reconstructed record is not data: every conclusion you draw from it is built on guesses. The weekday breakdown that would have told you something useful is now noise, because the weekday assignments themselves were invented on Thursday evening.

This is the thing that killed my original habit spreadsheet. Opening a sheet on a phone was slow enough that I deferred to "when I'm at my laptop," deferral became reconstruction, and within six weeks the file was a record of what I probably did. I kept it for another month before admitting it was worthless. The full story is in how I turned a spreadsheet into a gamified habit tracker.

Friction is the dominant variable

Which leads to the conclusion that matters more than any feature comparison: the cost of logging at the moment of the behavior determines whether your data is real.

If logging takes ten seconds, you do it now. If it takes ninety seconds, you do it later, and later means never or means guessing. There is no middle state where you reliably log two hours after the fact.

Ten seconds is not arbitrary. It is roughly the window in which an action does not require its own decision to initiate — short enough to complete inside the gap you already have, rather than becoming a task that needs scheduling. Past that threshold, logging becomes a thing you have to decide to do, and deciding to do things is the specific resource that is scarce.

This reframes what to look for in a tracker. Analytics depth, progression design, aesthetics — all secondary. The first question is how long the daily interaction takes, because everything else depends on having an honest record.

What adds friction

In rough order of damage:

• →Mandatory fields. A required mood rating, note or reflection prompt turns a tap into a form. Every required field is a reason to skip a day.
• →Navigation depth. If today's tasks are not the first thing on screen, you are paying a scan-and-find cost before you can log anything.
• →Confirmation dialogs. "Are you sure you completed this?" doubles the interaction for no benefit.
• →Load time. A three-second splash screen is a third of your budget.
• →Ambiguous tasks. "Exercise" requires a judgment call about whether a walk counted. Judgment calls are expensive on low-capacity days, and the cheap resolution is to not log at all. Define tasks so completion is unambiguous.
• →Streak anxiety at the point of entry. If opening the app shows you a number you are about to break, opening it becomes aversive. Why streaks don't work for ADHD covers this.

What a ten-second log looks like

Concretely: open the app, today's active tasks are already on screen, tap the ones you did, done. No required notes, no mood survey, no confirmation. Optional fields stay optional.

In SELV, logging is a tap per task on the today view. Each completed task adds its share of the day's 100 XP, there is nothing else to fill in, and the dashboards are a separate place you visit when you want them rather than something you pass through to log. That separation is deliberate: the analytics are the reward you choose to collect, never the toll you pay at the entrance.

The design rule underneath it: entry cost near zero, depth available on demand. An app that makes you walk through its insights to record a checkbox has inverted the relationship.

Making logging itself the anchored habit

The reliable solution to "I forget to log" is to stop treating logging as something you do when you remember and make it a stacked habit with its own anchor.

The best anchor for most people is getting into bed. It is involuntary, it happens daily, it is the end of the window so you are logging the complete day, and you can do it one-handed. Second best is the first drink of the day, logging yesterday.

Two notes on that. Logging yesterday in the morning is a legitimate pattern, not a failure — a consistent one-day offset keeps your weekday data accurate, which is the thing that matters. What destroys accuracy is variable delay, not fixed delay. And logging at a reliable anchor beats logging at the ideal moment: a tracker you fill in every night at 90% accuracy is worth far more than one you fill in immediately at 40% coverage.

When you have already lost a week

Do not reconstruct it. The temptation is to fill the gap from memory so the record looks complete, and that is how you poison the dataset — a week of invented entries is worse than a week of blanks, because blanks are honest and inventions are indistinguishable from real data later.

Leave the gap. It reads as what it was: a period where you were not logging. Then log today.

This only works if the system does not punish the gap, which is the practical argument for permanent accumulation. If a missing week zeroes a streak, you are incentivised to falsify the record to protect the number — the mechanic is actively rewarding you for corrupting your own data. How to restart habits after burnout covers the re-entry.

Estimation, not just perception

Time blindness has a second half that gets less attention than the first, and it changes how you should set up a habit list.

Alongside difficulty sensing elapsed time, there is difficulty estimating how long something will take — usually in the direction of underestimating. A task you budget ten minutes for takes twenty-five. Four such tasks in a day produce an hour of overrun, and the overrun lands on whatever was scheduled last.

Which means habit lists built by estimating durations are systematically over-subscribed. You picked six habits that "only take a few minutes each," and the real total is well over an hour. The list was never completable, and the daily failure it produces reads as a motivation problem rather than an arithmetic one.

Two corrections that help. First, time your habits once, honestly, with a stopwatch rather than an estimate. People are routinely surprised, and the surprise is almost always in the same direction. Second, build the list against your worst realistic day rather than your best — if it cannot be completed on a bad day, the list will generate failures on most days.

This is also why anchoring beats scheduling. An event-anchored habit does not need a time budget; it happens in the gap that already exists after the anchor. A time-scheduled habit requires an accurate estimate of everything before it in the day, which is exactly the computation that is unreliable here.

The short version

Time blindness means clock cues are unreliable and retroactive recall is unreliable. Both problems have the same shape of fix: attach things to events rather than to times, and make the recording cheap enough to happen at the event.

Everything else about a habit tracker is a preference. This part is a constraint, and an app that fails it cannot give you an honest record no matter what else it does well.

Further reading: habit tracking with ADHD for the full picture on tracker mechanics, habit stacking with ADHD for anchor selection, and what your completion rate actually means for reading the data once it is trustworthy.