Business & Entrepreneurship

How to Pick a Side Project That Won't Die in Two Weeks

February 7, 2026

Pick a side project with a real problem, small scope, existing skills, and a visible finish line. Excitement is not enough.

A workflow diagram and product brief sketched on paper on a wooden desk
Photo by Kelly Sikkema / Unsplash

Most side projects do not die because you are weak.

They die because you picked a project that needed a team, a runway, a distribution plan, and a therapist.

Then you tried to build it on Tuesday nights.

Brave.

Bad math.

The right side project is not the most exciting idea.

It is the idea with enough pull, small enough scope, and a finish line you can actually reach.

Excitement is not a plan

Excitement is useful at the start.

It gets you to open the file.

It does not carry you through week four when the easy parts are done and the work becomes ordinary.

So stop asking:

Am I excited about this?

Ask:

Will I still do this when it gets boring?

Different question.

Much better.

If the answer is no, the project is not bad. It is just not a good side project right now.

Use the four-filter test

Before you start, run the idea through four filters.

1. Real problem

What problem does this solve?

For whom?

How often does it hurt?

If you cannot answer in one sentence, you do not have a project yet.

You have a mood.

Examples:

  • freelancers need a faster way to estimate project scope
  • writers need a cleaner way to store rough ideas
  • local businesses need simpler landing pages
  • beginners need a no-nonsense budgeting template

Specific beats impressive.

2. Small finish line

Can you finish version one in 4 to 8 weeks?

Not if you quit sleep.

Not if every weekend becomes a workday.

Realistically.

If not, cut the scope.

Then cut it again.

The first version should feel almost too small.

Good.

That is how it gets finished.

3. Existing skills

A side project can teach you something.

It should not require you to learn everything.

Use the 80/20 rule:

  • 80% skills you already have
  • 20% skills you are stretching

If the project requires a new coding language, new design skill, new marketing channel, new audience, new product model, and new discipline system, congratulations.

You built a quitting machine.

Pick something closer to your current strengths.

4. Distribution path

Who will see it?

Where will you share it?

Who needs it enough to care?

Most side projects are built in private and then released into silence.

Do not do that.

Before you start, write:

  • I will share this with [specific group]
  • I will ask feedback from [specific people]
  • I will publish updates on [specific channel]
  • I will know it worked if [specific signal]

Distribution is not a marketing department problem.

It is part of the project.

Pick the smallest useful version

Do not build the full dream.

Build the proof.

Full dream:

  • account system
  • dashboard
  • integrations
  • mobile app
  • templates
  • analytics
  • paid plan

Small proof:

  • one page
  • one workflow
  • one template
  • one useful result

The small proof answers the real question:

Does anyone care enough to use this?

If yes, build more.

If no, you saved months.

That is not failure. That is tuition paid in a cheaper currency.

Make the project boring enough to finish

This sounds insulting.

It is useful.

A side project should have boring parts.

Clear parts.

Repeatable parts.

If every step requires invention, you will run out of steam.

You want a project where the next action is obvious most days.

Examples:

  • write one lesson
  • build one page
  • record one demo
  • test one workflow
  • ask three people for feedback
  • publish one update

If your project has no obvious next actions, it is still too vague.

The side project scorecard

Score your idea from 1 to 5:

  • real problem
  • 4 to 8 week finish line
  • uses existing skills
  • clear distribution path
  • small useful version
  • obvious next actions

Total possible: 30.

If it scores under 22, do not start.

Fix the idea first.

This is how you avoid becoming the person with eight half-built things and one dramatic explanation for each.

Your move

Write down three side project ideas.

Run the scorecard.

Pick the one that scores highest, not the one that sounds best in conversation.

Then build the smallest useful version.

If side projects keep collapsing for you, read why side projects die. If you need a fast starting container, launching a side project in a weekend will help.

But choose first.

No more starting from vibes.