Priority 0+1 and the Nightly Build
Priority 0+1 and the Nightly Build
Priority 0+1 is an evening sort that books important work with no deadline first, so that lesser tasks take the hit on a broken day. The matrix is not the invention. Placement is. Urgent work feels important, and the work that would have mattered never gets a slot unless it is booked first.
Task management is deciding which work deserves a clock at all: the whether. 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.
A plan built the night before for a tired, interrupted tomorrow still finishes its two protected blocks. A calendar drawn for the best tomorrow dies the first time focus dips, and the miss takes the rest of the day with it.
Core takeaways
- Importance is the consequence of leaving an item undone. Urgency is how close its deadline sits. The mind reads urgent as important, so the important item with no deadline is booked first, near the start of the day, and urgent work is fitted around it.
- Everything that arrives during the day goes into one trusted place, unsorted. Each evening that list is sorted into one to three priorities. Two is usual.
- Three lenses name tomorrow’s first hours. The quietly dreaded task opens the day. Anything that starts a wait on someone else goes out early. Anything under two minutes is done during the sort and never reaches the schedule.
- When time disappears, lower items absorb the loss and the top block stays. A day scheduled by importance degrades gracefully.
- A plan dies three ways: no schedule, vague blocks, over-packing. The nightly build gives every block a measurable intention, overestimates each task by about 25 percent, underfills the day by about 25 percent, books rest, and writes rails into the calendar.
- Priority 0 is core values and a long-term vision, reviewed every six months, the aim-check above every daily list. One week of actual against planned is the only number that sizes the pads.
What the evening sort produces
Each evening, a running list is sorted into one to three priorities. Two is usual. The sort names what must be done, what can be done, and what to drop. It doubles as a review of the day just spent.
Most days only one or two things finish. Because they are the highest-importance items, output stays steady. Important work with no deadline is booked before anything with a deadline, and when the day breaks, lesser tasks take the hit.
One inbox, sorted once
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. It is 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.
The sort happens off the clock. 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.
Placement, not the matrix
Intuition prioritises badly. The mind reads urgent as important. That is urgency trapping: the day fills with deadlines, so the work that would shrink future load never gets a slot. Homework has a deadline. Skill-building does not, so it is deferred until the gap cannot close. Present bias is enough to explain the trap. No Pleistocene story is required.
Knowing the four quadrants leaves the trap intact. People who can name all four still fall in, because the trap lives in scheduling order, not in understanding.
Importance is the significance of the consequence if the item is left undone. Urgency is how close the deadline sits. Consequence of failure, not a feeling.
The standard matrix assumes items can be delegated. These treatments assume they cannot, which is why the urgent-not-important cell is batch-and-delay rather than hand-off.
- Important and urgent: do.
- Important and not urgent: schedule first, near the start of the day.
- Urgent and not important: batch and delay to the last viable moment.
- Neither: delete.
Deleted items re-enter if they are genuinely needed, like a re-downloaded file. Deleting without anxiety draws on Decision Making. Doing urgent-not-important work early steals minutes from important work. Doing those items together, at the last viable moment, preserves flow.
The four treatments are not the system. Anyone who has seen the matrix already owns them. The addition is the booking order: the important-not-urgent cell goes into the day first, near the start, and everything urgent is fitted around it. That is placement.
Three lenses for the first hours
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 opens the day: the most complex, the highest investment, the one that sits on the chest. 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 of the nightly build.
Two-minute jobs never reach the schedule. They are the one exception to batch-and-delay. 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 |
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.
Protect downward
Priority 1 is tomorrow’s single most important block. It keeps its claim when the day breaks. Protect downward is the survival rule: when time disappears, lower items absorb the loss; the top item stays. Never the other way.
Twenty minutes of evening meditation is the worked case. Blocked first, it survives a day that otherwise ate the evening. Left for “when things settle,” it never happens. No deadline ever arrives to defend it. A day scheduled by importance degrades gracefully: the afternoon can die and the morning block still happened.
Three ways a plan dies
No schedule. Deciding as the day unfolds allocates the hours to whatever shouts. The loud item wins. The compounding one does not get a block, because nothing was reserved for it.
Vague blocks. “1–3pm: biology” names a subject and no next action. The delay at the start of the block is where a distraction gets in. A three-hour “study biology” block assumes three hours of perfect hold, which is the same assumption with a longer label. Vague blocks fail by delay-then-drift; Procrastination a System Problem owns that sequence.
Over-packing. No room for error. One slip invites quitting, and a vague block inside a packed day compounds: the delay uses the slack that was never left, then the miss is read as the plan being impossible. The three-hour biology block is this death when it is also the only block that could have moved.
Those are the three. A fourth is not needed.
The nightly build
Contents before layout. Fifteen minutes deciding what deserves tomorrow can save days. That is a house line, not a measured saving. Without an active sort, urgency does the sorting. The priorities from the evening sort are what get blocked; the build does not re-derive them.
Non-negotiables first, with travel time. Then important-non-urgent work, the kind that compounds and has no deadline shouting, before the urgent.
Every block gets a measurable intention. “Write two paragraphs of about 250 words” is checkable. That pass/fail is what a vague block lacked. Beginners script the entry minute by minute, then loosen. An intention every thirty to sixty minutes is the house knob; shaky focus uses the thirty-minute end of it.
Overestimate every task by about 25 percent, shrinking toward 10 percent with experience. Underfill the day by about 25 percent: a quarter-hour between tasks, and thirty to sixty minutes unscheduled at the end. Both numbers are starting knobs. The range they come from is wider. They are not laws.
Overfilling costs four ways: an illusion of a productive plan, hidden capacity that never gets seen, estimates that stay corrupted, and the habit of living behind the calendar.
Rest is booked. Skipped relaxation returns as unplanned delay plus guilt.
Important work stays out of high-risk zones: an unproven early morning, a post-drain commute. Mail can live there. If a risky slot must be used, rails go in with it: a five-minute energizer, do-not-disturb, other people told, one space that is only for the block.
Protections are written into the plan. “I’ll try my best at 5:30” guards nothing. The rail is on the calendar or it is not a rail.
Blocks sized for a tired day, not a heroic one, are the prescription. Heroic days are not required. Study Scheduling fills the protected blocks once they exist. A defended block is what makes Flow State reachable.
A week of actual against planned
Repeated failure is an execution problem: entry, energy, environment. It is not a shortage of wanting it. Track actual against planned for a week. Each barrier is accepted or addressed. That week is the only number that calibrates the pads. Most acceptance is premature: discomfort misread as impossibility.
Nine days out of ten is a feel-check, not a score. A plan that completes on ordinary days beats one that works only when everything is perfect. A reader who misses that feel-check shrinks the day. The repair is not grit.
A week of actual against planned is what sizes the slack and writes the rail.
Priority 0, the aim above every daily list
Priority 0 sits above every daily one: core values and a long-term vision. If it drifts, every Priority 1 is aimed wrong. It is an aim-check, not another daily list. The review is every six months. The hunt is for change; the bias assumes stability, especially while life is still being chosen.
What is held is a vision, not a highly specific ten-year goal. The specific target tunnels. Medium-term goals that do not move toward the vision are bad decisions. Re-touching why the work matters, on that same six-month cadence, is what sustains motivation through grind. Worked examples of what a gain should improve live under Priority 0 Examples on Marginal Gains.
A broken day still aimed at Priority 0, because the hit ran downward.
How often to sort
Daily when the week is volatile; weekly when it is stable. Sunday night works while life is stable. Switch to every night when the week changes fast, and sort twice a day if items arrive fast. The planning itself is scheduled: the unscheduled half hour at day’s end doubles as the slot that builds tomorrow.
Price, quit signals, and checkable marks
The system does not fit a day that has no important-not-urgent work, or a reader who already knows the matrix and skips placement. A six-month vision review will feel like a luxury under load.
The price is an evening sort that costs minutes every day, and a top block that is defended even when the afternoon dies.
The first quit signal is the top item becoming what gets dropped when the day breaks, the rule inverted. The second is a trusted place that is empty most days; then drop back to the calendar.
The checkable marks: tomorrow’s first block is an important-not-urgent item that was booked last night, the frog or the wait-starter; nothing under two minutes is still on the list; if the afternoon dies, that block still happened.
How to practice this
- Tonight, sort the running list into one to three priorities. Notice that two is usual, and that the sort reviews the day just spent.
- Book the important item with no deadline first, near the start of the day. Fit urgent work around it. Notice whether that block still happened on a day the afternoon died.
- During the sort, do anything under two minutes and send anything that starts a wait on someone else. Notice that tomorrow’s first block has a name and nothing under two minutes is left on the list.
- Give every block a measurable intention, such as two paragraphs of about 250 words. Notice that the block now passes or fails, where a vague block did neither.
- Overestimate each task by about 25 percent and leave about a quarter of the day unfilled. Notice a quarter-hour between tasks and thirty to sixty minutes free at the end.
- Track actual against planned for one week. Notice which misses were entry, energy, or environment. Resize the pads from that week and nothing else.
Related pages
- Marginal Gains: Priority 0 Examples, the worked list of what a gain should improve.
- Time Management, Attention and Scheduling: cluster home: attention architecture, prioritisation, scheduling. The sort chooses; that cluster schedules the day and protects attention.
- Study Scheduling: fills the study blocks once the protected blocks exist.
- Decision Making: deleting without anxiety.
- Decisional Delays: why the sort happens off the clock, choices kept out of execution time.
Open questions
- How does the evening sort run on a day that has no important-not-urgent work?
- Once volatility drops, is a weekly sort enough, or does a meditation-style block still want a nightly lock?
- 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
- Ainslie, G.; Laibson, D. Present bias / hyperbolic discounting: the trap of reading near deadlines as importance. Names in the footer; the page’s frame is placement, not the literature.
- Eisenhower / Covey as practice: important-not-urgent booked first, because important-non-urgent work is crowded out unless it is blocked before urgency fills the day. The matrix is assumed known; this page owns order of booking.
- Allen, David. Getting Things Done. Capture into one trusted place, and finish anything cheaper to do than to track; provenance of the two-minute exception only. Public practice, not a required purchase, and not a recommended stack.
- 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.
- Kahneman, D., & Tversky, A. (1979). Planning fallacy: people under-estimate how long a task will take. Buehler, Griffin, & Ross later reviews. Direction for the pad; the 25 percent figure is this system’s knob, not theirs.
- Gollwitzer, P. M. Implementation intentions. A specified next action beats a vague block at the cue. Confirmed at Implementation intention.