The 80/20 Rule for Side Projects: When You Have a Day Job

The side-project trap: trying to do everything in 2 hours a night

Most side-project builders get the 80/20 rule wrong before they even start. They picture their evening as a single block of time, open their task list, and try to "find the key stuff" across everything at once: day job leftovers, side project tasks, personal errands, all in one pile. That's the single-distribution misread, which means they're slicing one pie instead of mapping two distributions against each other.

The result is predictable. You spend 90 minutes on day-job overflow because it feels urgent, 20 minutes on your side project because it doesn't, and 10 minutes on a personal task you forgot about. You're busy for 2 hours, and your side project barely moved. The 80% consumed your night, and the 20% got the leftovers.

Here's the correction. Your day job and your side project are not one list. They're two separate areas, each with its own 100% of tasks, each with its own distribution. If you try to prioritize across both at once, the urgent always wins, which means the day job always wins, which means your side project never gets the focus it needs. The fix is not more time. The fix is separating the areas and running a different lens inside each one.

The two-area approach: day job as one area, side project as another

The 80/20 rule works across contexts when you group your life into areas and prioritize within each, not across all of them at once. For the side-project juggler, that means two areas: Day Job and Side Project. Each gets its own task list, its own lens, its own 20%, and its own top 3. You prioritize your side project on its own terms, not as whatever's left after the day job eats your evening.

This is not a cosmetic separation. It's structural, which means it changes what you see. When day-job tasks and side-project tasks live in the same list, the day job dominates because its tasks come with deadlines, managers, and consequences that are visible this week. Your side project's tasks come with none of that. They matter because you decided they count, which is a quieter signal that loses every time it competes with a loud one.

When you separate them, each list gets its own frame. You can look at your side-project list and ask "what matters here?" without the day job shouting over it. In PRTO, this maps to the areas feature: you create a Day Job area and a Side Project area, each with its own task tree.

Different lenses for different areas: urgency for the day job, goals for the side project

Once you have two areas, the next move is declaring a different lens for each. This is the step most side-project builders skip, which is why their side project stalls even when they're spending 10 hours a week on it.

Day Job, urgency lens. Your day job is mostly urgency-driven. Your manager hands you tasks, some of which matter and some of which are fire drills. Your 20% under the urgency lens is the work that keeps your review intact and the people you answer to calm. If leaving a task undone creates visible pain this week, it's probably in the 20%.

Side Project, goal lens. Your side project is goal-driven. Nobody is asking for this work, which means it matters because you decided it counts. Your 20% under the goal lens is the work that compounds: shipping the feature that 80% of your users actually need, writing the one piece of content that brings in signups, strengthening the one relationship that opens a door.

Same person, two areas, two lenses, two distinct 20% sets. The lens isn't a detail. It's the input that determines what counts as "the few that matter" in each area, and a 20% found without a frame is just "anything that felt urgent," which puts your side project right back in last place. In PRTO, the goal/urgency lens toggle lets you switch frames inside each area, find the 20%, and drag those items into the top 20% column.

The intersection: work that serves both

Here's where the two-area approach becomes more than the sum of its parts. Once you've ranked your tasks under the urgency lens and under the goal lens, you have two 20% sets. The question most people never ask: where do they overlap?

The intersection is the work that's high-impact under both lenses at once. This is not the same as going deeper into one lens (that's the recursion, where you treat your 20% as a new 100% and zoom in: 20% to 4% to 0.8%, each level a smaller mirror of the last). The intersection is breadth, which means overlaying two lenses and finding the overlap. Anyone with a day job and a side project lives in tension: urgent at the office, what compounds on your own time. The intersection is the work that serves both, and it's rare. But when you find it, that's the work that matters most, because it moves what you owe now and your long-term goals at the same time.

Picture a developer whose day job involves building internal tooling, and whose side project is an indie app. A day-job task like shipping an internal demo is urgent this week. A side-project task like recording a screencast for users compounds over months. The skill underneath both is the same: recording a clear demo. When you rank everything under both lenses, both tasks land in the overlap. That's the intersection. In PRTO, select All Areas on the Focus page and switch to urgent and goal-aligned mode. The page shows you the overlap directly: items that are high-impact under both lenses, visible without hunting.

Protecting your side-project 20% when time is scarce

The side-project juggler's real constraint isn't motivation. It's time. You have 8 to 12 hours a week for your side hustle, if you're lucky, and the day job can eat into that without warning.

Pick your top 3, not your top 10. From your side-project 20% under the goal lens, pick the 3 items that matter most right now. Not 10, not 7: three. The constraint forces honest selection, because if all of it is a priority, nothing is. If you have 8 hours and 3 items, you'll go deep. If you have 8 hours and 10 items, you'll ship nothing.

Run the cascade when the list is long. If your side-project 20% still feels crowded, treat it as a new 100% and find the 20% within it. That's 4% of your original list, which drives roughly 64% of results. Zoom in again and you're at 0.8%, which drives 51%.^[3][4][5] Each level is a smaller mirror of the last.^[3] You can do this manually today: treat your 20% as a new list and rank within it. In PRTO, dedicated cascade levels are on the roadmap.

Protect deep work on the top 3. The 80% is loud. The 20% is quiet. Your side-project 20% has no deadline, no manager, no consequence this week, which means it loses to anything that does. Block the time, close the tabs, and work on the top 3 first. If you have 2 hours, spend the first 90 minutes on your top 3, then 30 on anything else. Not the reverse.

The weekly review for side-project builders

Your 20% changes. Projects move, new work arrives, and the lens that fit last week might not fit this one. If you set your 20% once and never revisit it, you'll keep protecting tasks that stopped being high-leverage. A short weekly review keeps the selection honest. Here's the loop, which takes 20 to 30 minutes:

1. Re-capture. Dump anything new into the right area. Don't sort yet.
2. Re-declare your lenses. Day Job stays urgency. Side Project stays goals.
3. Re-mark the 20%. Look at each area through its lens. Cut what stopped compounding. Add what became high-leverage.
4. Re-pick your top 3. From the updated 20% in each area, pick the 3 that matter most this week.
5. Check the intersection. Rank everything under both lenses and look at the overlap. Is there anything high-impact under both now? If yes, that's your first move next week.

If you run this loop weekly, your side project gets the focus it needs, your day job gets the urgency coverage it demands, and the intersection gets found before it slips away. You're not adding hours. You're pointing the lens at the right work.