Back to blog
Guide

Side Project After Work: How to Keep It Moving When Your Job Takes Your Best Hours

🧭
The Lovestack team
7 min read

You get home at 6:40. The project you actually care about is sitting on your laptop, three tabs deep, exactly where you left it eleven days ago. You know what it needs. You also know you have roughly the cognitive capacity of a houseplant right now. So you tell yourself you'll give it a proper run on Saturday, and you open something else instead.

That loop is the whole problem. Not motivation, not the project, not the tooling. The unit of progress you're waiting for — a long, clear-headed block — is a unit your week doesn't produce. So the work has to be cut into pieces small enough to survive your real evenings.

The free weekend is not coming

Be honest about the last two weekends. Something came up: errands, family, a flat tire, or you were simply flattened and slept until eleven. If your project only moves in four-hour blocks, and four-hour blocks happen twice a quarter, your project moves twice a quarter. That's the arithmetic, and no amount of discipline changes it.

Your employer has first claim on your sharpest hours, and that's a real constraint rather than a personal failing. The hours that are genuinely yours are shorter, later, and lower-wattage. Planning around them is a separate skill — we go deeper on it in planning the hours that are actually yours.

So stop budgeting time you don't have, and start sizing work to the time you do.

Make the unit one dated next step

A project list is a wish. A next step is an instruction. The difference is four things: a verb, one object, a date, and a size you can finish with half a brain.

Compare:

  • "Work on the landing page" → Tue: paste the three headline options into the hero, delete two, keep one.
  • "Set up email" → Wed: create the account and send one test email to myself.
  • "Fix onboarding" → Thu: screen-record myself signing up, save the file, don't watch it yet.
  • "Talk to users" → Mon: send the message I already drafted to the two people in my notes.

The right-hand versions are boring, and that's the point. Boring is what you can do at 9:40 p.m. without negotiating with yourself first. Long, vague lists do the opposite — they make you re-decide everything every time you look, which is exactly why long to-do lists backfire.

The tired test

Before a step goes on a date, run it through three questions:

  1. Do I have to decide anything? If yes, it isn't a doing step — it's a deciding step, and it belongs in a different slot.
  2. Do I have to find anything? Hunting for a file, a password, or a link is where tired sessions die. Put the path or the link in the step itself.
  3. Can I finish it in about twenty minutes? If not, split it until you can.

Anything that fails the test gets rewritten, not deleted. "Redesign the pricing page" fails all three. "Write down the three prices I'm choosing between" passes.

Separate deciding from doing

This is the move that makes the rest work. Deciding is expensive and needs your good brain. Doing is cheap and doesn't.

Take one short session a week — thirty to forty minutes, whenever your head is clearest, Saturday morning for a lot of people — and spend it entirely on decisions and dates. You're not building anything. You're producing four or five dated doing-steps for the week ahead. If that weekly slot sounds familiar, it's the same muscle as a weekly review, aimed at one project.

Then every weeknight step is pre-decided. You open the project, read one line, do it, close it. No thinking required, because the thinking already happened on Saturday with coffee.

A menu for 9 p.m.

Some nights even a twenty-minute step is too much. Keep a short list of things that still count, so a bad night produces something instead of nothing:

  • Write tomorrow's step, in detail, and stop.
  • Record a two-minute voice note about what's bugging you in the project.
  • Send one message you've been avoiding.
  • Take the screenshot, rename the file, commit the thing you already finished.
  • Delete one feature, page, or idea you're never going to build.
  • Read your own notes from last week.
  • Open the project for sixty seconds and close it, so tomorrow isn't a cold start.

And one more, which is a real option: mark tonight as off and go to bed. A deliberate skip doesn't break anything. An unmarked skip turns into guilt, and guilt is what keeps the laptop closed for the next eleven days.

Park it mid-sentence

The most expensive minutes in a short session are the first five, where you try to remember what you were doing. So end every session by writing the next line, not by cleaning up.

Leave a single note at the top of whatever you were in — the file, the doc, the page — that says: next: … Make it an instruction to a stranger. "next: the submit button posts but the success message doesn't show — check the handler around line 40." Future you, tired, can act on that. Future you cannot act on "continue form."

The same principle applies to the ideas that hit you at work, in the car, in the shower. They need one place to land, not five, or they evaporate — that's the single capture inbox habit, pointed at your project.

Protect one hour, not five

When people finally get serious, they block out Saturday 9–2. It gets eaten, they feel defeated, and the block never gets rebooked.

Book one hour instead. Same slot, every week, dated like a dentist appointment. One hour you will actually defend beats five you'll surrender. If the slot gets taken, move it inside the same weekend rather than writing the week off — and if you consistently run past your own blocks, plan the overrun in rather than pretending it won't happen.

If that hour at home is where your focus falls apart — people, notifications, the laundry — a daily plan that protects focus hours at home is worth more than another productivity app. Working quietly alongside someone else, even a stranger on a video call, also helps more than it sounds like it should: see running a focus session without a partner.

Measure touches, not hours

Hours logged is a demoralizing metric for someone with a full-time job, because the number will always look small. Count touches instead.

Define a touch as a dated step, done, however small. Then track one number per week: how many touches. Three is a good week. One is a real week. Zero, twice in a row, is a signal that the steps are too big, not that you're lazy.

This matters because the thing that kills side projects is rarely the start. It's week two, when the novelty is gone and the system you set up on Sunday needs maintaining — the keeping problem that quietly ends most setups.

When you lose two weeks

You will. A work crunch, a trip, a sick kid, and suddenly it's been three weeks and the project feels like someone else's.

The re-entry rule: do not re-plan. Re-planning feels productive, costs an entire evening, and at the end of it you've shipped nothing and you're more tired. Instead, open the project, read your "next:" note, and do that one thing even if it's now slightly wrong. Movement first, planning after. The same logic applies to any streak you've broken — restarting after missing a week is about lowering the bar for one session, not rebuilding the system.

If you genuinely can't tell what the project needs anymore, give yourself one deciding session with a hard stop, produce three dated steps, and close it. That's a repair, not a reboot.

What a month of this actually looks like

Twelve to twenty small steps and maybe four protected hours. It does not feel like heroic progress on any single night. What it produces over a month, though, is a landing page that exists, an email that sends, two conversations with real people, and four features you decided not to build.

Compare that to the alternative you've been running: one good Saturday, a lot of tabs, and the same "next: continue form" note you wrote in September. The small version wins because it's the one your calendar will actually allow — and when a genuinely open weekend does show up, you'll spend it building on something that already moves instead of remembering where you were. If everything on your plate feels equally on fire and the project keeps losing, that's a triage problem first: how to plan your week when everything feels urgent.