Why Good Ideas Are Killing Your Startup
Good ideas kill startups because you can only finish one at a time, and every new idea you chase quietly steals hours from the one that was actually working. The skill that separates people who ship from people who just brainstorm isn’t having ideas. It’s saying no to good ones on purpose so you can carry a single thing all the way to done.
You’re not failing to launch because you’re out of ideas. You’re failing because you have too many, and each one feels just exciting enough to abandon the last. That itch has a name.
What is shiny object syndrome?
Shiny object syndrome is the habit of dropping the project you’re on the second a newer, shinier idea shows up. It feels like ambition. It’s actually how you never finish anything.
Here’s what it looks like. You spend three weeks building a study-planner app for your school. It’s almost usable. Then a friend mentions nobody can find good used textbooks, and suddenly that feels like the real opportunity. You open a new Notion doc, sketch a marketplace, and the study planner dies at 80% done. Two weeks later, a TikTok about AI note-taking makes the marketplace feel boring, and you pivot again.
Notice the pattern. Every new idea arrives at its most attractive moment: pure possibility, zero grind. Every old idea sits at its ugliest, when the fun part is over and the boring 20% is all that’s left. Your brain compares “shiny new thing” against “annoying almost-done thing” and picks shiny every time. That comparison is rigged. The new idea only looks better because you haven’t hit its boring part yet.
Why do good ideas do more damage than bad ones?
Bad ideas are easy to reject. You look at them, feel nothing, and move on. Good ideas are dangerous precisely because they’re good. They’re plausible, you can picture them working, and that’s what pulls your attention off the thing in front of you. A founder with ten bad ideas finishes one project because nine get dismissed instantly. A founder with ten good ideas often finishes zero, because each is tempting enough to justify a switch. More good ideas can mean less output.
Switching is also expensive. Every time you jump projects, you throw away the momentum, the half-built landing page, the customer conversations, and the context in your head. Starting is the most expensive phase of any project, and shiny object syndrome makes you pay that cost over and over without collecting the payoff. So next time an idea grabs you, ask: is this genuinely better, or just newer? Newness is not a signal. It’s a trap.
The one-project rule
The discipline is simple to state and hard to follow: run exactly one company at a time, and don’t start a second until the first has reached a real finish line.
A “finish line” doesn’t mean a huge exit. For a high schooler with no funding and a part-time schedule, it’s something concrete and provable, like:
- A live landing page that actually converts visitors into signups.
- Ten paying customers, or ten clear nos so you know the idea’s dead.
- A real launch, not just a build. Shipping isn’t the same as actually launching.
- A demo you can present start to finish without it breaking.
The rule works because it forces the boring 20% to happen. Most of the value in a startup lives in the part you skip: the polish, the outreach, the launch. New ideas let you feel productive while permanently avoiding it. One project carried to a finish line teaches you more than five abandoned at the fun stage combined.
An idea parking lot: capture without chasing
You don’t have to pretend the new ideas aren’t good. The trick is to separate capturing an idea from acting on it.
Keep an idea parking lot: one note on your phone where every new idea goes the instant it shows up. Give it two sentences, then close the note and get back to work. You’ve told your brain “I heard you, I logged it,” which is usually all the itch wanted.
Then, once a month, review the parking lot on purpose. Here’s a way to score what’s in there so you compare ideas fairly instead of by whichever is loudest today:
| Question | Weak idea | Strong idea |
|---|---|---|
| Still exciting a month later? | You forgot you wrote it down | You keep thinking about it unprompted |
| Who has this problem? | ”People in general” | A specific group you can reach |
| Can you test it cheaply this week? | Needs money or a team you lack | You can test it before building with a landing page and DMs |
| Would you drop your current project for it? | Not really, it just felt fun | Honestly yes, and you can say why |
The magic of the parking lot is that most “amazing” ideas quietly fail the one-month test. The excitement was real, and temporary. By the time you review, you already know which were fireworks and which were signal.
How to decide when switching is actually the right call
Focus is the default, but it’s not a religion. Sometimes the honest move is to switch. The skill is telling shiny-object switching apart from a real pivot.
Switching is avoidance when you’re jumping right as the boring part begins, the new idea feels better mostly because it’s new, or this is your third switch this month. Switching is a real decision when you tested the idea and got honest signals it won’t work, you’ve hit your finish line, or the problem turned out too small to matter. If people keep saying they love it but never buy, learn why friends loving it isn’t validation.
Here’s a clean process to run before you allow yourself to jump:
- Write down why you’re really switching. Be honest about whether it’s evidence or boredom.
- Check where you are on the current project. If you’re near the finish line, the answer is almost always “finish first, then reconsider.”
- Put the new idea in the parking lot instead of starting it. If it’s real, it’ll survive two weeks of waiting.
- Set a kill-or-continue date for the current one. Give it a real deadline to prove itself instead of drifting away.
- Only switch if the new idea is still winning after all four steps. Most of the time, it won’t be.
This is the same muscle behind knowing when to quit versus push through. Quitting on evidence is smart. Quitting on a whim is shiny object syndrome in disguise.
What this looks like when you’re 16 with no money and a full class schedule
The constraints you complain about are your advantage here. Limited hours, no budget, school eating most of your week: you literally cannot run three projects at once, so the choice is made for you. Say you’ve got eight hours a week around homework and a part-time job. Eight hours moves one project forward. Split across three ideas, it keeps all three permanently stuck at the starting line. The math forces focus, and that’s a gift.
A working setup: one project, one finish line, one parking-lot note, and a habit of writing new ideas down instead of chasing them. When school gets brutal, protect the focus by shrinking the project, not by swapping it. And if you keep starting things and never finishing, the fix might be structure. That’s a big part of why a program like batch0 runs as four one-week sprints with a hard demo day at the end. A deadline you can’t quietly slip past often turns an idea-hopper into someone who ships.
The bottom line
Ideas are cheap and finishing is rare. That’s the whole game. The founders you admire aren’t more creative than you. They’re just more disciplined about ignoring the good ideas that would pull them off course, so they can drag the remaining one all the way to done.
So pick your one thing. Park everything else. And the next time a shiny new idea shows up mid-project, don’t ask whether it’s good. Assume it is. Ask whether it’s better than finishing what you started, then get back to work. When you’ve carried one company across the finish line, you’ll have earned the right to pick the next one, and you can apply that focus to something real.