Working on multiple projects simultaneously feels productive. Progress everywhere. Options open. Momentum diversified.
In reality, it is one of the fastest ways to slow everything down.
Every project carries cognitive context: goals, constraints, open loops. Switching between them incurs a cost. That cost compounds throughout the day.
The single project rule is simple: work on one primary project at a time until it reaches a clear completion point.
This does not mean ignoring all other responsibilities. It means choosing one project as the dominant focus for your deep work.
When focus is unified, progress accelerates. Problems stay warm in your mind. Solutions emerge faster. Quality improves.
Multitasking projects creates the opposite effect. Each session begins with reorientation. Each interruption dissolves momentum. Days feel busy but unproductive.
The resistance to single-project focus is emotional, not logical. It feels risky. What if priorities change? What if you choose the wrong project?
These fears are understandable but overstated. Progress on one completed project almost always beats partial progress on many.
Choose your single project deliberately. Ask which project, if completed, would create the most leverage or relief.
Define what completion means. Not perfection—done enough to move on.
Protect your focus time fiercely. When other projects surface, capture them and return to the current one.
Sequential completion creates visible wins. Wins create motivation. Motivation sustains momentum.
One project at a time produces better results faster. Focus is a force multiplier.
Define “one” at the right level
Most people cannot literally have one project. Work, home, health, and relationships create simultaneous responsibilities. The useful constraint is one primary project per protected focus block or one dominant project per short planning horizon—not neglect of everything else.
Separate maintenance from projects. Paying a bill, answering a required message, and attending a standing appointment may continue while a product launch is the primary project. The rule governs discretionary deep-work capacity.
Choose with a scorecard
Rate candidate projects from 1–5 on:
- value if completed
- urgency or cost of delay
- readiness: whether the next actions and dependencies are available
- strategic fit with the current quarter
- effort remaining, scored in reverse so a smaller finishable project can compete
The score is not an automatic decision. It reveals why a glamorous project may be blocked and why completing an older, nearly finished one might release more capacity.
Set a completion boundary
Write what “done enough to move on” means in observable terms. “Improve website” invites endless polishing. “Publish the revised home page, verify the contact path, and log follow-up ideas” creates an exit.
Also define a review trigger: a critical dependency stalls for three days, a customer need changes, or a deadline moves. Changing projects at a pre-decided trigger is adaptation, not failure.
Keep a parking lot with a cost
Capture other ideas in one parking lot, but add the date and the project they would displace. Review it weekly, not whenever the current work becomes difficult. Delete ideas that no longer feel valuable after the delay.
A ten-day field test
Choose one primary project and reserve the first available focus interval for it on ten workdays. Track minutes lost to project switching, time spent reorienting, and movement toward the completion boundary.
Compare this with the previous ten workdays if records exist. The rule is useful if completion accelerates without creating unacceptable neglect elsewhere.
Sources
- Executive control of cognitive processes in task switching — experimental research on switch costs
- Why is it so hard to do my work? Attention residue when switching tasks — research on attention remaining with a prior task