Letting yourself finish and stop

Choose a small number of projects and actually complete them before adding more.

Why it works

Open projects multiply faster than they close, leaving a perpetual backlog that drains attention and produces no sense of completion. Capping work-in-progress and finishing before starting forces the unavoidable triage that finitude demands, and finishing delivers the closure that a sprawling, never-done list cannot.

How to do it

1. List your active projects and pick a small cap (e.g. no more than three).
2. Refuse to start a new one until an existing one is genuinely finished.
3. Let the projects that do not make the cap wait — openly, not secretly.

Evidence

Echoes work-in-progress limits from Kanban and the attentional cost of unfinished goals. Mechanistic: capping concurrent work reduces context-switching and the intrusion of open loops. (mechanistic)

Mechanistic; the specific cap is a heuristic, and some life roles legitimately require many simultaneous threads.

Sources

• Masicampo & Baumeister (2011), unfulfilled goals intrude on attention, Journal of Personality and Social Psychology

Common mistake

Keeping a long "open" list and telling yourself you are working on all of it, when really nothing is progressing to done.