How to Manage Multiple Side Projects: A 5-System Operating Model (2026)
Juggling 3+ side projects? Learn the relay-race system for managing multiple side projects without burning out, plus how to kill, pause, or ship each one.
Most people don't fail at managing multiple side projects because they lack time. They fail because they treat a stack of projects like a stock portfolio to balance, when it should be run like a relay race: one project in the lead lane at a time, the rest held in a steady, low-effort state until it's their turn.
That reframe is the whole operating model. Below are five systems (the Ledger, the Relay, the Rhythm, the Autopilot, and the Dashboard) that replace "a little bit of everything every week" with a structure that actually finishes things.
Why Managing Multiple Side Projects Feels Impossible (It's Not a Time Problem)
The hidden cost of context-switching
Every time you move from one project's codebase, customer list, or mental model to another, you pay a tax before you do any real work: reloading context, remembering where you left off, and re-establishing momentum. Researchers who study multitasking and attention, including work summarized by the American Psychological Association, have long documented that switching between unrelated tasks carries a measurable cognitive cost compared to staying on one task. Run five projects a little each day and you're paying that tax five times before lunch, and you never get far enough into any one of them to hit a productive groove.
Why 'balance' is the wrong goal
"Balance" implies every project deserves equal attention this week. It rarely does. One project might be one customer conversation away from its first sale. Another might just need its backups checked once a month. Treating them identically means the urgent one stalls while the dormant one gets attention it doesn't need. The goal isn't balance, it's sequencing: giving each project the attention it needs, when it needs it, not on a fixed rotating schedule.
The myth of the parallel portfolio
Investors can hold ten stocks at once because the stocks don't need their personal attention to perform. Side projects aren't like that. Each one needs a founder's hands-on decisions, and hands can only be on one keyboard at a time. The "portfolio" mental model quietly convinces people they're making progress on everything, when in reality they're making real progress on nothing and calling the scattered activity "diversification."
System 1: Take Inventory: Audit Every Project Before You Manage Any
The one-page project ledger
Before you can sequence projects, you need to see all of them on one page: name, current state, last meaningful action, and next meaningful action. Tools like Notion or even a plain spreadsheet work fine here. The point isn't the tool, it's forcing every project out of your head and onto a single surface where you can compare them honestly.
Scoring each project: momentum, money, meaning
Once every project is listed, score each one on three axes so the comparison isn't just a gut feeling.
| Score | Momentum (is it moving?) | Money (is it earning or close?) | Meaning (do you still want it?) |
|---|---|---|---|
| High | Shipped something in the last 2 weeks | Revenue or signed customers | Still excites you to open it |
| Medium | Shipped something in the last month | Clear path to first dollar | Neutral, but not dreading it |
| Low | No activity in 60+ days | No plausible revenue path visible | You avoid opening it |
Spotting zombie projects you should have killed
A zombie project scores low across all three columns but still occupies a tab, a subscription, and a slice of guilt every week. It isn't advancing and it isn't dead, it's just costing you attention by existing. Flagging these honestly during the audit is what makes the rest of the system work, because every zombie you don't kill is a project silently competing for the slot that should go to something with real momentum.
System 2: The Relay-Race Model: Run One Project Hard, Not All Projects Lightly
Active vs. maintenance vs. dormant tiers
Every project in your ledger belongs in one of three tiers at any given time, and only one project at a time should sit in the top tier.
| Tier | What it gets | Typical time commitment |
|---|---|---|
| Active (the lead lane) | Daily focused work, your best energy hours | 60-80% of project time budget |
| Maintenance | Scheduled check-ins, automated alerts | A fixed block once a week or less |
| Dormant | Nothing, deliberately, until revisited | None, parked on purpose |
Choosing your single 'primary' each sprint
Pick the one project moving into the active tier based on your ledger scores, not on whichever one is loudest in your head that day. A good default rule: the project with the highest momentum plus money score gets the lead lane next, because it's closest to a real outcome. A project can only graduate into the lead lane during a scheduled review, never mid-week on a whim.
How long each project stays in the lead lane
Give the active project a fixed sprint, commonly two to four weeks, with a defined outcome to hit before it rotates back to maintenance. An open-ended "I'll work on this until it's done" lead lane is how one project quietly absorbs a year while the others go dormant without anyone deciding that on purpose.
System 3: Build a Lightweight Operating System for Your Projects
One capture inbox, many project queues
Every idea, task, or "I should fix that" thought goes into a single capture inbox first, regardless of which project it belongs to. Apps like Todoist or Trello work well for this. Sorting into the right project queue happens later, during your weekly review, not in the moment, so a stray idea about Project C never derails the focused block you're spending on Project A.
The weekly review ritual (20 minutes)
Once a week, empty the capture inbox, update the ledger, and confirm which project stays in the lead lane versus which one rotates. Todoist's own guide to the weekly review is a solid template for the mechanics even if you don't use their app. Twenty minutes is enough if the ledger from System 1 already exists, because you're updating a structure, not rebuilding one from scratch.
Batching by energy type, not by project
Group similar tasks across projects by the kind of energy they require: deep creative work in one block, admin and email in another, calls in a third. A maintenance-tier project's quarterly tax filing and your active project's customer calls can share an "admin block" even though they belong to different ventures, because the switching cost between similar task types is far lower than between dissimilar ones.
System 4: Automate and Delegate the Maintenance Tier
What to automate first (billing, backups, deploys)
Maintenance-tier projects should run with as little manual intervention as possible. Prioritize automating the things that cause real damage if missed: billing and subscription renewals, data backups, and deploys or updates. Platforms like Basecamp for project tracking or built-in scheduled jobs on your hosting provider can carry most of this load without you remembering to do it manually.
Monitoring so dormant projects don't rot
A dormant project doesn't need daily attention, but it does need a smoke alarm. Simple uptime or error monitoring, even a basic scheduled check that emails you if something breaks, is the difference between a project that's safely parked and one that's quietly dying while you're not looking.
When to pay for help vs. do it yourself
Pay for help on anything recurring, mechanical, and outside your core skill (bookkeeping, routine customer support replies, basic content updates). Keep doing it yourself anything that requires judgment specific to that project's direction. The test: if a competent freelancer with a short brief could do it correctly, delegate it; if it requires knowing the whole backstory, keep it.
See All Your Projects in One Place (Mid-Article CTA)
Why a single dashboard beats five tabs
If your projects live across five different logins, spreadsheets, and note apps, the ledger from System 1 decays the moment you stop updating it by hand. A single dashboard that pulls in real status automatically removes the maintenance burden of maintaining your own maintenance system.
Set up your project control panel with carbonapps.com
This is exactly the gap carbonapps.com is built to close: one place to see every project you're running, instead of stitching together screenshots from five different tools every Sunday night during your weekly review.
Track status, metrics, and next actions at a glance
The goal is the same one-page view from your ledger, except it updates itself. Status, key metrics, and the next action for each project, active, maintenance, or dormant, visible in one glance instead of five logins.
System 5: Decide What to Kill, Pause, or Ship
The sunk-cost checklist
Time and money already spent on a project are not a reason to keep running it. James Clear's writing on the sunk cost fallacy is a useful gut check here: ask only whether you'd start this project today, from scratch, knowing what you know now. If the answer is no, the money already spent doesn't change that answer.
Graceful shutdown vs. indefinite pause
A table helps separate the three real outcomes, because "I'll get back to it" without a plan is just a kill you haven't admitted to yet.
| Outcome | When it fits | What you do |
|---|---|---|
| Kill | Low momentum, low money, low meaning on the ledger | Cancel subscriptions, archive code, notify any users, close it out |
| Pause | Still meaningful or promising, but genuinely not now | Set a specific review date, move to dormant tier, document where you left off |
| Ship | Active tier, close to a defined "done" | Lock scope, cut remaining features, release what exists |
Defining 'done enough' to ship
Set the finish line before you start the sprint, not after you're tired of the project. "Done enough" means it solves the original problem for the original user, even if your list of nice-to-haves is still long. Founders who study product launches, including resources from Y Combinator's startup library, consistently point to shipping something narrow and real over polishing something broad and theoretical.
Protect Your Focus: Avoiding Burnout Across Projects
Scheduling recovery, not just work
Recovery time needs to be on the calendar with the same seriousness as a client call, not left to "whatever's left over." Researcher and author Cal Newport, who writes extensively about deep, focused work, has argued that the quality of your working hours depends directly on genuinely disconnecting during your non-working ones.
The 'no new projects' rule and when to break it
Set a default rule: no new side project starts until an existing one is killed, paused, or shipped. The exception is rare and deliberate: a genuinely time-sensitive opportunity that passes the same ledger scoring as everything else, not just something shiny that showed up this week.
Signs you're over-committed
Watch for the same handful of warning signs across your projects: you dread opening tools you used to enjoy, your weekly review keeps getting skipped, every project feels "behind," and your maintenance tier keeps growing because nothing ever graduates back out of it. Any one of these is a signal to run the audit again, not to add a sixth project.
Your 30-Day Plan to Get All Side Projects Under Control
Week 1: audit and ledger
Build the one-page ledger from System 1 for every project you're currently running, including the ones you're embarrassed to admit are still technically alive. Score each one honestly on momentum, money, and meaning.
Week 2: set tiers and automate
Assign every project to active, maintenance, or dormant. For anything landing in maintenance or dormant, spend the week automating or delegating the tasks identified in System 4 so those tiers can genuinely run with minimal input.
Weeks 3-4: run your first relay sprint
Put your highest-scoring project in the lead lane for a two to four week sprint with one defined outcome. Everything else stays in maintenance or dormant, untouched except for its scheduled check-in.
| Week | Focus | Output |
|---|---|---|
| 1 | Audit and ledger | Every project scored and listed on one page |
| 2 | Tiers and automation | Active/maintenance/dormant assigned, maintenance tasks automated |
| 3-4 | First relay sprint | One project in the lead lane, a shipped or decided outcome |
Frequently Asked Questions
How many side projects can one person realistically manage at once? There's no fixed number, but the relay model suggests most people can realistically keep one project active, two or three in maintenance, and anything beyond that should be dormant or killed. The constraint isn't how many you can track, it's how many can get real, hands-on attention in a given week.
Should I work on all my side projects every day or focus on one at a time? Focus on one at a time in the active tier. Spreading daily effort across every project usually means none of them get the sustained attention needed to actually finish or ship.
How do I know when to kill a side project instead of pausing it? Use the sunk-cost checklist: if you wouldn't start the project today knowing what you know now, and it scores low on momentum, money, and meaning in your ledger, it's a kill, not a pause. Pauses should have a specific review date; if you can't name one, it's probably a kill.
What's the best tool to track multiple side projects in one place? The tool matters less than having a single source of truth. A spreadsheet, Notion, or a dashboard like carbonapps.com all work, as long as every project's status lives in one place instead of scattered across separate tools per project.
How do I manage side projects alongside a full-time job? The same systems apply, just with a smaller time budget for the active tier, often evenings or weekends only. The relay model matters more, not less, in this situation, since you have even less room to waste attention running several projects lightly instead of one with focus.
How do I avoid burnout when running several projects simultaneously? Schedule recovery time as seriously as work time, enforce a no-new-projects rule until something graduates out, and watch for the warning signs covered above, like dreading tools you used to enjoy or skipping your weekly review.
The five systems aren't complicated on their own: a ledger to see clearly, a relay to sequence effort, a rhythm to stay current, an autopilot to protect your attention, and a dashboard to keep it all visible. What's hard is the discipline to actually run one project at a time instead of five projects badly. Start with the audit this week, pick one project for the lead lane, and let the rest wait their turn.
More from the blog
How to Get Your First SaaS Customers: The First 10 Before You Scale Anything (2026)
Your first SaaS customers don't come from ads or SEO. They come from manual, unscalable outreach. A step-by-step playbook to land your first 10 paying users.
Self Hosted Supabase vs Managed: The Real Cost & Control Tradeoff (2026)
Self hosted Supabase vs managed, compared on real cost, ops burden, data control, and scaling. Learn the exact point where self-hosting actually wins.