How do you manage multiple side projects at once?

The approach that survives contact with real life is a rotation, not a juggle: designate one lead project that gets your best hours, give every other active project a minimum weekly heartbeat so it stays warm, park anything you can't heartbeat without guilt, and rebalance the roles once a week in about fifteen minutes. The goal is that every project is either moving, warm, or deliberately parked, and none of them are silently dying.

How many side projects is too many?

The honest limit is set by your weeks, not your ambition: one lead project plus one or two warm projects is sustainable for most people alongside a job or studies. More than that and the heartbeats alone consume the time that should be going to the lead. There is no limit on parked projects; parking is free.

Should I kill a side project that isn't moving?

Not necessarily. Most stalled projects don't need killing, they need honest parking: an explicit decision that the project is dormant, with a note on why and what would wake it. Killing is for projects you no longer want even in imagination. Parking is for projects whose time isn't now. The distinction removes most of the guilt.

How to Run 3 Side Projects Without Losing Your Mind

The problem was never your ambition. It's that you're trying to juggle when you should be rotating.

You don't run three side projects at once. You run one, keep two warm, and rotate. That single reframe, from juggling to rotation, is most of what separates the people who ship multiple things a year from the people with a graveyard of half-finished repos and abandoned drafts. The rest is a fifteen-minute weekly ritual and a way of parking projects that doesn't feel like admitting defeat. This piece is the whole system.

First, some reassurance you've probably never been given: wanting several projects is not a character flaw to be fixed. The advice industry treats multi-project people as distractible children who need to be taught focus. But some of us are wired to have three fires going, and the polymaths, indie hackers, and serial creators of the world get a lot done precisely because the fires feed each other. The problem was never the number of projects. It's that nobody teaches the logistics.

Why multiple projects quietly die

Understand the four failure modes and the system that follows will feel obvious rather than clever.

Context switching eats the hours you thought you had. Ten hours a week spread as one daily hour across three projects is not ten hours of work. Every switch pays a re-entry tax: reloading where you were, what you were doing, why. Split three ways daily, a huge share of your time goes to remembering instead of making. The same ten hours, concentrated, produce embarrassingly more.

Guilt distributes itself across everything. When all projects are equally "active," working on any one of them means neglecting two. You feel vaguely guilty during every session, which makes every session worse. Three active projects means three sources of guilt and zero sources of permission.

Untouched is indistinguishable from dead. A project you haven't opened in three weeks has no heartbeat. You don't know if it's resting or rotting, and the uncertainty itself repels you: opening it means finding out how bad it's gotten. So you don't open it, and the uncertainty compounds. This is how projects die: not by decision, but by avoidance of a status check.

Sessions end without a hook. You stop working when you're tired, which is usually at a hard part or a dead end. Next session begins exactly there, at the least inviting spot in the whole project. No wonder starting feels like wading into cold water.

Projects die not by decision, but by avoidance of a status check.

The rotation system

Five rules. Together they take about fifteen minutes of overhead a week.

Crown one lead project.

At any moment, exactly one project holds the crown: it gets your best hours, your default yes, and the majority of the week. Not forever, just for now. The crown can move weekly or monthly, but it is never shared. The moment two projects are "both the priority," you're back to juggling, and juggling is the disease. Choosing a lead feels like betraying the others. It's the opposite: it's the only arrangement under which the others survive, because they stop bleeding guilt into each other.

Give everything else a heartbeat.

A warm project gets a minimum viable touch each week: one small task, thirty minutes, enough to keep the context alive and prove the pulse. Answer the open issue, sketch the next screen, write one paragraph. The heartbeat is not progress theater; it's what makes the difference between "resting" and "rotting," and it keeps re-entry cheap for the day the crown rotates to it. If you can't spare a weekly heartbeat for a project, that's not a scheduling problem. That's the project telling you it belongs in the third category.

Park without shame.

