Answer extracted from the The Conference Room with Simon Lader podcast — listen to the full episode below.
Why High-Performing Teams Need an 80% Confidence Goal Sweet Spot
High-performing teams perform best with goals they have 80% confidence in achieving. At 100% confidence, goals are too easy and don't extract peak performance; at 50%, failure rates spike too high. With 80% confidence goals, one-fifth will inevitably fail—and this must not just be acceptable but actively rewarded in corporate culture.
The Confidence Paradox: Why Easy Goals Kill Performance
Setting goals your team is completely certain about achieving sounds safe, but it's a performance trap. When there's no risk of failure, there's no pressure to innovate or push boundaries. Teams coast instead of stretching. The goal itself becomes a floor rather than a challenge.
The opposite extreme is equally damaging. Goals where your team has only 50% confidence create chaos and demoralization. The failure rate becomes too high for psychological safety, and people stop believing in the objectives. Trust erodes when failure feels commonplace rather than exceptional.
The 80% Rule: Mathematically Embracing Failure
The sweet spot is 80% confidence—meaning one-fifth of goals will fail. This is the zone where teams are genuinely stretched, where they must think differently and execute at their best, yet where most objectives still succeed. As David Etchew explains in the episode, this statistical inevitability requires a cultural shift.
The math is clear, but the leadership implication is harder: leaders must actively accept risk on behalf of their teams. That means not just tolerating the 20% failure rate—it means rewarding it, learning from it, and building it into how the organization measures success.
"I could fail every day as long as I failed differently the day before I learned from it. The thing that drives me nuts is failing the same way twice."
David Etchew — CEO of Cyberbit. With over 20 years leading businesses from startups to global organizations at GE (where he ran a $30 million security business line), Rapid7, and other major enterprises, Etchew brings deep experience in scaling teams and navigating high-stakes decisions across diverse company stages.
Etchew's insight captures the core contract: failure is not the enemy—repeated failure of the same kind is. The culture must distinguish between productive failure (new learning) and reckless failure (ignoring past lessons). This distinction is where the 80% rule becomes truly powerful. Discussed at length in this podcast, it's the difference between building a learning organization and a risk-averse one.
Why Corporate Culture Is the Real Constraint
The 80% confidence goal itself is a simple metric. The hard part is the culture that surrounds it. Most organizations are structurally wired to punish failure—even the productive kind. Bonuses, promotions, and reputations are built on success metrics that don't account for acceptable failure rates.
For the 80% rule to work, leaders must visibly reward teams that fail as long as they learned something new. Performance reviews must ask: "Did you attempt 80% goals? Did you fail differently than before?" This cultural inversion is explored in detail by David Etchew, who has implemented it across companies at different scales.
Key takeaways
- High-performing teams need 80% confidence goals—ambitious enough to extract peak performance, yet statistically likely to succeed four times out of five.
- At 100% confidence, goals are too safe and don't drive innovation; at 50% confidence, failure rates undermine psychological safety.
- With 80% confidence, one-fifth of goals will fail—and this must be accepted and rewarded, not punished.
- The real challenge is building a corporate culture that distinguishes between productive failure (new learning) and reckless repetition of old mistakes.
See also
How do large organizations like Amazon and AWS maintain innovation despite their enormous scale?
Large organizations maintain innovation through first-principles thinking, small team structures (like AWS's two-pizza rule), and flat organizational hierarchies that enable rapid decision-making despite scale.
What operational capabilities do small companies have relative to larger enterprises?
Small companies are much more nimble, closer to the customer, and quicker in their decision processes and how they drive change. Large companies face organizational friction and longer approval cycles.
What advantages does cross-functional leadership experience provide compared to deep specialization in a single domain?
Cross-functional leadership experience provides context and empathy across different business functions, making it easier to build teams and navigate complexity in diverse organizations.