Task Management

Every item competing for a day passes through two separate decisions: whether it deserves doing at all, and when it actually gets done. Task management owns the first decision — to-do lists, project lists, study queues, competing commitments, the question of what is worth effort and at what priority. Time management owns the second — scheduling, the question of what an 8–9am block is best spent on. Each fails alone: skip the first and the calendar fills with neatly arranged low-value work; skip the second and a perfectly ranked list never meets a clock.

A dedicated system earns its overhead only when the plate is genuinely full. With a few things to balance, tasks run fine out of the calendar or its built-in list. Once commitments multiply — several projects, other people’s timelines, life admin on top — an app becomes close to mandatory, because the volume exceeds what a head reliably holds and the loop below assumes one trusted place where everything lands.

The loop: collect, prioritize, allocate

Three steps on a daily rhythm:

• Collect everything, all day, into one place. A task enters the app the moment it appears, with no sorting and no judgment in the moment. Capture costs seconds; trying to remember costs attention all day and still drops things.
• Prioritize once a day. At the end of the day — twice if tasks accumulate fast — run the list through the existing machinery: the Priority 0+1 System with its modified Eisenhower matrix decides what must happen, what can happen, and what gets deleted. The sort doubles as a daily review of everything on the plate.
• Allocate what survives. Two-minute jobs get done during the sort itself; everything else takes a slot in tomorrow’s schedule. The order those slots take comes from the lenses below.

Which task gets the first block

Equal priority and equal urgency still leave a sequencing question. Two lenses settle it inside the day; a third — bottlenecking — reaches across days.

• Eat the frog first. Among tomorrow’s high-priority tasks, one is being quietly dreaded — usually the most complex, highest-investment, and most impactful of the set. That one opens the day. Clearing it removes the largest mental burden early, which makes every later block easier to enter, and it simplifies scheduling because the number-one block names itself. Frogs left in place linger on the list precisely because they need the most time, until the remaining runway is shorter than the task and urgency and stress spike together.
• Two-minute jobs never reach the schedule. Listing, re-reading, and re-deciding a tiny task across several days costs more than the task itself. Do it on the spot and keep the list for items that need real planning.

Bottlenecking: promote whatever gates later work

• A trivial task can gate an important one. Some tasks matter little in themselves but sit upstream of heavier work: until they are done, a later step cannot start. Graded in isolation they score low on importance; their real weight is the work waiting behind them.
• Anything involving other people is the standard case. Once a request leaves your hands — an email, a booking, an invitation — the reply timing leaves your control. Sent early, the wait runs in parallel with other work. Sent only when it finally feels urgent, the time remaining may be shorter than the other party’s response time, and the important downstream work dies on schedule. A clinician requesting a scan performs a two-minute task whose timing fixes the date of everything that follows it.
• The repair is deliberate urgency inflation. While sorting an important-but-not-urgent task, ask: once this is done, will I be waiting on someone or something else? If yes, raise its urgency and clear it as early as possible. Deferred, it resurfaces as urgent exactly when the list is fullest, stacked on top of newer tasks that are genuinely high priority.

The three lenses compress into a per-task test: frog → first block of the day; starts a wait on someone else → as early as possible; under two minutes → immediately.

Links into the system

The prioritize step is the Priority 0+1 System running against a fuller inbox; the allocate step hands its output to Building a Schedule That Survives, where the frog becomes the first protected block of the nightly build. Sorting once each evening keeps choices out of execution time — the same repair Decisional Delays makes — and the cluster home is Time Management, Attention and Scheduling.