Default new requests to tomorrow

Unless something is genuinely urgent, new work goes to tomorrow — not today.

Why it works

Most incoming requests feel urgent but are not time-critical. Defaulting them to tomorrow breaks the reflex that treats "new" as "now," which is the primary driver of reactive work expanding to fill the day. By the time tomorrow arrives, many items resolve themselves or reveal their true priority, so the list self-curates rather than requiring constant triage.

How to do it

1. When a new task arrives, ask: does this need to happen today, or does it just feel that way?
2. If it is not genuinely time-critical, add it to tomorrow’s list without deliberation.
3. Reserve a "will-do-today" exception only for true deadlines or genuine emergencies.
4. At day’s end, review tomorrow’s list and pre-commit to what you will actually do.

Evidence

Practitioner rule with plausible grounding in urgency-bias and planning fallacy research: people systematically overestimate how many tasks need to happen today and underestimate how much today’s commitments cost. The "defer by default" heuristic is Forster’s mechanism for correcting that bias. (mechanistic)

Whether deferring most requests actually frees more time without damaging relationships depends heavily on role and organizational culture.

Common mistake

Classifying nearly everything as "urgent" within the first week, which recreates the original problem while adding a labeling step in front of it.