Priority 0+1 System

Priority 0+1 books important work with no deadline first, and lesser tasks take the hit on a broken day. The matrix is not the invention. Placement is. Urgent work feels important; the work that would have mattered never gets a slot unless it is booked first.

Placement, not the matrix

Intuition prioritises badly. The mind reads urgent as important — 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, except a job under two minutes, which is done on the spot.
• Neither: delete.

Deleted items re-enter if they are genuinely needed, like a re-downloaded file. 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 page. Anyone who has seen the matrix already owns them. What this page adds 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.

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.

Most days only one or two things finish. Two is usual. Because they are the highest-importance items, output stays steady.

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.

Nightly sort and Priority 0

Each evening, a running list is sorted into one to three priorities. Two is usual. The sort doubles as a review of the day just spent. Task Management collects the inbox this page sorts.

Daily when the week is volatile; weekly when it is stable. Slack stays in the day. Building a Schedule That Survives owns how that slack is sized and how a vague block dies; this page only names that slack has to exist.

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.

Study Scheduling fills study blocks once the rank exists. Deleting without anxiety draws on Decision Making. The cluster home is Time Management, Attention and Scheduling.

This is the wrong page if the day has no important-not-urgent work, or if the matrix is already known and placement is skipped. A six-month vision review will feel like a luxury under load. The price is an evening sort, and a top block that is defended even when the afternoon dies. The quit signal is the top item becoming what gets dropped when the day breaks — the rule inverted. The checkable marks: tomorrow’s first block is an important-not-urgent item that was booked last night; if the afternoon dies, that block still happened.

A broken day still aimed at Priority 0, because the hit ran downward.

Links into the knowledge base

• 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.
• Task Management — collects the inbox this page sorts.
• Building a Schedule That Survives — turns the ranked output into a calendar; owns slack and vague blocks.
• Study Scheduling — fills study blocks.
• Decision Making — deleting without anxiety.

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?

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. The matrix is assumed known; this page owns order of booking.
• Allen, D. Getting Things Done — provenance of the two-minute exception only. Not a recommended stack.