"Waiting mode": why a 2 PM meeting deletes your whole morning.

For years my calendar had a recurring 2 PM steering call on it. Thirty minutes, low stakes, cameras optional. And for years, that thirty-minute meeting quietly ate five hours of my life every week — because from the moment I woke up and saw it, the morning was already over.

I would not start the deep work. I would not start the shallow work. I would not start the dishes. I answered a few emails, opened the document, closed the document, checked the time, checked the time, checked the time. I was a project manager coordinating people across time zones — reconciliation runs for Bank of America at Aon, private-equity research pipelines at Morningstar — and I could not use the four free hours sitting in front of a meeting I was running.

If you have inattentive ADHD, you know this state so well it has a name in the community: waiting mode. You're not resting. You're not working. You're orbiting.

§1It has a name, and it isn't "lazy"

Clinicians describe waiting mode as one of the signature ways time blindness shows up: you shut down and initiate nothing because something is scheduled later — even when starting would not interfere at all.^[1] It sits alongside chronic lateness and messy transitions in the time-blindness family. Here's what struck me when I went looking for help: almost everything written about it is addressed to parents of teenagers. Meanwhile, roughly fifteen and a half million US adults carry an ADHD diagnosis — about half of us diagnosed as adults^[2] — and we are sitting in offices, orbiting meetings, wondering why we can't touch the report due Friday just because standup is at 11.

So consider this the missing adult version.

§2The mechanism: your day has one landmark

ADHD time famously comes in two flavors: now and not now. What that means in practice is that time has no texture — you cannot feel the difference between a 45-minute gap and a four-hour gap. They are both just "not now, but soon, probably, oh no."

Into that fog, an appointment drops like a lighthouse. It is the only visible landmark in the entire day. So attention — which in ADHD goes wherever the salience is — locks onto it and never lets go. Every glance at the clock is your brain re-checking the only coordinate it has.

You are not afraid of the meeting. You are afraid of the transition — being ripped out of deep focus with no warning, mid-thought, mid-flow.

That fear is rational, by the way. If you've ever been dragged out of hyperfocus by a calendar ping, you know it feels less like a reminder and more like a fire drill. Your brain has learned that descending into real work before a meeting has a cost — so it refuses to descend at all. Waiting mode is not a failure of discipline. It is a risk-avoidance strategy your survival blueprint wrote years ago, running unsupervised.

§3The PM diagnosis: a mis-scheduled dependency

Here is where ten years of enterprise scheduling finally paid rent. When I stopped treating my mornings as a character problem and drew them as a project plan, the defect was embarrassing — because I would have caught it in any junior planner's Gantt chart in about four seconds.

A 30-minute meeting is a small, fixed task. In my head, though, it was scheduled as a blocking dependency: every other task of the day marked "cannot start until the meeting finishes." In scheduling terms, I'd priced a half-hour event as a full-day resource lock. No project on earth would survive that plan. Mine didn't either — thirty-three years of it.

§4The fix: four scheduling moves, no willpower required

Everything below is environment design. None of it asks you to feel differently or try harder — that advice has never once survived contact with an ADHD Tuesday.

• 01Rename the unit. You do not have "a 2 PM meeting." You have a 9:30-to-1:30 free block — say it that way, write it that way, calendar it that way as an actual named event. The brain locks onto the most visible object in the day; make the gap the most visible object instead of the meeting. Of everything on this list, this one move does the most work.
• 02Pay the transition tax up front. Put a 30-minute landing strip on the calendar before the meeting. That block has one job: absorb the crash. Wrap up, make tea, re-read the agenda, stare at a wall. Waiting mode exists because interruption is unpriced; price it, and the free block becomes safe to descend into. Enterprise plans call this buffer management — it's why good projects don't panic when a task runs long.
• 03Keep a gap-sized task menu. Choice paralysis eats half of every gap. Keep a standing list of tasks pre-labelled 30 / 60 / 90 minutes — written on a good day, chosen from on a bad one. A four-hour gap before a meeting is not "the report you're dreading"; it is two 90s and a 30, picked off a menu you already trust.
• 04Give time texture you can feel. The clock-checking loop exists because time is invisible; every check is a manual poll. Move time into the environment where your peripheral vision can watch it for free: an analog timer with a shrinking disc, a visual countdown, an ambient color that shifts as the block ages. The rule: you should never have to ask what time it is to know where you are in the block.

§5What changed

I still have a brain with two time zones. The 2 PM call still exists — there is always a 2 PM call. But the morning stopped belonging to it. The free block has a name, the crash is pre-paid, the menu removes the choosing, and the wall glows so I don't have to poll the clock like a nervous parent.

Some mornings I still orbit. The system doesn't shame me for it — a system that only works on good days isn't a system, it's a fair-weather friend. But most mornings, the four hours in front of the meeting are mine again. Multiply that by every working day of a decade, and you understand why I now write these field notes.

You were never lazy. You were running an unexamined schedule. Re-draw it.