Nine Nos For Every Yes
Guard product quality with creative restraint — every feature you say yes to is a puppy you must care for forever
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 3
- Confidence
- 88%
Rauch frames product quality as the product of a thousand small details and disciplined restraint. The best product builders say nine nos for every yes, because a feature isn't a one-time decision — it's like adopting a puppy that grows into a demanding beast requiring ongoing care. Saying yes commits you to the real-world complexity that feature will spawn.
Origin
Rauch's own principle, expanded from a tweet: 'The secret to product quality is blood, sweat, and tears.'
Core principles
- 01A great product is a thousand little details, so you are never really done
- 02Every yes creates a permanent maintenance obligation
- 03Restraint is a creative act, not just a defensive one
- 04Quality demands love, obsession, and repeated testing on your own product
How to run it
- 1
Treat each feature request as a long-term adoption
Before saying yes, weigh not just building the feature but caring for it as it grows and generates complexity.
Watch out A feature 'grows into a beast that you have to take care of' — the ongoing cost dwarfs the build cost.
- 2
Default to no
Bias toward roughly nine rejections for every acceptance to protect quality and focus.
- 3
Obsess over the details you do ship
Pour love, restraint, and heavy self-testing into the surfaces you commit to, especially hard cases like mobile web.
Pro tip Dogfood relentlessly — Vercel uses Vercel and v0 to build Vercel and v0.
In the wild
Rauch praises how well Midjourney's mobile website works, noting that making mobile web that good is possible but requires a sense of love, restraint, obsession, and a lot of testing and dogfooding.
→ A polished, high-quality mobile experience that demonstrates what disciplined restraint plus obsession produces.
Common mistakes
Saying yes to too many features
Each yes becomes a demanding, permanent maintenance burden that erodes overall quality; without restraint the product bloats into unmanageable complexity.
Thinking a product is ever 'done'
Because quality lives in a thousand details, treating the work as finished lets those details rot and the quality slip.
Is it for you?
Best for
Founders and product leaders deciding what to build and protecting a quality bar
Not ideal for
Early exploration phases where breadth of experimentation matters more than restraint
From the transcript
“the best product builders will say nine nos for every yes because when you say yes is like adopting a puppy. A feature is like…”
“It grows into a beast that you have to take care of and it's very demanding and loving but also it you know it's a…”
“a a great product is made up of a thousand little details, right? And so you're never really done”
From the episode
Everyone’s an engineer now: Inside v0’s mission to create a hundred million builders
Guillermo Rauch (founder and CEO of Vercel, creators of v0 a