Why knowing when to leave doesn't get you out the door
Your maps app tells you when to leave. Your calendar pings "time to leave". Backward calculators tell you when to start getting ready. And you're still late — because the number was never the hard part.
The "leave by 8:12" promise
A whole family of tools now computes departure arithmetic for you. Navigation apps subtract travel time from your arrival time. Calendar assistants fire a "time to leave" alert. Backward "ready-by" calculators go one step further and subtract your getting-ready time too, telling you when to start. The arithmetic is genuinely useful — and genuinely solved.
Yet the mornings look the same. You see the 8:12 notification at 8:12, standing in the kitchen with wet hair and an unpacked bag. Knowing the number and being ready at the number are two different problems, and the second one is where lateness actually lives.
Knowing is not doing: the intention–behavior gap
Psychology has studied this distance for decades under an unglamorous name: the intention–behavior gap. Forming a sincere intention — "I'll start getting ready at 7:20" — turns out to be a surprisingly weak predictor of actually doing it. What reliably shrinks the gap is turning the intention into an if-then plan bound to a concrete cue: Gollwitzer's implementation intentions, whose meta-analysis across 94 independent tests found a medium-to-large effect (d = .65) on goal attainment, over and above merely intending.[1]
The mechanism explains why a single "leave now" alert underdelivers: when the cue arrives, the action it demands — be finished with everything — isn't a single action you can start. It's the outcome of forty-five minutes of earlier actions, each of which needed its own cue at its own moment.[2] One notification at the end of the routine cannot trigger the twelve behaviors that had to happen before it.
Lateness happens inside the routine, not at the door
Look at where the time is actually lost and the calculator's blind spot gets obvious. The planning fallacy — the best-documented bias in time estimation — doesn't strike at the door; it strikes inside every step. The shower that "takes ten minutes" takes eighteen; breakfast absorbs a phone check; packing surfaces a missing charger. People underestimate task durations even against years of their own evidence, and their worst-case estimates are still shorter than their average reality.[3] Unpacking a task into its components measurably improves the estimates[4] — but a when-to-leave calculator never sees your components. It treats "get ready" as one opaque block, built on exactly the kind of unexamined estimate the research warns about.
So the failure mode is structural: the tools stop at the moment the actual problem begins. They hand you a correct number, then leave you alone inside the forty-five minutes where the number is won or lost.
What execution support looks like
The research that explains the gap also describes what closes it, and none of it is willpower:
- A cue per step, not per departure. Each step's start and wrap-up arrives as an event that names the next action — a delivered if-then plan, at the moment it applies.[1]
- The timekeeping handed over entirely. Monitoring the clock yourself is a background job that degrades everything else and silently stops the moment something absorbs you; offloading it to an external system is the documented fix.[5]
- Visible state, not arithmetic. A live answer to "am I still okay?" — computed from what's actually left to do — replaces the mental re-calculation you'd otherwise run between every step.
- A plan that survives contact with reality. When one step overruns, the rest must adapt; a schedule that can only be right or abandoned will be abandoned by Tuesday.
Calculators, calendars, routine apps — what each solves
None of these categories is wrong; each solves a real piece of the problem. A navigation app solves the travel math. A calendar solves where you need to be and when. A habit or routine app solves what your routine contains, and builds consistency. A when-to-leave calculator solves the start time. What none of them takes on is the execution layer — pacing you through the steps, against the deadline, while reality interferes.
That layer is the gap OutOnTime was built for. It stores your real steps, plans backwards from your Ready-by time, then stays through execution: one live buffer number, a cue for every step, quiet re-pacing when something overruns, and an honest debrief afterwards that shows exactly where plan and reality diverged. A calculator tells you when to start. OutOnTime stays with you until you're out the door.
References
- Gollwitzer, P. M., & Sheeran, P. (2006). Implementation intentions and goal achievement: A meta-analysis of effects and processes. Advances in Experimental Social Psychology, 38, 69–119. Publisher page.
- Gollwitzer, P. M. (1999). Implementation intentions: Strong effects of simple plans. American Psychologist, 54(7), 493–503. DOI.
- Buehler, R., Griffin, D., & Ross, M. (1994). Exploring the "planning fallacy": Why people underestimate their task completion times. Journal of Personality and Social Psychology, 67(3), 366–381. Full text (PDF).
- Kruger, J., & Evans, M. (2004). If you don't want to be late, enumerate: Unpacking reduces the planning fallacy. Journal of Experimental Social Psychology, 40(5), 586–598. Publisher page.
- Risko, E. F., & Gilbert, S. J. (2016). Cognitive offloading. Trends in Cognitive Sciences, 20(9), 676–688. Full text (PDF).
From knowing to actually leaving
OutOnTime is a free Android routine timer that stays with you after the math — pacing, adapting, and keeping the buffer honest. Open beta on Google Play.
Join the beta