TRACK 01Basecamp · Lesson 8 of 13

Shiny object syndrome: how to stop starting over every month

Why beginners keep jumping to new ideas, and a few plain rules to help you finish one thing before you start the next.

You start a project. Two weeks in, it gets boring or hard. Then you see a video about a different way to earn online, and it looks so much easier, so you drop the first thing and start the new one. A month later, you do it again.

That loop has a name: shiny object syndrome. It means chasing every new idea that catches your eye, so you never stay with one long enough to see if it works.

By the end of this lesson, you'll know why it happens, how to spot it in yourself, and how to set a few simple rules that keep you on one track. None of it takes willpower you don't have.

The short version

  • New ideas feel exciting because you haven't hit the hard part yet. Your current project has.
  • Write new ideas down in a "parking lot" list instead of acting on them right away.
  • Commit to one project for a set stretch of time, and only decide to switch at a planned checkpoint.

Why the new thing always looks better

Every project has a fun start, a long boring middle and a hard finish. The start is all ideas and plans. The middle is doing the same small tasks over and over while not much happens.

When you're in the middle of your project, you're comparing it to the start of a new one. That's not a fair fight. Of course the new one looks better. You haven't found its problems yet.

The internet makes this worse. There's always someone with a new method, a new platform or a new tool, and they make it look smooth. You see their highlight reel, not their boring middle.

The new idea isn't better. It's just newer, and you haven't hit its hard part yet.

How to tell if you have it

Be honest with yourself. A few signs:

  • You have three or more half-built projects sitting in folders.
  • You've bought courses or tools for ideas you never started.
  • You switch ideas right after a hard week, not after looking at real results.
  • You spend more time reading about new methods than working on your current one.
  • You can't name what you'd count as "done" for the project you're on.

If two or more of those fit, you're not broken. This is one of the most common things beginners run into. It's fixable with a few rules.

Rule 1: Start an idea parking lot

You can't stop new ideas from showing up. Your brain will keep making them, and that's fine. The trick is to stop acting on them the moment they arrive.

Make a list somewhere easy. A notebook page, a note on your phone, a single doc. Call it the parking lot. When a shiny idea shows up, write it down in one or two lines and close the list.

That's it. The idea is safe. You haven't lost it. You've just parked it, so you can get back to the thing you're actually building.

Rule 2: Pick a commitment window

A commitment window is a stretch of time where you promise yourself you won't switch projects, no matter how bored you get. Pick a length that's long enough to actually learn something. For most beginner projects, that means a few months, not a few weeks.

Write down the start date and the end date. Put the end date on your calendar. That date is your checkpoint, the one moment where you're allowed to decide whether to keep going, change course or stop.

Before the checkpoint, the answer to "should I switch?" is no. You don't have to think about it. That's the point. The lesson on reading your results honestly covers how to make that checkpoint decision when you get there.

Rule 3: Define "done" for this round

Shiny object syndrome loves a project with no finish line. If you never decided what "done" looks like, you'll never feel done, and quitting will always feel reasonable.

So write one sentence: "This round is done when..." Keep it small and something you control. For example:

  • "This round is done when my checklist product is finished and listed for sale."
  • "This round is done when I've published eight posts."
  • "This round is done when I've offered my service to ten people who fit."

Notice that none of those say "when it makes money." You can't control that part. You can control finishing.

Rule 4: Put the hard part on a schedule

People usually jump ship when they hit a task they don't like. Writing the sales page, asking people for feedback, learning the boring tool. The shiny new idea feels like an escape hatch.

Instead, name the hard task and give it a time slot. "Saturday, 9 to 10, I write the first draft of the sales page." It doesn't have to be good. It just has to happen.

Hard tasks shrink once you start them. The dread is usually bigger than the work.

When you feel the urge to switch

When the itch hits, run through three quick questions before you do anything:

  1. Am I switching because of real results, or because this week was hard?
  2. Is my checkpoint date here yet?
  3. Have I written this new idea in the parking lot?

If the answers are "it was hard," "no" and "now I have," then close the tab and go back to work. The new idea will keep just fine in the parking lot.

When switching is the right call

Sometimes you really should change direction. Rules aren't meant to trap you in a dead end forever.

Good reasons to switch, at your checkpoint, include clear signs nobody wants the thing after a fair test, a big change in your life or schedule, or finding out you truly hate the work, not just the boring parts. Those are real reasons. "This new thing looks easier" is not.

When you do switch, finish or close out the old project properly. Write a short note about what you learned and what you'd do differently. That way the time wasn't wasted. It turned into experience you carry into the next one.

Do this next

The grass is greener over there because nobody's mowed it yet. Mow your own.

This is general information to help you learn, not legal, tax or financial advice. Every situation is different, and nobody can promise results, including me. If money or the law is involved, check your state's rules or talk to a qualified professional.
Sean "SAMX"

Veteran. Gen Xer. Thirty-plus years building things on the web. I write these so you can skip some of the expensive mistakes.

Build with me