How Many Projects Can You Run in Parallel and Still Finish?

The short answer: WIP limits work; pick three

David Anderson's Kanban (source) formalised the work-in-progress (WIP) limit principle that lean and software teams have been using for decades to manage parallel work. The finding is consistent across team and personal-productivity literatures: throughput peaks around three to five concurrent items for most knowledge workers, and degrades sharply above that as context-switching cost overwhelms additional capacity. The implication for personal projects is the same. You don't need a permanent rule; you need an honest WIP limit that matches your actual switching cost. For most readers, that limit is three.

Why "more projects = more output" fails

Every additional concurrent project adds switching cost. Loading the context of a project — files, decisions, mental model, current bug — takes real minutes that don't produce output. Two projects cost two context-loads per day; five cost ten or fifteen. The capacity to absorb that overhead is much lower than most readers assume, and the part that suffers is depth — your hands are moving on each project but the quality of the work in each drops because nothing has the sustained attention it needs. Reducing the WIP usually increases total output even though it looks like you're doing less.

A workable personal rhythm

• Three active projects, no more. One that's primary (most of the week), one that's secondary (light maintenance), one that's exploratory (small experiments). New ideas wait in a parking lot until one of the three closes or moves to inactive.

• Different days, not different hours. Switching every two hours costs more than switching every two days. Allocate larger blocks to single projects; the depth this produces beats the variety. Most readers find that two days on the primary, one day on the secondary, half a day on the exploratory works.

• Define "done" or "paused" before adding the fourth. The classic failure is adding without closing. If you want to start a new project, you have to either finish one or formally park one (with a date for when it might resume). The friction of having to choose is the technique.

• Weekly check: which of the three hasn't moved? If a project sits on the list for three weeks without progress, the honest move is to park it. The slot it occupies is more valuable than the slow drift. Drift looks like activity; it isn't.

What "finished" means when nothing is ever final

Many personal projects don't have a clean end state — a side business, a craft practice, a long-term study. For these, define "this iteration is finished" rather than "the project is finished." The iteration ends when a specified output exists (a shipped feature, a body of work to show, a passable proficiency level). When it ends, the project doesn't have to leave the list — but the next iteration is a deliberate choice, not an automatic continuation. That choice is where you reapply the WIP discipline.

Why this pays double for ADHD

ADHD attention has high context-loading cost — the time to get back into a project after a break is longer than for neurotypical workers, sometimes substantially so. The hidden tax on parallel projects is therefore larger, and the same three-project limit that's reasonable for others is closer to mandatory for ADHD readers. The other ADHD-specific gain is the visible parking lot — without it, the felt pressure of "I should also be doing X" persists for everything you're not actively working on, and that pressure damages the work that's in front of you. A clean parked list lets the brain release the load.

FAQ

What if I have a job AND personal projects?

The job is one of the three slots. If the job is full-time, it usually takes one or two slots depending on intensity, leaving one or two for personal work. Pretending the job doesn't count is how the three-project rule gets quietly broken.

What about really small projects?

Anything that needs you to load context counts. A weekend project is a slot; a half-day errand is not. The test is whether you'd need to reorient yourself to resume it. If yes, it's a project; if no, it's a task.

Can I do four if one is in maintenance only?

Yes, if the maintenance one is genuinely light — under an hour a week, no decisions to make, no problem-solving. The slot test is cognitive load, not calendar time. A truly hands-off project barely uses a slot; one you think about every day uses a full one.

How do I let go of a project I love that I can't move on?

Park it explicitly with a re-evaluation date. "Pause this until April; if I want it back then, it returns; if not, retire it." Parking is much less painful than killing and lets you recover the slot without grief work. Most parked projects either return quietly or fade — both are okay outcomes.

What's the smallest version to try this week?

Write down everything you're currently in motion on. Mark the three that get this week. Park the rest with a date. That's it. Most readers find this single audit produces immediate relief — and a clearer view of where the week's energy can actually go.