Idea validation
How to validate a project before you launch it
Side project, new product line, or internal initiative — any project benefits from validation before launch. Here's a simple way to de-risk before you commit resources.
“Validation” has become startup jargon, but the idea is older and broader than startups. Anyone about to invest serious time — a side project, a new product line, a community initiative, an internal tool at work — faces the same risk: pouring months into something that, it turns out, nobody needed. Validating a project simply means buying down that risk before you pay it in full.
The one question every project must answer
Before scope, budget, or timeline, every project rests on one assumption: that the outcome it produces is something specific people actually want. Validation is the act of finding that assumption, writing it down plainly, and testing it as cheaply as possible — before the project's momentum makes it embarrassing to stop.
The sunk-cost trap is the real enemy
The longer a project runs, the harder it is to cancel — not because it's working, but because stopping feels like admitting waste. Validating early gives you permission to stop before the trap closes.
A lightweight validation pass for any project
- Write the outcome in one sentence, from the point of view of the person who benefits.
- Name who specifically wants that outcome — and how you know, beyond your own assumption.
- List what they do today instead, and why your project would be worth switching to.
- Pick the riskiest assumption and design a test that costs days, not months.
A project that can't survive a few honest questions on paper won't survive contact with reality.
A structured starting point
The free IdeasBuenas analysis is built exactly for this first pass. You answer a short set of questions about your project and get back a structured read of its potential, its risks, and the next steps that matter — a clear-eyed reality check you can do in an afternoon instead of a planning offsite. Whether your project becomes a company or stays a side project, you'll start with evidence instead of optimism.
Before you commit the calendar, commit ten minutes. Validate the project first.