Coaching practices for What to Do When Solution Fails
Describe almost anything you are working through and IX Coach finds the practices whose real-world fit is closest. For What to Do When Solution Fails, these are the strongest matches in the current practice library.
Does this sound like the set of challenges you might be facing?
- 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 finally saw the right answer, but I just nodded and moved on without ever lining it up against what I’d tried
- My kid and I agree on a fix and it sounds great in the moment, but a few days later it’s fallen apart again
- I try one way to crack a new problem, it doesn’t work, and I immediately stop and go look it up
- I always jump straight to the worked example or the solution before I’ve even tried the problem myself, and the explanation never really lands
Practices that may help
- 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 - Canonical contrast after failure
After your attempts, examine the expert solution specifically for what your approaches were missing.
Productive Failure: How Struggling First Makes Instruction More Effective - Evaluate solutions for durability: realistic, mutually satisfying, safe
A collaborative solution that fails one of three tests — realistic, mutually satisfying, safe — will not hold.
Collaborative Problem Solving (Ross Greene) - Solution-space exploration
Generate multiple different approaches to a problem before converging on one.
Productive Failure: How Struggling First Makes Instruction More Effective - Incubation: Why Stepping Away Solves Problems
When you step away from a stuck problem, solutions often surface later — the incubation effect. There is genuine experimental research showing incubation periods can improve problem-solving, especially for creative problems, though the effect is modest and depends on conditions. The practical upshot is real: deliberate breaks beat grinding when you’re truly stuck. - Attempt problems before seeing the solution
Try to solve or answer a question before you are shown how — even if you fail.
The Generation Effect: Why Making It Yourself Makes It Stick - 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 - Distinguish diagnostic trees (why?) from solution trees (how?)
Use a "why?" tree to find root causes and a "how?" tree to generate solutions — mixing them produces confusing structures.
Issue Tree Analysis - Rebuild from fundamentals and stress-test it
Reassemble a solution from verified parts, then attack it to find where it breaks.
First-Principles Thinking, Made Usable - State the goal, then invert it
Ask "what would guarantee I fail at this?" before asking how to succeed.
Inversion: Solve Problems Backward
Related concerns
- Attempt Before Instruction
Try to solve a new type of problem with your current knowledge before any formal teaching.
Attempt before instruction
- Creative Failure Analysis
Each failed approach tells you precisely where the active constraint lives — mine that information before trying again.
Treat failed attempts as constraint-locators rather than dead ends
- Productive Failure How Struggling First Makes Instruction More Effective At Work
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.
- Productive Failure Practice
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.
- Responding To Failure Productively
After any failure, immediately extract the specific information the error revealed about the problem.
Treating errors as data points
- When Mental Models Latticework Inversion As Entry Model
Before solving a problem, ask what would guarantee failure — then avoid those things.
Use inversion as the first model in every problem
Describe your situation in your own words to search the complete practice library.