What the book argues
"Fail fast, pivot quickly, and treat every launch as an experiment. The sooner you learn what doesn't work, the better."
In resource-constrained communities, failing fast can damage trust — sometimes deliberation matters more than speed.
Ries' fail-fast philosophy assumes that the cost of failure is low and that users will forgive repeated pivots. In communities like the ones I work with — students, graduates, and early-career professionals in Morocco — trust is fragile and resources are scarce. A failed initiative doesn't just waste money; it erodes the community's willingness to engage with future initiatives. Sometimes it's better to validate thoroughly before launching than to learn by failing publicly.
Evidence from my experience
When launching Vanguard-Community, I spent weeks designing governance structures and recruiting administrators before opening to beneficiaries. A "fail fast" approach might have launched with a WhatsApp group and iterated — but the deliberate approach meant 60 beneficiaries engaged in the first 3 months with zero trust-building friction.
What the book argues
"Build the minimum viable product — the smallest thing you can build that lets you start learning."
When people's wellbeing is at stake, the bar for "viable" should be higher than minimal.
The MVP concept works well for software products where a bug is an inconvenience. But in social impact work — workshops on hate speech, community support systems, mentorship programs — a too-minimal offering can actively harm participants. A poorly facilitated hate speech workshop could reinforce the very attitudes it aims to counter. The "viable" threshold must account for the human stakes involved.
Evidence from my experience
The Hate Speech Workshop wasn't a minimal test — I invested in the full methodology (Iceberg model, empathy mapping, Counterspeech, role-play) before running it with 50 participants. The thoroughness is why the session doubled from 2 to 4 hours: participants trusted the process enough to go deeper.