Fear-Origin Audit for Product Bets
Products built from competitive fear fail; audit the motivation before you audit the roadmap.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 85%
Paul Adams (CPO at Intercom, formerly Facebook and Google) worked on Google Buzz and Google Plus and diagnosed a common root cause: the motivation came from a place of fear, not from a genuine desire to solve a human problem. His counter-system pairs a motivation audit at the origin of any bet with a culture that makes big bets survivable — ship fast, ship early, ship often — while consciously holding the tension against a team's craft standards.
Origin
Paul Adams' first-hand account of Google's social projects (Buzz, Google+), contrasted with the culture he helped design at Intercom after co-founder Eoghan McCabe pitched him with 'at Facebook you can design the product, at Intercom you can design the company'.
Core principles
- 01Ask where the bet came from. Fear and love produce different products.
- 02Competitive fear as a root cause reliably produces privacy disasters, secrecy, and internal antagonism.
- 03Formative research (mapping how people actually live) outranks tactical research (can they use the button).
- 04Big bets mean you will get a lot of it wrong — so the culture must make being wrong cheap.
- 05Ship fast, ship early, ship often — failure is embedded in the principle, not an exception to it.
- 06The tension between craft standards and shipping fast never resolves; it gets navigated.
How to run it
- 1
Interrogate the origin of the bet
Before resourcing a major initiative, ask out loud: is this coming from a place of fear (a competitor is winning, we look weak) or from a place of genuinely understanding what people struggle with? Write the answer down.
Pro tip Fear-origin bets have tells: extreme secrecy, separate buildings, separate keycards, all-hands mobilization, and internal antagonism from the teams excluded.
Watch out Fear-origin projects can still be brilliantly staffed and well executed. Execution quality is not evidence the motivation was sound.
- 2
Buy formative research alongside tactical research
When asked for tactical research ('can people use this?'), do it — and take an extra 20 minutes per session for formative work. Adams mapped people's whole social networks: who's in them, how they communicate, on which channels, what works and what doesn't.
Pro tip Piggyback formative questions onto sessions you're already running. It's the cheapest way to get strategy-grade insight out of a usability budget.
- 3
Wait for the pattern to repeat across dozens of sessions
Over ~18 months and dozens of people, Adams saw the same pattern every single time: people need far better ways to communicate with small groups of family and friends. A pattern that holds across dozens of sessions is a real finding, not an anecdote.
Pro tip The obvious-in-hindsight finding (this became WhatsApp and iMessage) is the valuable one. It only looks obvious afterwards.
Watch out A correct finding attached to a fear-motivated project still fails. Google+ was built on this research and still came from the wrong place.
- 4
Design a culture that makes big bets survivable
If you prefer big bets over incremental ones — higher risk, higher reward — you must accept that a lot will go wrong. Encode it: ship fast, ship early, ship often. Fast, early shipping means fast learning, which means fast change and fast improvement.
Pro tip The earlier formulation, 'ship to learn', makes the purpose explicit. Say both.
- 5
Name and hold the craft tension explicitly
A design-founder culture with high craft standards will resist shipping fast — nobody wants to be embarrassed by what they ship. Do not pretend to resolve this. Encourage both high standards and fast shipping, and navigate the tension consciously and continuously.
Pro tip Say out loud that the tension is permanent. Teams handle a named trade-off far better than a hidden one.
Watch out Resolving the tension in either direction — pure craft or pure velocity — breaks the system.
In the wild
Adams spent four years at Google working on failed social projects. The motivation, he argues, came from competitive fear rather than from a desire to make something great for people. Google+ was so secret that everyone on it moved to a separate building with a separate keycard, breeding internal antagonism. When Adams left mid-project for Facebook, Google assumed he was a spy, quarantined him and forensically analyzed his laptop.
→ Buzz was a privacy disaster and Google+ followed. Adams' root-cause diagnosis: run from a place of competitive fear, which he doesn't think leads to good things. Meanwhile Google Maps and Android — not fear-driven — became some of the best products ever made.
Persuaded to join a 10-person Intercom with the pitch 'at Facebook you can design the product, at Intercom you can design the company', Adams helped build a culture that embraces failure. The principle on the wall — originally 'ship to learn', now 'ship fast, ship early, ship often' — bakes in the expectation that big bets go wrong more often than not.
→ A culture where high-risk/high-reward bets are viable, but with a permanent, acknowledged tension against a design-founder team's craft standards.
Common mistakes
Building from a place of fear
When the root motivation is 'a competitor is beating us here', the resulting product optimizes for the competitor rather than for the user's actual struggle. Adams traces Buzz and Google+ directly to this.
Secrecy as a substitute for conviction
Separate buildings, separate keycards, quarantining departures — extreme secrecy is a symptom of fear-driven programs, and it manufactures internal antagonism that costs you long after launch.
Doing only tactical research
Usability studies tell you if people can use the thing. They never tell you whether the thing should exist. Formative research — mapping how people actually communicate and where it breaks — is what surfaces the real opportunity.
Is it for you?
Best for
Product and design leaders about to launch a defensive initiative against a competitor, and leaders designing a culture around high-risk, high-reward bets.
Not ideal for
Mature businesses whose value genuinely comes from incremental optimization, where big bets are the wrong risk posture.
From the transcript
“I think a lot of the motivation for those projects came from a place of fear you know it didn't come from a place of…”
“but the root cause for me is that the project has been run from a place of fear competitive fear which I don't think leads…”
“and the same pattern emerged every single time which was people need way better ways to communicate with small groups of family and friends”
“principle called ship to learn and or we've actually changed it since over on the wall here ship fast ship early ship often is what…”
“we never want to be embarrassed by what we ship so there's a real tension there”
From the episode
Failure