What to do with a task you keep postponing

Updated 2026-09-12

The short answer

A task that has survived two weeks of being scheduled later is not waiting for more resolve. It is telling you something specific, and the useful move is to find out which of four things it is.

  1. It is not actually one task. It is a project wearing a task's name.
  2. It is blocked, and some part of you knows it.
  3. It is genuinely low priority, and the honest action is to delete it.
  4. It has no first move named, so there is nothing to start.

Each has a different fix, and "try harder tomorrow" is the fix for none of them.

Urgent work keeps arriving ahead of the important task, so it never reaches the front. Aging is the fix WITHOUT AGING the important thing new urgent work keeps arriving on the left. The dashed item never runs. It is not forgotten — it never reaches the front. That is starvation. WITH AGING the important thing a waiting item's priority rises until it must run. Every operating system does this. A standing first slot is the same idea, by hand.
Urgent work keeps arriving ahead of the important task, so it never reaches the front. Aging is the fix

Working out which one it is

Say the first thirty seconds out loud. Open the spreadsheet and check the Q3 column. If you can say it, it is not (4). If you cannot, that is the whole problem and naming it takes less time than another day of avoiding it.

Ask what has to be true before it can be finished. If the answer involves someone else, it is (2) — and the real task is the short one that unblocks it, which is usually a message. This is the cheapest possible discovery and people skip it for weeks.

Ask how long it would take if you started now. If you cannot answer, it is (1). A task you cannot estimate is not understood yet, and understanding it is the actual first item. More on what an estimate is for.

Ask what happens if it is never done. Sometimes the honest answer is: nothing. That is (3), and the correct action is to delete it rather than carry it. A list that keeps things nobody will ever do costs attention every time it is read.

The one that is really none of those

Sometimes it is clear, unblocked, small, and matters — and you still will not do it. That is worth naming honestly rather than dressing as a planning problem.

Two things still help. Make it smaller than feels reasonable — ten minutes, not ninety. The resistance usually scales with the imagined size rather than the real one, and ten minutes of a thing avoided for a fortnight is an enormous improvement on the fortnight. And put it first, because a thing avoided does not become more likely at four o'clock; it accumulates the weight of having been avoided all day.

What does not help is reading the difficulty as evidence about your character. It is a task you have not done.

Why the calendar keeps eating it

There is a structural reason this happens to specific tasks rather than randomly, and it is worth knowing so you stop taking it personally.

Work with a deadline is loud; work without one is silent. A queue with no correction always serves the loud item first, so the quiet task never reaches the front however important it is. The formal name is starvation and it happens in systems with no willpower to lack. The mechanism and the standard fix.

The standard fix is aging — a waiting item's priority rises until it must run. Done by hand, that means the postponed task gets a fixed slot first, before the day fills, rather than the leftover time at the end. Leftover time is where postponement happens, by definition.

A five-minute procedure

  1. Write the task exactly as it sits on your list.
  2. Rewrite it as the first physical action. If you cannot, the real task is "work out what this actually involves" — put that on the list instead.
  3. Check whether it is waiting on anyone. If it is, do the unblocking thing now; it is probably two minutes.
  4. Decide if it matters. If not, delete it and feel nothing.
  5. If it survived all four, give it the first slot tomorrow. Not a slot. The first one.

Where to go next

Using this in Decide One

Decide One keeps what you did not choose visible rather than letting it sink, because a system that hides unchosen work is running the exact failure it should be correcting.

A line you did not finish is unfinished. It is not marked against you, and a day you did not open is not counted.

Open Decide One — free to use, with no account. Nothing you write leaves your device.

Decide One is a priority instrument. Bring the day into view, choose a method, give the first thing real time.

Open it — free, nothing to sign up for