How to Stay Motivated to Finish a Side Project
Most side projects don't die from a lack of ability or a lack of a good idea. They die in the unglamorous middle — past the exciting start, before any visible finish — where the initial burst of enthusiasm has worn off and nothing external is forcing you to keep going. Nobody's waiting on the album, the app, the zine, or the workbench project. That's exactly what makes it a side project, and it's exactly why it's harder to finish than anything with a boss or a client attached.
Motivation research has a lot to say about why this middle stretch is where projects go to die, and more usefully, what actually gets people through it. None of it is about willpower.
Understand why the middle is the hard part
Psychologists Edward Deci and Richard Ryan's self-determination theory identifies three things that sustain motivation on anything you're not forced to do: autonomy (it feels like your choice), competence (you can see yourself getting better at it), and relatedness (someone else is aware of or involved in it). A side project usually starts with all three firing at once — you chose it, you're learning fast because everything is new, and you've told a few people about it. By the middle stretch, the novelty-driven sense of competence flattens out (progress slows, the easy wins are gone), and relatedness quietly disappears too, because you've stopped mentioning it. Autonomy is often the only leg still standing, and autonomy alone isn't enough to carry a project through a long plateau.
Knowing this reframes the problem usefully: the goal isn't to manufacture more willpower. It's to deliberately rebuild the competence and relatedness legs that naturally eroded.
Shrink the project until it's finishable
The single biggest motivation-killer in a side project is scope that quietly grew past what you can realistically finish in the time you actually have — not the time you wish you had. A project sized for a fantasy version of your schedule guarantees the "I'm behind" feeling that kills motivation faster than almost anything else.
The fix is blunt: cut scope until the smallest complete version is realistically finishable in the next two to four weeks at your real, current pace. A four-track EP instead of a twelve-track album. A working single feature instead of the full app. One finished piece instead of a whole series. This isn't giving up on the bigger vision — it's making sure you finish something, because a finished small thing generates the competence and momentum to attempt the bigger thing next, while an abandoned big thing generates neither.
Use a implementation intention, not a general goal
Psychologist Peter Gollwitzer's research on implementation intentions found a specific, reliable gap between people who set a general goal ("work on the project regularly") and people who set an if-then plan ("if it's Tuesday evening after dinner, I work on the project for 30 minutes at the kitchen table") — the if-then group followed through significantly more often. A general intention leaves the actual moment of starting up for negotiation every single time, and that negotiation is where motivation quietly loses.
Pick the specific trigger — a day, a time, a location, a preceding action — and write it down as a single if-then sentence. Vague plans compete with everything else in your week. Specific ones don't need to compete; they just need to fire.
Rebuild relatedness on purpose
Because a side project usually has no built-in audience, the "someone else is aware of this" leg of motivation has to be manufactured deliberately, not left to happen naturally. This doesn't require a public launch or a following — it requires one or two people who know the project exists and will occasionally ask about it. Tell a friend the specific next milestone, not just "I'm working on a project." Post a rough, unpolished update somewhere, even to a tiny audience. Work alongside someone else, in person or over a video call, even on unrelated projects — the "body doubling" effect, well documented in ADHD research but useful for almost anyone, comes from simply having another person present while you work, which makes starting easier even without any direct collaboration.
The specific mechanism matters less than the effect: someone else's awareness turns your project from a private thought you can quietly abandon into a small, real commitment.
Bundle the project with something you already enjoy
Behavioral scientist Katy Milkman's research on "temptation bundling" found that pairing a should-do activity with a want-to-do one measurably increases follow-through — her original study paired an audiobook people were eager to hear with time on a gym treadmill, restricted to treadmill time only. The same move works for a side project: reserve a favorite snack, a specific playlist, or a favorite coffee shop exclusively for project time, so the activity picks up some of the pull of the thing it's bundled with.
Make progress visible, even in small increments
Harvard researcher Teresa Amabile's work, published as The Progress Principle, analyzed thousands of daily work diaries and found that the single strongest predictor of a good, motivated day wasn't recognition, pay, or pressure — it was making visible progress on meaningful work, even a small step. The inverse held too: setbacks disproportionately hurt motivation, more than equivalent gains helped it, which means a project where progress is invisible tends to feel like a slow accumulation of setbacks even when it's actually inching forward.
A side project is especially vulnerable to invisible progress, because there's no manager tracking it and no dashboard showing movement. The fix is to make progress visible to yourself on purpose: a simple checklist of small milestones, a running log of what changed after each session, even a physical chain of X's on a calendar for days you touched the project. None of this needs to be sophisticated. It needs to exist somewhere you'll actually see it, so that a genuinely productive Tuesday registers as one, instead of dissolving into the general sense that "I haven't made real progress in weeks" that kills more side projects than any single setback does.
Protect the project from Parkinson's Law
Left with an open-ended deadline, a side project will expand to consume all the time you don't allocate it, because there's no natural boundary pushing back. The fix isn't a harsh deadline imposed from nowhere — it's a real one with a real consequence attached, even a small, self-imposed one: tell a friend you'll show them a finished draft by a specific date, book a slot at an open mic, submit to a low-stakes call for entries with an actual deadline. An external date, even a manufactured one, does something an internal "someday" target can't.
Let the finished version be smaller than the imagined one
A large share of side projects that stall out aren't stalled — they're finished in every way except the creator's willingness to call them done, because the finished version doesn't match the version imagined at the start. That gap is normal, not a sign of failure. Nearly every real, finished creative or technical project falls short of its initial imagined version in some way; the difference between people who finish and people who don't is mostly whether they're willing to ship the real version instead of holding out for the imagined one.
Start here
Write one if-then sentence right now for your side project: the specific day, time, and place you'll next work on it, and for how long. Then tell one person — a text message is enough — what you're planning to have done by then. That single sentence and that single message rebuild two of the three legs motivation actually runs on, and they take less than five minutes today.