Task Management
Task Management
Task management is deciding which work deserves a clock at all. Time management owns the when — leave whether out and the calendar becomes a tidy stack of work that should never have been scheduled, leave when out and a ranked list never meets a day. The small item other work is waiting on belongs in the same pass: it earns a slot because of what sits behind it, not because it looks large.
The loop
A dedicated inbox earns its overhead only when the plate is full. A handful of items can live on the calendar. Many projects, plus other people’s reply times, make one trusted place close to mandatory — a class of tool, not a product.
Collect everything, all day, into that one place. Do not sort in the moment. Capture costs seconds. Remembering costs attention and still drops things. The dump exists so the item leaves working memory and the rest of the day can run.
Prioritize once a day — twice if items arrive fast — through Priority 0+1 System, the evening sort that names what must be done, what can be done, and what to drop. That sort is the daily review. It happens off the clock because Decisional Delays is what those choices become when they leak into the block: the work that should have started waits on a decision that belongs to yesterday evening.
Allocate what survives. Anything that would take less time to finish than to track gets done during the sort. Everything else gets a slot tomorrow.
The loop is overhead the calendar does not need when the plate is light. An evening sort costs minutes every day. If the trusted place is empty most days, drop back to the calendar.
Three lenses
What survives the sort still has to be sequenced. Three lenses do that work. They are not a second system. They are how the next day’s first hours get named.
Eat the frog first. Among tomorrow’s high-priority tasks, the one quietly dreaded — most complex, highest investment, the one that sits on the chest — opens the day. Clearing it removes the largest mental burden and names the number-one block. Frogs linger until the runway left is shorter than the task, which is why first is not a preference. The frog becomes the first protected block on Building a Schedule That Survives, the page that turns allocated items into a day that can still run.
Two-minute jobs never reach the schedule. Listing them, ranking them, and re-deciding them tomorrow costs more than doing them during the sort. They finish in the review or they do not belong on a list.
Bottlenecking grades a task by what waits behind it, not by how large it looks. A trivial item can gate important work. Anything that involves other people is the standard case. Sent early, their wait runs in parallel with other work. Sent when it finally feels urgent, remaining time may be shorter than their reply.
A scan request is the picture. The scan itself is not the emergency. The result is what later work needs. Sent in the morning, the lab’s turnaround runs while other blocks run. Sent at the end of the week, the wait starts when the list is fullest and the remaining days may be fewer than the lab needs. The repair, during the sort, is deliberate urgency inflation: if this item starts a wait, raise its urgency and clear it early. Deferred, it resurfaces when the list is already packed.
The portable test, per item:
| If | Then |
|---|---|
| frog — high-priority and quietly dreaded | first protected block |
| starts a wait on someone else | as early as possible |
| under two minutes | immediately, during the sort |
After one evening sort, tomorrow’s first block should be named — the frog or the wait-starter — and nothing under two minutes should still be on the list.
What the clock receives
The clock only receives work that earned a slot. The wait other work is on has already started. Two-minute jobs never made the calendar. That is the whether pass finished: Time Management, Attention and Scheduling is the cluster that then schedules the day and protects the attention those slots need.
Links into the knowledge base
- Priority 0+1 System — the sort this inbox feeds: what must be done, what can be done, what to drop.
- Building a Schedule That Survives — where allocated items become blocks; the frog is the first protected block.
- Decisional Delays — why the sort happens off the clock: choices kept out of execution time.
- Time Management, Attention and Scheduling — cluster home: this page chooses; that cluster schedules and protects attention.
Open Questions
When two frogs and a wait-starter land on the same morning, which lens wins?
At what plate-size does the trusted inbox start costing more than it returns?
Sources
- Allen, David. Getting Things Done. Capture into one trusted place, and finish anything cheaper to do than to track. Public practice, not a required purchase.
- Cowan, Nelson. Working-memory limits: a few items in mind, easily displaced. Externalizing the rest is why capture is cheap and remembering is not.
- Goldratt, Eliyahu M. The Goal. A small gate can determine the throughput of everything behind it. The personal-list version is bottlenecking, not a project-management course.