Build your own ideas with structure

April 21, 2025 · 4 min read

An idea without structure is just a thought. Structure is what turns thinking into building.

I have notebooks full of ideas I never shipped. Most people do. The problem isn't ideas — they're abundant. The problem is the gap between having an idea and the first version of it existing in the world. That gap is where most good things die.

Why structure doesn't kill creativity

There's a common belief that structure is the enemy of spontaneity. That if you plan too much, you lose the spark. I've found the opposite to be true.

Structure is what makes creativity sustainable. A blank canvas is terrifying. A framework with defined edges is where real work happens. When I started treating ideas like projects — with a clear scope, a defined first step, and an explicit list of what I wouldn't include — more of them actually shipped.

The three questions

Every idea I work on now passes through three questions before I write a single line of code or design a single screen:

What is the simplest version of this that would prove the idea works?

Who is this actually for, and what do they need to feel in the first 30 seconds of using it? And: what is the one constraint that will force me to make real decisions instead of deferring them?

These aren't restrictions. They're handles. They give you something to hold onto when the idea starts to feel overwhelming — which it always does, somewhere in the middle.

Shipping ugly first

The hardest part is not the building. It's the permission you have to give yourself to ship something imperfect.

Structure helps here too. If you've defined what "done" looks like — not perfect, just done — you have a finish line. Without one, you'll keep adding features and adjusting details until the project quietly dies of your own perfectionism. I've killed more projects that way than through any external obstacle.

A system, not a method

I don't think there's one right way to structure ideas. What matters is that you have something — a template, a ritual, a document — that consistently moves you from idea to artifact.

Mine involves four fields: what the thing is, who it's for, what the first working version looks like, and a date by which I'll decide if it's worth continuing. Four fields. But they've shipped more ideas than any planning tool I've ever tried.

The idea isn't the thing. The thing is the thing.