Add A Zero Heuristic
The 'Add A Zero' Heuristic
"If you want to improve the speed of a company, then make faster decisions." — Brian Chesky
What It Is
A mental model for goal setting where leaders arbitrarily increase the target by 10x (add a zero) to force the team to abandon current processes and use first-principles thinking.
When To Use
- Annual planning or kick-offs for major initiatives
- Team is defaulting to safe, low-impact optimization work
- Current processes mathematically cannot achieve the required scale
- Need to break incrementalism and inspire breakthrough thinking
Core Principles
1. Force a Process Break
If the goal is 10x higher, the current way of working is mathematically impossible. The team must invent a new way.
2. First Principles Thinking
Break the problem down to its fundamental components to reconstruct a solution that supports scale.
3. See Potential in People
Use the ambitious goal to signal belief in the team's capability, not just as a demand for more hours.
4. Pace Setting
Use the expanded goal to drive decision velocity. "Can we decide this now?" instead of "Circle back next week."
How To Apply
STEP 1: State Current Target
└── "We need to acquire 10,000 new hosts this quarter"
STEP 2: Add a Zero
└── "What if we needed to acquire 100,000?"
STEP 3: List Why Current Process Fails
└── "Manual outreach can't scale to 100K"
└── "Current funnel conversion is too slow"
STEP 4: Brainstorm New Approaches
└── "What would we need to build?"
└── "What partnerships would enable this?"
└── "What constraints can we remove?"
STEP 5: Extract Feasible Innovations
└── Apply breakthrough ideas to original target
Common Mistakes
❌ Simply demanding 10x results without allowing the team to change constraints
❌ Using this as a pressure tactic rather than a thinking exercise
❌ Applying it to tasks where incremental improvement is actually the right approach
Real-World Example
The internal Airbnb mantra of "Add a zero" which pushes teams to rethink how they acquire hosts or manage support tickets at a fundamentally different scale.
Source: Brian Chesky, Lenny's Podcast
More from coowoolf/insighthunt-skills
gardening-mindset
Use when dealing with ecosystems, network effects, or high-uncertainty environments where the right answer cannot be known in advance, when rigid planning consumes more value than it creates
45gamification-triad
Use when designing retention mechanisms, habit loops, or auditing why users drop off despite engaging with core features, to structure gamification beyond superficial badges
44three-layer-agent-stack
Use when building AI-powered products or agents, when raw model intelligence isn't enough to solve user problems, or when designing the architecture for agentic workflows
15minimum lovable product (mlp)
In an era where AI lowers the cost of building software, viability is obsolete. The differentiator is joy and emotional connection. Prioritize "Wow" over "Aha"—brand is product interaction.
14pre-mortem-kill-criteria
Use before launching products or signing contracts, when needing to combat sunk cost fallacy, or when standard pre-mortems fail to change behavior
14curiosity-loops
Use when facing a significant decision (career pivot, product direction, technical choice) and feeling stuck or indecisive, when seeking contextual advice rather than generic recommendations
13