business-entrepreneurship
How to Pick a Side Project That Won't Die in Two Weeks
February 7, 2026
Most side projects die because you picked wrong from the start. Here's how to pick one you'll actually finish.
You’ve got the itch again. Another idea. This time, you think, will be different. You’re going to see it through.
Two weeks later, it’s gathering dust.
Here’s what nobody tells you: it’s not about your commitment. It’s not about your discipline. It’s about picking the wrong project in the first place. You’re starting from a hole, and no amount of willpower climbs you out.
The problem is that we pick side projects the way we pick fast food—based on whatever we’re craving right now. It feels exciting, so we assume that means it’s right. But excitement fades. What remains? Boredom, scope creep, and the feeling that you’re a quitter.
You’re not a quitter. You just picked badly.
Kill the “Follow Your Passion” Myth First
Everyone says it: “Follow your passion and you’ll never quit.”
That’s nonsense. You know what kills side projects faster than anything? Passion without constraints. Passion makes you ambitious. Ambition makes you scope creep. Scope creep makes you quit.
Passion is also unreliable. It surges and crashes. If your entire project depends on a feeling, you’re building on sand.
What actually makes you finish? Three things working together: something small enough to finish, something interesting enough to sustain, and something useful enough to matter. Not one. All three.
If you optimize for just passion, you’ll pick something big and vague that sounds cool in conversation. If you optimize for just speed (the “just ship it” crowd), you’ll build something shallow that doesn’t feel worth your time. If you optimize for just utility, you’ll grind on something joyless.
You need the intersection.
The Three-Axis Test
Before you commit a single hour, run your project idea through this:
Axis 1: Can you finish it in 4-12 weeks? Not the “if I work 20 hours a week” fantasy. Real honest time. If the answer is no, cut scope until it is. The goal isn’t to change the world with one project—it’s to complete something, own it, and move forward. Finishing trains you. Half-finished teaches you nothing except that you quit.
Axis 2: Does it hit a real problem for someone (including you)? Not “It would be cool to have this.” Real problem. Something that bugs you enough that you’d use it yourself, or something someone’s already paying for. If you can’t articulate the problem in one sentence, you don’t understand it yet. Go back to the drawing board.
Axis 3: Does it use skills you have? This is where most people get it wrong. They think a side project is where you learn everything new. No. A side project is where you ship. Learning new skills is fine as a bonus, but if the project depends on you mastering something unfamiliar while also building the whole thing, you’re adding friction you don’t need. Pick something that lives 80% in your wheelhouse.
If it fails any axis, it’s not a side project—it’s a long-term commitment disguised as a side project. Neither is bad, but you need to know which one you’re starting.
The Constraint Filter
Here’s the tough part: make the project smaller.
Not by a little. By a lot. By an amount that feels risky.
What’s the absolute minimum version? Not the “version 1 with basic features.” The MVP that might be too minimal, the one that makes you nervous because it feels incomplete. That’s your target.
Completeness isn’t about features. It’s about shipping something that works and solves the core problem. Everything else is polish, and polish kills side projects.
Example: You want to build a productivity app. The full version has auth, cloud sync, team sharing, mobile app, and an algorithm that learns your patterns. That’s a startup, not a side project.
The minimal version? A single-user, no-login web app that solves one specific workflow. Finished in 8 weeks. Launched. You can always build more, but the magic is in shipping first.
One More Filter: Can You Explain It in a Sentence?
If you can’t describe your project in one clear sentence, it’s too complicated. This isn’t about marketing—it’s about clarity. If you’re confused, you’ll get lost in the build.
“A tool for X users to do Y” should be all it takes.
If you’re hedging or adding caveats, you don’t have a clear enough vision yet. Sit with it longer. The best ideas are simple because they’re focused.
Pick, Then Commit to Not Quitting
Once you’ve run it through the three-axis test and the constraint filter, you’ve picked right. Now the commitment piece is real, because you’ve set yourself up to win.
You’re not fighting through the slog of a 18-month vision. You’re executing a 12-week plan. You’re using skills you already have. You’re solving a real problem. The finish line is visible.
That’s what makes you ship.
The side projects that matter aren’t the ambitious ones. They’re the focused ones. The ones where someone looked at the chaos of “what should I build?” and said, “Not that. This smaller thing, right here.”
That’s the decision that wins.
Your move: Write down three ideas you’re considering. Run each through the three axes. Which one survives intact? That’s your project. Not the one that sounds coolest. The one that fits.
Want to dig deeper into why projects die in the first place? Check out why side projects die. And if you’re wrestling with the startup mindset around side work, read about the quiet power of doing less—it reframes what “winning” actually means.
Ship the small thing. That’s the entire game.