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
- List your active projects and pick a small cap (e.g. no more than three).
- Refuse to start a new one until an existing one is genuinely finished.
- 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.
Practice this with IX Coach
7 days free, then $40/month (~$1.30/day).
More practices for Four Thousand Weeks, Made Practical
- Pay yourself first — with time
Take time for what matters off the top, before the day’s demands consume it.
- Embracing necessary missing-out
Accept that every yes is a thousand noes — and choose anyway.
- Settling on purpose
Make a real, binding choice instead of keeping every option open forever.
- Treating rest as worthwhile in itself
Allow leisure that has no payoff, instead of optimizing every hour for productivity.
- Cosmic insignificance therapy
Use the scale of time and the universe to loosen the grip of impossible standards.