Validate Before Building
Core Concept
Strategy without user validation is fiction. Every assumption in a strategy doc, pricing model, or GTM plan is untested until someone who isn’t you confirms it. The cheapest way to reduce risk is usually a conversation, not code.
The Pattern
You build a pricing strategy, a launch plan, pitch copy, and competitive positioning — all before talking to a single potential customer. It feels productive. It’s actually “running your startup in your imagination” (Rob Fitzpatrick, The Mom Test). The strategy docs create an illusion of progress while the core risk — “does anyone want this?” — remains unaddressed.
Where I’ve Seen It
- Show Notes (Feb 2026): CEO built pricing, GTM, 3-wave launch plan before a single Mom Test conversation. Dave challenged: “are we using lean startup methodology or assuming too much?” Led to a hard rule: validate the current phase’s assumption before building for the next phase.
- General pattern in startups: Product-minded founders default to building because building feels like progress. Distribution-minded founders default to selling. Neither defaults to listening.
The Countermeasure
- Name your biggest assumption. What, if wrong, kills the business?
- Design the cheapest test. Usually a conversation (Mom Test), not code.
- Set a kill threshold. “If 0 out of N conversations confirm X, we reassess.”
- Front-load validation over feature development. Speed of learning > speed of building.
Related Patterns
- Fishing-Pond-Effect — Where you test matters as much as what you test
- Non-Consumption-JTBD — Some jobs can’t be validated through conversation at all
- Solve-The-Meta-Problem — Parent pattern: validate-before-building IS “solve for learning speed, not product completeness”
- Iteration-Speed-Is-The-Strategy — Conversation as the cheapest iteration cycle