Instead of stigmatizing failure, LEGO embeds a formal "After Action Review" (AAR) process into its culture, with reviews happening daily at some level. This structured debrief forces teams to analyze why a project failed and apply those specific learnings across the organization to prevent repeat mistakes.
Effective leadership in an innovation-driven company isn't about being 'tough' but 'demanding' of high standards. The Novonesis CEO couples this with an explicit acceptance of failure as an inherent part of R&D, stressing the need to 'fail fast' and learn from it.
During product discovery, Amazon teams ask, "What would be our worst possible news headline?" This pre-mortem practice forces the team to identify and confront potential weak points, blind spots, and negative outcomes upfront. It's a powerful tool for looking around corners and ensuring all bases are covered before committing to build.
For leaders overwhelmed by AI, a practical first step is to apply a lean startup methodology. Mobilize a bright, cross-functional team, encourage rapid, messy iteration without fear, and systematically document failures to enhance what works. This approach prioritizes learning and adaptability over a perfect initial plan.
Foster a culture of experimentation by reframing failure. A test where the hypothesis is disproven is just as valuable as a 'win' because it provides crucial user insights. The program's success should be measured by the quantity of quality tests run, not the percentage of successful hypotheses.
The 'fake press release' is a useful vision-setting tool, but a 'pre-mortem' is more tactical. It involves writing out two scenarios before a project starts: one detailing exactly *why* it succeeded (e.g., team structure, metrics alignment) and another detailing *why* it failed. This forces a proactive discussion of process and risks, not just the desired outcome.
To move beyond static playbooks, treat your team's ways of working (e.g., meetings, frameworks) as a product. Define the problem they solve, for whom, and what success looks like. This approach allows for public reflection and iterative improvement based on whether the process is achieving its goal.
Intuition is not a mystical gut feeling but rapid pattern recognition based on experience. Since leaders cannot "watch game tape," they must build this mental library by systematically discussing failures and setbacks. This process of embedding learnings sharpens their ability to recognize patterns in future situations.
Before starting a project, ask the team to imagine it has failed and write a story explaining why. This exercise in 'time travel' bypasses optimism bias and surfaces critical operational risks, resource gaps, and flawed assumptions that would otherwise be missed until it's too late.
Borrowing from filmmaking, view communication slip-ups not as failures but as different "takes." This reframes errors as opportunities to try a different approach next time, reducing fear and encouraging experimentation and growth.