Parking is an explicit, written decision: this project is dormant, here's why, and here's what would wake it ("after the launch," "when winter comes," "if the client season slows"). A parked project costs nothing: no heartbeat, no guilt, no pretending. The graveyard feeling that haunts multi-project people comes almost entirely from projects that were never honestly parked, only silently abandoned. The difference between the two is one sentence of honesty, and it's the difference between a portfolio and a burden. Parked is a real status, not a euphemism for dead.

Never end a session without leaving a hook.

The last two minutes of any work session belong to your future self: write down the exact next physical action, mid-thought if possible. "Finish the signup validation, the bug is in line 84" beats "continue auth work" by a mile. Hemingway famously stopped writing mid-sentence for exactly this reason. A session that ends with a hook is a session that took care of the next one, and across three projects, hooks are what make rotation cheap instead of costly.

Rebalance weekly, in fifteen minutes.

Once a week, look at the whole board and ask three questions. Does the crown move? (Usually no; changing leads every week is juggling in disguise.) Did every warm project get its heartbeat, and if one didn't for the second week running, does it move to parked? And does anything parked want to wake up? This tiny ritual is the entire management layer. It replaces the constant background hum of "should I be working on the other thing?" with a decision that's already been made, which, as the manifesto argues, is where most willpower is actually saved.

The math of small beats

Here's the part that requires faith at first and becomes obvious in hindsight. A project that receives one focused block a week for a year gets fifty-plus sessions. Fifty sessions is a shipped app, a finished manuscript draft, a real body of work. Meanwhile the "all in until I burn out, then nothing for two months" pattern, averaged honestly, delivers less than half of that, and feels dramatically worse.

Rotation looks slow week to week and fast year to year. The juggle looks fast week to week and is, over any honest accounting period, mostly stationary. You are not choosing between speed and sanity. Sanity is the speed.

One more effect worth naming: visible momentum on any project spills over. Shipping a small win on the lead makes the warm projects feel more possible, not less, because what you're building across all of them is the same underlying asset: the identity of someone whose projects move. Guard that identity with heartbeats, and it guards you back.

The short version One crown, weekly heartbeats for the warm ones, honest parking for the rest, a hook at the end of every session, and fifteen minutes of rebalancing a week. Rotation looks slow week to week and fast year to year. The juggle is the opposite, and the juggle is lying to you.

Questions people ask

How many projects can one person actually sustain?

Alongside a job or studies: one lead plus one or two warm is the honest ceiling for most people, because heartbeats cost real time. Full-time on your own work, you can sometimes hold a lead and three or four warm projects. Parked projects are unlimited; they cost nothing but the honesty of parking them. If your warm list needs more time than your lead, the labels have stopped meaning anything.

What if two projects both have deadlines?

Deadlines temporarily overrule the system: the nearest hard deadline wears the crown, the other deadline project gets scheduled blocks rather than a mere heartbeat, and everything else drops to parked until the storm passes. The system is for normal weeks. In deadline weeks, protect only what's on fire, and forgive yourself the rest; the rotation will still be there when you're back.

I feel guilty every time I park something. Any advice?

Write the wake condition down and reread it when the guilt arrives. Guilt thrives on vagueness ("I'm abandoning it") and starves on specifics ("it wakes after the launch, as decided on the 15th"). It also helps to reread your record of what the lead project shipped during the parked months; the parked project didn't lose that time, you spent it, on purpose, somewhere that mattered more right then.

Does this work with a full-time job?

It works best with one, honestly, because scarcity forces the discipline the system encodes. With ten spare hours a week: six to eight on the lead in two or three concentrated blocks, a thirty-minute heartbeat each for one or two warm projects, fifteen minutes of rebalancing. That's a sustainable creative life alongside employment, and it ships things, which is more than most unsustainable ones do.

A command center for all of it

Wardesk holds every project in one calm place: the lead, the warm ones, and the parked, each with its next step waiting. The daily briefing answers "which one, today?" so the rotation runs itself. It's free to try.

Try Wardesk free → No credit card. Your data stays yours.