Time Blindness: What's Really Happening When Someone Is Chronically Late

When someone is consistently late, the standard interpretation is "they don't respect my time." For a lot of neurodivergent people, that interpretation is almost always wrong.

Time blindness is the physical difficulty of perceiving the passage of time. Not laziness. Not carelessness. Not a lack of respect for anyone's schedule. It's an actual perceptual difference in how time is experienced, moment to moment.

Most people carry a relatively consistent background sense of how much time has passed. Twenty minutes feels like twenty minutes. A drive takes about as long as expected. The transition from one activity to the next is anchored by a felt sense of clock-time moving forward.

For a lot of AuDHD people, that internal clock doesn't run the same way. Five minutes and forty-five minutes can feel almost identical when absorbed in something interesting. Estimating how long a task will take is genuinely difficult — not in the "I always underestimate a little" way most adults do, but in the "I don't have a reliable internal read on this at all" way. Leaving on time for something requires conscious, deliberate scaffolding, because the felt sense of I need to start getting ready now simply doesn't generate the way it does for a lot of neurotypical brains.

When someone with this wiring is late, the honest mechanism is usually that their nervous system never generated the time-passage signal that would have produced an on-time departure. They were trying. They weren't trying to disrespect anyone. The internal clock just didn't fire in time.

Add hyperfocus to the mix, and it gets more intense. Hours can genuinely collapse into what feels like minutes during a deep work or interest session — the person emerges and is honestly shocked to discover what time it is. Again: not character. Architecture.

Nagging and shame don't touch the actual mechanism, because the problem was never motivation. What helps is external scaffolding:

• Alarms and calendar reminders, set with buffer built in
• Shared timekeeping rather than assumed timekeeping
• Explicit verbal cues — "we need to leave in fifteen minutes" lands very differently than "we need to leave at seven," because the first one doesn't depend on an internal clock at all

Here's the failure pattern that follows almost every attempt to fix this: a time-management system gets downloaded with real enthusiasm, used heavily for two weeks, abandoned for three months, then reinstated with fresh shame about the previous "failure." Repeat indefinitely.

The shape of the failure isn't the system's fault. It's a binary approach applied to a nervous system that doesn't actually run binary. The fix isn't finding the one perfect system to stick with forever — it's recognizing that systems are situational tools, deployed when the load calls for them and set down when it doesn't.

If and when, not always. During a low-demand stretch, you may not need scaffolding at all. During a high-demand stretch — a big project, a major life change, compounded stress — you may need it urgently. The system that was necessary two months ago isn't necessarily the system needed now, because the load is different.

Feelings are an unreliable indicator of when scaffolding is needed, because feelings about time lag, distort, and sometimes don't arrive at all — that's the whole mechanism behind time blindness in the first place. Behavior is more honest.

On the low-demand end: restlessness, inventing new projects, a felt need for more to do. That's the signal you have slack.

On the high-demand end: tightness in the chest, racing thoughts, sleep disruption, novelty-seeking or unplanned spending. That's the signal the load has outpaced the scaffolding currently in place.

Once you're reading the themes rather than waiting to feel like you need a system, the deployment question becomes practical rather than moral: not "why can't I stick to this," but "is the current load calling for more structure right now, or less."

Answer honestly, for your current stretch of life:

• What alarms, reminders, or shared timekeeping do I already have in place?
• Where do I keep arriving late or missing transitions despite those supports — meaning the scaffolding that's there isn't matched to this particular gap?
• What's my current restlessness-or-tightness read: am I in a low-demand or high-demand stretch right now?
• Based on that read, does the system need to come out, or can it go back in the drawer?

The goal isn't a permanent system. It's a system you can pick up and put down without treating either move as a failure.

• Time blindness is a perceptual difference in how time passes, not laziness or disrespect.
• Estimating how long a task will take can be genuinely unreliable — not a mild underestimate, but no internal read at all.
• Hyperfocus can compress hours into what feels like minutes.
• Nagging doesn't touch the mechanism; external scaffolding — alarms, shared timekeeping, explicit cues — does.
• "We need to leave in fifteen minutes" works better than "we need to leave at seven," because it doesn't depend on an internal clock.
• Organizational systems fail predictably when applied as an all-or-nothing permanent fix rather than a situational tool.
• Picking a system up and putting it down as the load changes is the system working correctly, not a sign it isn't sticking.

This article is for educational and informational purposes only.

Well wishes. 🙏

L.C. Dialogos Buddhist chaplain, Plum Village tradition

© 2026 LC Publishing Company. All rights reserved.