I have a notes app full of ideas.
Product ideas. Feature ideas. Business ideas. Some good, some bad, most somewhere in between. I've been collecting them for years.
You probably have something similar. A notebook. A Notion database. A folder of voice memos. Ideas waiting for "someday."
Here's what I've learned: the ideas aren't special. Everyone has them. The difference between people who build things and people who dream about building things has nothing to do with the quality of their ideas.
It has everything to do with what happens next.
The Myth of the Great Idea
We love stories about great ideas. The eureka moment. The flash of insight. The napkin sketch that became a billion-dollar company.
These stories are mostly fiction. Or at least, they're edited.
Most successful products didn't start with a unique idea. They started with an obvious idea, executed well, iterated relentlessly, and got a little lucky with timing.
Dropbox: "What if files synced automatically?" Obvious. Slack: "What if work chat was better?" Obvious. Airbnb: "What if people rented their spare rooms?" Obvious.
The ideas weren't special. The execution was.
Ideas Are Multipliers, Execution Is the Base
Derek Sivers has this framework: ideas are worth nothing. Execution is everything.
More precisely: a brilliant idea with weak execution produces a small result. A so-so idea with brilliant execution produces a big result.
The math looks something like this:
- Weak idea × Brilliant execution = Something
- Brilliant idea × Weak execution = Nothing
- Brilliant idea × Brilliant execution = Rare
You can't control whether your idea is brilliant. You probably can't even tell. But you can control whether you execute.
The Idea Graveyard
Open your notes app. Look at all those ideas.
How long have they been sitting there? Months? Years?
They're not waiting for the right time. They're not waiting for you to be ready. They're waiting because starting is scary and ideas are safe.
Ideas don't require you to fail publicly. Ideas don't get rejected by users. Ideas don't expose your limitations.
That's why they stay in the notebook.
What Execution Actually Looks Like
Here's what happens when you stop protecting ideas and start executing:
Day 1: Describe it clearly. Write down what the thing does. Not features—outcomes. What problem does it solve? For whom? Why would they care?
Days 2-7: Build the ugliest possible version. Not a prototype. Not a mockup. Something that works. Ship it ugly.
Day 8+: Put it in front of people. Real people with the problem. Watch what they do. Listen to what they say. Learn.
Ongoing: Iterate based on reality. The real idea—the one worth building—emerges from this process. It won't look like what you started with.
The Idea Will Change
This is the part most people don't expect: the idea you start with is never the idea you end up with.
Twitter started as a podcasting platform. Instagram started as a check-in app. Slack started as a video game company.
The initial idea was just the excuse to start. The real idea came from building, learning, and adapting.
If you wait for the perfect idea before starting, you'll never find it. The perfect idea is on the other side of executing the imperfect one.
Permission to Start Small
You don't need to see the whole staircase. You don't need a business plan. You don't need to know where this is going.
You need to take the first step.
Build the smallest possible version. Put it in front of one person. Learn something. Take the next step.
The path reveals itself as you walk it.
The Real Difference
The difference between builders and dreamers isn't talent. It isn't luck. It isn't having better ideas.
It's the willingness to start before you're ready, with an idea that isn't perfect, knowing you'll probably have to change everything anyway.
That's it.
Your ideas aren't precious. They're starting points.
Pick one. Start building. See what happens.
Related Reading
- How to Validate Without Building Anything — Test your idea before you write any code.
- Ship It Ugly — Why your first version should embarrass you.
- The Imposter Syndrome That's Keeping You Stuck — You don't need to be a "real developer" to build real things.