Everything in this series points in one direction. You can't be your own second opinion. Encouragement isn't a verdict. And when you do ask, you quietly select the feedback that will help your idea survive. Follow all of that to the end, and only one move is left, and it's the uncomfortable one: stop waiting for a yes, and go looking for the no.

Most founders do the reverse. They seek validation and merely tolerate criticism when it shows up. Flip the posture. Treat the no as the thing you're hunting for, and treat a yes as something that still has to be earned. Because the no is the cheap information, and an unbuilt year is the expensive one.

Why is the no the bargain?

If your idea has a fatal flaw, that flaw exists right now, whether or not you've found it. You can pay to discover it today — over a coffee, in one hard question, for the price of a little discomfort. Or you can pay to discover it in twelve months, after the build, the launch, and the savings: same flaw, wildly different invoice. Going looking for the no is just choosing to settle the bill while it's still small.

So do the things the rest of this series sets up. Find the person with no stake in your hope and the nerve to be straight with you. Ask the question whose worst answer scares you. And — the part that's actually hard — go in wanting the flaw to be findable. If it's there, today-you and next-year-you both want today-you to find it.

The same flaw, two invoices: find it now for the price of a hard question, or in twelve months for a year of building A flaw in your idea exists today either way. One path finds it now at tiny cost; the other avoids it and pays a year of wasted building later. GO LOOKING FOR THE NO The flaw exists now either way. Only the invoice changes. ! The flaw — it's there today go looking for it now avoid it PAY NOW A hard question a coffee. a little discomfort. PAY LATER A year of building the build · the launch · the savings the runway · the year you don't get back Same flaw. Bigger invoice. A yes that could never have been a no isn't worth having.
The same flaw, two invoices — find it now for the price of a hard question, or later for a year.

A no is not a verdict on you.

The reason we avoid this is that a no feels like a judgement on us. It rarely is. A good no tells you which part is wrong — the market, the timing, the wedge, the price — not that you're incapable. It's a reading on the idea, taken early, when changing course is cheap.

The founders who hear it and adjust aren't the weak ones. They're the ones who didn't spend a year building the wrong version of the right thing. A no in July is often exactly what makes a yes in October possible.

"A yes that could never have been a no isn't worth having."

What survives the door

Here's the payoff, and it's the opposite of what avoidance promises. A yes that survived a real attempt to kill it is worth something; a self-generated yes never can be. When you went looking for the no — asked the sharp question of the right person, genuinely open to the answer — and the idea still held, that's not reassurance. That's evidence. It's the only kind of yes you can actually build on, because it earned its way past a test that could have stopped it.

That's the whole difference between feeling validated and being right. The mirror will always say go; it's built to. The door might say no. The founders who make it through aren't the ones who avoided the door — they're the ones who walked up to it hoping it would tell them the truth, and then believed it when it did.

Want more like this? Rick writes about the go/no-go decision, founder counterintuitions, and the business of building ventures worth building.

All writing