Starting feels productive because something visible changes immediately.
A new document exists.
A new tab opens.
A new project gets a name.
A new commitment enters the calendar.
A new book moves onto the bedside table.
Finishing is quieter.
It often requires returning to something that is no longer exciting, resolving details, checking quality and resisting the attraction of a new beginning.
This creates a structural problem.
If starting is easier than finishing, active work accumulates.
Quick Read
In one sentence: work-in-progress limits simplify life by capping how many tasks, projects or commitments may remain actively open at once, forcing new work to compete with existing work instead of silently adding another unfinished state.
The idea is well known in Kanban systems, where teams limit the number of work items in progress to improve flow and expose bottlenecks. An empirical study of more than 8,000 work items across five software teams found that lower WIP correlated with shorter lead time, while also showing that productivity relationships were more complicated and that no universal “optimal” WIP number could be inferred. A structured synthesis of Kanban research likewise identifies WIP limits as a central practice while warning that implementation benefits and challenges depend on context.
That nuance matters.
This article is not going to tell every family to keep exactly three projects open.
The transferable principle is:
When active work grows faster than completion capacity, reduce the number of things allowed to remain active.
What Counts as Work in Progress?
Work in progress is not everything you care about.
It is everything currently consuming active coordination, memory, setup or follow-up.
A project can be inactive and safely stored.
A goal can be long-term without occupying today’s work surface.
A book can sit on a shelf without becoming an obligation.
WIP begins when the thing is active enough that the system must keep asking:
- What happens next?
- Who owns it?
- When do I return?
- What is blocked?
- What still needs checking?
Every active item creates coordination load.
Why Too Much WIP Feels Like Busyness
A person with twenty active items can spend the day touching all twenty and finishing none.
That feels busy because context switches are visible.
Research on task switching explains why this can be cognitively costly: switching requires control processes and can create interference. Reviews of interruptions and task transitions similarly emphasise that attention must move between goal systems, with cognitive, emotional and performance consequences.
WIP limits do not eliminate switching.
They reduce how many unfinished goal states are simultaneously competing for return.
Node 1: Limit Active Projects
Projects multiply easily.
Learn a language.
Redesign the room.
Start a side business.
Organise the photos.
Train for an event.
Read six books.
None is bad.
The problem is simultaneous activation.
A project limit says:
Before activating another project, finish, pause, delegate or deliberately drop one of the current active projects.
The inactive backlog can remain large.
The active surface remains small.
Node 2: Limit Active Tasks Inside a Project
One project can contain too much WIP too.
Write introduction.
Design slides.
Email reviewer.
Research sources.
Edit appendix.
Build spreadsheet.
If everything begins, the project becomes a field of partially constructed pieces.
A WIP rule can require one or two current tasks to reach a defined state before another is opened.
This exposes the real bottleneck.
Maybe research is not the bottleneck.
Maybe review is.
Starting more research does not repair a review bottleneck.
Node 3: Limit Household Improvement Projects
Homes can become permanent renovation queues.
Half a cupboard reorganised.
A broken chair waiting for repair.
Paint bought but not used.
Documents partly scanned.
Storage boxes waiting for labels.
A household WIP limit might be:
Only two nonessential improvement projects remain active at a time.
The number is not universal.
The principle is that the house should not contain unlimited unfinished interventions.
Node 4: Limit Student Subject WIP
Students can open too many learning loops.
Monday: start algebra revision.
Tuesday: start comprehension notes.
Wednesday: start chemistry flashcards.
Thursday: start history summaries.
Friday: nothing has reached a verification point.
A better unit is the learning loop:
diagnose → practise → retrieve → correct → verify → schedule next return.
Finish that cycle on a manageable number of topics before activating many more.
This does not mean studying only one subject all week.
It means limiting unresolved learning repairs.
Node 5: Limit Decision WIP
Decisions can remain active too.
Which school?
Which laptop?
Which holiday?
Which enrichment?
Which repair option?
If five significant decisions remain simultaneously under research, comparison expands.
Limit decision WIP by closing one search before opening another where possible.
This works with Enough: define stopping rules so a decision can leave WIP.
Node 6: Limit Communication WIP
Conversation threads are open loops.
Some require your response.
Some require another person’s response.
Some are finished but remain visible.
Closure helps convert these into states.
WIP limits add a behavioural rule: do not create ten new request threads while five important conversations still lack clear next states.
Node 7: Limit Learning Resources in Active Use
A student can own many books and use few.
The problem appears when many resources are active simultaneously.
Three textbooks open.
Four websites bookmarked.
Two tuition worksheets.
Five video channels.
One AI chat.
The student spends more time choosing the next resource than learning from one.
Limit the active learning stack:
- one primary syllabus/reference source;
- one practice source for the current target;
- one correction/explanation route;
- additional resources only when the current stack cannot answer the identified need.
The exact stack varies.
The principle is fewer simultaneous sources competing to define the task.
WIP Limits Are Not Backlog Limits
You may have fifty ideas.
You do not need fifty active projects.
You may have twenty books you want to read.
You do not need twenty books accusing you from the bedside table.
A backlog can be large if it is genuinely inactive and reviewed appropriately.
The WIP limit protects the active surface.
WIP Limits Reveal Bottlenecks
When you cannot start new work, an uncomfortable question appears:
Why is the current work not finishing?
Maybe you are waiting for another person.
Maybe the task is too large.
Maybe quality criteria are unclear.
Maybe you lack expertise.
Maybe every day contains too many interruptions.
Maybe the project should be dropped.
Without a WIP limit, these bottlenecks can remain hidden because new work keeps creating the sensation of forward motion.
WIP Limits and Margin
Margin is uncommitted capacity.
WIP limits protect that margin from being consumed by partially active work.
Ten half-active projects can consume attention even if none fills the calendar today.
WIP limits protect invisible capacity as well as visible time.
WIP Limits and Triage
Triage decides which work most deserves scarce active slots.
WIP limits make those slots scarce enough that the decision matters.
When the limit is full and a genuinely higher-priority task arrives, something must happen explicitly:
- finish something;
- pause something;
- drop something;
- delegate something;
- or refuse the new task.
This is far healthier than pretending the new task can simply join the pile for free.
WIP Limits and Ownership
Ownership matters because unfinished work without an owner becomes invisible WIP.
A project should not count as “someone is handling it” unless someone actually owns its next state.
How to Choose a WIP Limit
There is no universal number.
The empirical Kanban study is a useful warning: lower WIP correlated with shorter lead time, but productivity relationships were not simple, and an optimal WIP limit was difficult to identify.
For personal life, choose a limit experimentally.
- How many active items can you hold without repeatedly forgetting state?
- How much switching is required?
- What completion rate is realistic?
- What work is genuinely parallel because it waits on external events?
- What margin must remain for exceptions?
Start lower than current overload, not lower than reality.
Waiting Is Not the Same as Active
A task waiting for someone else need not occupy an active slot if it has a trusted waiting state and follow-up trigger.
This is another reason closure architecture matters.
Separate:
- active;
- waiting;
- scheduled;
- paused;
- backlog;
- done.
Otherwise the WIP count becomes meaningless.
WIP Limits for Students
A practical student limit might apply to unresolved repairs rather than subjects.
For example:
No more than three active weak-topic repairs at once. New weak topics enter triage, but only the highest-value ones become active until a current repair reaches verification.
This prevents a diagnostic test from producing twenty simultaneous study projects.
WIP Limits for Families
Families can use WIP limits for:
- household improvement projects;
- major purchases under research;
- new extracurricular commitments;
- repairs requiring coordination;
- large administrative tasks.
The point is not bureaucratic counting.
It is creating a visible moment when “one more thing” must confront the existing load.
WIP Limits for Work
At work, WIP limits are most useful when paired with visible flow.
New tasks should not enter active work simply because a stakeholder asks loudly.
If capacity is full, the requester should see the trade-off:
Which current item should pause so this can start?
That question turns hidden overload into explicit prioritisation.
When WIP Limits Fail
- Arbitrary numbers: the limit is copied from someone else without relation to actual work.
- Fake pausing: tasks are labelled paused but still consume attention and meetings.
- Waiting confusion: externally blocked work remains counted as active without reason.
- No triage: low-value work occupies slots while high-value work waits.
- No finishing criteria: items never leave because “done” is undefined.
- Hidden channels: new work bypasses the limit through messages or favours.
- Limit gaming: large work is split artificially just to satisfy the number.
- Overrestriction: the limit is so low that useful parallelism is destroyed.
A Seven-Day WIP Experiment
- Day 1: list every genuinely active project or repair.
- Day 2: move waiting, paused and backlog items out of active WIP.
- Day 3: choose a provisional active limit below current overload.
- Day 4: refuse to activate new work without freeing a slot.
- Day 5: observe what bottleneck prevents completion.
- Day 6: repair one bottleneck rather than starting another task.
- Day 7: adjust the limit based on lead time, quality, stress and useful parallelism.
Further Reading and Evidence
- Sjøberg, D. I. K. (2018). An empirical study of WIP in Kanban teams, ACM/IEEE ESEM.
- On the benefits and challenges of using Kanban in software engineering: a structured synthesis study.
- Kanban in software engineering: A systematic mapping study.
- Kiesel, A. and colleagues. Control and interference in task switching—A review.
- Leroy, S., Schmidt, A. M. & Madjar, N. Interruptions and Task Transitions.
Frequently Asked Questions
What is a work-in-progress limit?
It is a cap on how many items may remain actively in execution at one time. New work waits, replaces existing work, or enters another state until capacity opens.
What is the best WIP limit?
There is no universal number. Choose experimentally based on task size, switching cost, useful parallelism, completion rate and required margin.
Does waiting work count?
Not necessarily. If the item is genuinely waiting on an external event and has a trusted follow-up state, it can be separated from actively executed WIP.
How does this help students?
It prevents every identified weakness from becoming an active study project simultaneously and encourages learners to complete diagnosis–practice–verification loops before opening many more.
Final Thought: Open Less So More Can Actually Close
There is a kind of ambition that measures itself by how many things have begun.
A simpler ambition asks how many useful things can reach completion without destroying margin.
Starting creates possibility.
Finishing creates capability.
When the system is full, the next act of progress may be refusing to start.