Planning a Side Project Around a 9-to-5

The Side Project Time Trap

You finish work at six. You eat something. An hour passes. By the time you sit down at your laptop, it's half eight and you've got maybe ninety minutes before tomorrow's alarm feels too close.

That's the reality of planning a side project around a full-time job. Not the startup-myth version with late-night breakthroughs and a pizza box on the desk. The real version, where your available hours are fragmented, your mental energy is already spent, and "I'll work on it this weekend" has become the lie you tell yourself every Sunday.

I built Weekloom while working a day job. At some point I stopped treating my side-project hours as leftover time and started treating them as scheduled time. That shift changed what I could actually ship.

This isn't about squeezing more hours out of a full day. You probably can't. It's about making the hours you already have count.

Why Availability Isn't the Problem

Most people with a day job have somewhere between 8 and 14 hours a week that aren't claimed by work, sleep, or essential life admin. Research from the Bureau of Labor Statistics consistently shows the average employed adult has around 5 hours of leisure time per day, most of it in the evening.

The problem isn't availability. Plenty of time exists. The problem is that unscheduled discretionary time gets filled by whatever feels easiest in the moment. Scrolling, TV, general decompression. None of it is bad. All of it is rational when you're mentally depleted. But it quietly devours the hours you intended to spend building something.

Two things make side-project time vanish faster than any other kind.

First: no external accountability. No standup, no deadline from a boss, no one waiting on your output. You could skip tonight and nothing would break, at least not immediately.

Second: tasks that are completely underspecified. "Work on the app" is not a task. It's an invitation to spend 40 minutes deciding where to start and then give up.

Both problems are solvable. Neither requires more hours.

Planning a Side Project in Weekly Blocks

The only planning system that's worked for me on nights-and-weekends work is a weekly one. Not daily. Not a running backlog. Weekly.

Here's why. Daily planning assumes you'll have a consistent check-in ritual every morning before you start. That works for a day job. For a side project, the days vary too much. Some nights you have an hour and a half, some you have twenty minutes, some you're too tired to think. Daily planning creates overhead that the project can't justify.

A running backlog sounds appealing but tends to go stale fast. You add tasks, you stop looking at them, and the backlog becomes an anxiety object rather than a planning tool.

Weekly planning threads the needle. Once at the start of the week, on Sunday evening or Monday morning, you decide what this specific week will look like for the project. Not what you'd like to do someday. What you're committing to doing before next Sunday.

This matters because it forces a constraint. You have to look at your week, see what evenings are actually available, and size the work to fit. It's the difference between "I want to finish the landing page" and "I'm going to write the hero copy on Tuesday and get the layout done Thursday."

For the task-level work, breaking each goal into small, checkable steps is what makes those Tuesday and Thursday sessions actually start quickly. When you sit down after dinner with ninety minutes, the last thing you want is to spend thirty of them figuring out what you're doing. If the step is already written, "draft the headline and three subheadings," you can open the doc and go.

Weekloom's Gantt board makes this visible in a way that a doc or a Notion page doesn't. Your side project is a row. The week stretches across as columns. Each day has a small set of steps you can check off. At a glance, you can see whether Tuesday is realistic or whether you've stacked too much on a night you know is already tight. That visual weekly view of your tasks prevents the classic overcommit that kills momentum.

Protecting the Hours You Actually Have

Scheduling weekly side-project time isn't enough if you don't defend it.

The specific threat varies by person. For some it's social commitments that get added to weeknights without anyone checking the calendar. For others it's the day job bleeding past its official end: one more email, one more Slack message, fifteen minutes that turns into an hour. For others still, it's the exhaustion that makes Netflix a more appealing option than opening a code editor.

Pick your two best slots and protect them like meetings. For most people with an office job, Tuesday and Thursday evenings are the most reliably unclaimed. Monday is still in work mode. Wednesday is midweek chaos. Friday you're done. Saturday and Sunday mornings, before the day's plans fill in, are worth considering too. Identify your two best slots and put them in your calendar as non-negotiable.

Keep the work session short enough to be sustainable. Ninety minutes is better than three hours. Three hours of side-project work on a weeknight is optimistic for most people and often results in a late bedtime, a rough Wednesday, and an abandoned Thursday session. Timeboxing your work to a fixed window, even one that feels too short, maintains consistency better than trying to grind.

End each session by writing tomorrow's first step. Not a summary. Just one line: what you'll do first when you next sit down. Your future self, sitting down at 8pm after a long day, needs to see a concrete entry point, not an open-ended question. That one habit does more for keeping a project moving than most productivity techniques I've tried.

The Compound Math of Small Sessions

Six ninety-minute sessions a week sounds underwhelming. That's nine hours. Nine hours a week on a side project, sustained over a quarter, is 117 hours of actual work. Over a year it's north of 450 hours.

Paul Graham has noted that many successful companies were built on evenings and weekends before their founders left their day jobs. The hours add up, but only if the sessions are productive rather than spent deciding what to do.

The failure mode isn't laziness. Most side-project people are motivated enough. The failure mode is unplanned sessions: sitting down without a clear task, circling for a while, feeling frustrated, closing the laptop. Do that a few times in a row and the project starts to feel stuck even though you've nominally been "working on it."

Planning the week in advance converts those sessions from open-ended to goal-shaped. You know what you're doing before you sit down. The ninety minutes goes toward the work instead of toward figuring out the work.

This compounds in another way. When you finish a session having completed something concrete, a specific feature, a specific piece of copy, a bug fixed, the project feels alive. That feeling is what brings you back Thursday. When sessions end in vague progress or no progress, the project quietly dies while still technically on your to-do list.

If the project has any risk of going stale between sessions, keeping a weekly planning routine tied explicitly to it helps. Five minutes on Sunday to reset the week's side-project tasks takes almost no time and does more for your output than most single-session grinding sessions ever will.

When the Week Falls Apart

At some point a week will collapse. A work deadline, an illness, a family thing. You miss both sessions. The project sits untouched for seven days.

This is where most side projects quietly die. The gap creates distance, the distance creates friction, and suddenly it's been three weeks and the project feels like something that "was" happening rather than something that is.

The move is not to recover all the lost work. You can't. The move is to do one small thing, the smallest concrete item on the list, to re-establish that the project is still alive. A single step completed keeps the thread intact. Doesn't matter if it's fifteen minutes. It matters that it happened.

Then, at the next weekly planning session, you size the week fresh. Don't try to catch up on last week. Just plan this week on its own terms, using the time you actually have.

Building in a weekly review habit helps here too. Even a quick ten-minute retrospective on what you did (or didn't do) keeps you honest about the project's real pace. Side projects that skip this tend to carry an inflated sense of progress that collapses at launch when the actual task list is still long.

Try Weekloom if you want a visual, low-overhead way to plan your side-project weeks. The board layout makes it obvious when you've overloaded a Tuesday evening or left a whole Thursday blank. That clarity, by itself, changes what you commit to.