Why do I procrastinate even on small tasks?
The task may take five minutes. Carrying it can take hours. The loop begins when the task becomes a repeated decision instead of a direct finish.
The message needs a short reply. The form needs one field. The object needs to be returned. None of it is large enough to explain why it stays open all day.
You see the task, decide not now, and carry it forward. When it reappears, it no longer contains only the original action. It also contains the memory that you have already delayed it.
A small task can therefore become mentally larger while remaining physically small.
Postponement turns one action into many decisions
The repeated cost is not only the unfinished task. It is the sequence of reopening, remembering, judging and postponing.
That makes the task feel more loaded each time even though the execution itself has not changed.
The useful distinction is between tasks that need planning and tasks that are already fully executable. Small procrastinated tasks often belong to the second group.
Where the loop actually turns
The turn is the first unnecessary delay after the next action is already clear.
Once the task is moved into an undefined later, it loses a concrete place in the day and becomes a recurring interruption instead.
The solution is not to feel more motivated. It is to remove the repeated choice.
Every return added another layer without changing the work itself.
Why making a bigger list can keep the loop alive
Moving the task into a list can be useful when the list creates a real time or place. A list that only stores the task preserves the same open decision.
Breaking an already tiny task into more steps can also create unnecessary ceremony around something that was ready to close.
The stronger move is either finish it now or assign one exact re-entry point. Undefined later is the part that keeps the loop running.
Use a closing rule, not a motivation rule
Choose a simple threshold for tasks that are genuinely ready: for example, one visible action that can be completed in a few minutes without new information.
When such a task appears, either complete it or give it an exact place: a named block, a calendar time or a clear batch.
This is not about doing every incoming task immediately. It is about preventing small executable actions from becoming indefinite background obligations.
REMOVE THE UNDEFINED LATER.
- 1Ask whether the next action is already fully clear.
- 2Finish it directly when the cost is genuinely small.
- 3If not now, assign one exact time or batch.
- 4Remove the task from view once that placement is real.
Do not use this rule to let minor incoming tasks interrupt protected deep work. Capture them into a real batch instead.
What to observe today
The same small task is reconsidered several times without gaining a place.
The task enters a list but still has no exact re-entry point.
The task is either finished or assigned once and stops demanding repeated decisions.
The task depends on missing information, another person or a larger decision that is not yet available.
Small-task procrastination grows when one executable action is repeatedly converted into an undefined future choice.
Serkan Elbasan
Serkan Elbasan is the founder of the Institut für Kognetik and an independent researcher working on recurrence, structural invariance, rule–state separation and the formal conditions under which systems can modify their own rules.