Answer extracted from the The Conference Room with Simon Lader podcast — listen to the full episode below.
How should organizations reframe missed goals into learning outcomes?
Shift the conversation away from whether targets were hit, and focus instead on what was learned. The real value of a missed goal lies in ensuring you never fail the same way twice—failing differently each time means progress, even when the original target wasn't achieved.
David Etchew implements this principle at board level through a structured quarterly presentation format. Each team presents three elements: what was accomplished, what was learned, and goals for the next quarter. The middle section—learning—is often overlooked in traditional board discussions, yet it's where the most important insights live.
When targets aren't achieved for substantive reasons—discovering unknown unknowns, encountering unexpected market shifts, or managing resource constraints—the learning becomes the primary outcome. As Etchew explains in the episode, organizations that treat missed goals as learning opportunities rather than failures cultivate resilience and adaptive capability.
Making learning the centerpiece of goal reviews
The difference between repeating failure and moving forward hinges on what Etchew emphasizes to his teams: "I could fail every day as long as I failed differently the day before and learned from it." This mindset reframes accountability away from rigid outcome targets toward intellectual rigor—did the team genuinely extract what could be learned from the attempt?
A goal that isn't achieved still has value if it generated insight. Unknown unknowns discovered during execution—market conditions that shifted, technical obstacles that surfaced, or dependencies that weren't anticipated—are legitimate learning outcomes. These insights directly inform strategy and planning for the next cycle, making them as valuable as hitting the original target.
The inverse problem, which Etchew names explicitly, is far more damaging: failing the same way twice. That pattern signals either that learning didn't occur, wasn't documented, or wasn't acted upon. A point discussed at length in the podcast is how high-performing organizations institutionalize this learning—making it visible, repeatable, and part of the quarterly cadence rather than a one-off conversation.
"I could fail every day as long as I failed differently the day before and learned from it. The thing that drives me nuts is failing the same way twice."
David Etchew — CEO of Cyberbit and cybersecurity executive with over 20 years of experience building, scaling, and leading businesses from startups to major global organizations. His career spans senior roles at GE (where he headed security globally and managed a $30 million business line), Rapid7, Gemalto, and CEO positions at NISO and Rangeforce before becoming CEO of Cyberbit following their acquisition of Rangeforce.
If you want to explore how this principle connects to team performance expectations, the full episode covers the relationship between acceptable failure rates and high-performing culture.
Key takeaways
- Structure quarterly reviews to explicitly address learning from unachieved goals, not just accomplishments and future targets.
- Treat goals missed for substantive reasons—market shifts, unknown unknowns, resource changes—as legitimate learning outcomes.
- The only failure that matters is repeating the same failure twice; differentiated failure with documented learning is progress.
- Make learning visible and actionable at the board level so it informs strategy and prevents institutional blind spots.
See also
What is the relationship between acceptable failure rates and high-performing team culture?
High-performing teams perform best with goals that they have 80% confidence in achieving. If goals have 100% confidence, they're too easy and don't extract the full potential of the team.
How do large organizations like Amazon and AWS maintain innovation despite their enormous scale?
Large organizations maintain innovation through first principles like keeping teams small enough to coordinate effectively and empowering them to act autonomously within clear boundaries.
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 structural constraints that slow decision velocity.