“Treating a startup idea as a question changes what you're looking for. If an idea is a blueprint, it has to be right. But if it's a question, it can be wrong, so long as it's wrong in a way that leads to more ideas.”
Blueprint or Question
In “Ideas for Startups” (2005), Paul Graham contrasts two ways to hold a startup idea. State it as a plan you mean to build and it invites objections: say you’ll build a web-based spreadsheet, and critics (loudest among them the ones in your own head) reply that you’d be competing with Microsoft, that the UI won’t measure up, that nobody will trust you with their data. A blueprint has to survive all of that before you write a line. Frame it as a question instead and the same idea becomes something to try, not defend: “let’s try making a web-based spreadsheet and see how far we get.” Now the bar is only whether the attempt teaches you anything.
A blueprint that’s wrong tends to be a dead end. A question that’s wrong can still point somewhere: Graham’s spreadsheet might turn into a collaboration tool that doesn’t have a name yet, something you’d never have specified up front but find by building toward it. Held that way, an early idea is less a thing to get right than a place to start looking.