Coaching practices for Intelligent Failure
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For Intelligent Failure, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- I get something wrong, mutter "ugh, wrong," and just bash at it again right away
- Something I tried just flopped and my instinct is to wince and bury it, but part of me suspects the way it went wrong is actually showing me something I’d never have seen if it had simply worked.
- I keep blaming myself and vowing to just try harder, yet the same failure happens again and again no matter how much willpower I throw at it
- Every time an approach flops I just throw it out and lunge at something totally different, and I keep slamming into the same wall
- I keep grinding to engineer the perfect outcome and getting nowhere, and it just occurred to me I’ve never once flipped it around and asked what would absolutely guarantee this blows up
Practices that may help
- Treating errors as data points
After any failure, immediately extract the specific information the error revealed about the problem.
Productive Failure: How Struggling First Makes Instruction More Effective - Treat errors as adjacent-possible expansion events
When something goes wrong, ask what new territory the failure has made visible that success would have hidden.
The Adjacent Possible, Made Practical - Distinguish system causes from individual causes in the analysis
Most failures have system causes and individual causes; fixing only the individual leaves the system to produce the same result again.
After-Action Review: The US Army’s Tool for Continuous Learning - Treat failed attempts as constraint-locators rather than dead ends
Each failed approach tells you precisely where the active constraint lives — mine that information before trying again.
Constraint Relaxation: Escaping the Walls You Built Yourself - Use inversion as the first model in every problem
Before solving a problem, ask what would guarantee failure — then avoid those things.
Mental Models: Charlie Munger’s Latticework Approach - Build an anti-goal checklist
Keep a running list of "what failure looks like" and review against it.
Inversion: Solve Problems Backward - Just-in-time instruction
Time the instruction to arrive immediately after the failure — not days later and not instead of failure.
Productive Failure: How Struggling First Makes Instruction More Effective - Optimize for avoiding stupidity, not brilliance
Munger: "It is remarkable how much long-term advantage people like us have gotten by trying to be consistently not stupid."
Inversion: Solve Problems Backward - Turn top risks into tripwires
Set a specific signal that tells you a feared failure is starting to happen.
The Pre-Mortem: Imagine It Already Failed - Separate competence from performance
A result below your standard does not retroactively prove you are incompetent — learn to hold these as distinct.
Impostor Phenomenon, Made Practical
Related concerns
- How To Make It Safe To Fail
Ask: does this plan require everything to go right? If so, redesign it.
Design decisions so they work even if some things go wrong
- Keep Failure In Context
Keep the explanation for failure in the domain where it happened — resist letting it spill into a verdict on your whole self.
Make attributions specific, not global
- Learning From Failure
After any failure, immediately extract the specific information the error revealed about the problem.
Treating errors as data points
- Manu Kapur Productive Failure
Productive failure (Manu Kapur) is a teaching design in which students attempt a problem without instruction first, inevitably failing or producing imperfect solutions, before receiving formal teaching. Multiple controlled studies show this sequence — struggle first, then instruction — produces significantly better conceptual understanding and transfer than instruction-first approaches, though direct procedural performance often remains equivalent.
- Startup Failure Analysis
Failure analysis contains the most actionable information in any honest review.
Spend more time on "what did not go well" than on what did
- Ability Vs Strategy Failure
Replace "I can’t do this" with "that approach didn’t work here" — ability is fixed in the sentence, strategy is not.
Attribute failure to strategy, not ability
Describe your situation in your own words to search the complete practice library.