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.

Why it works

A failed solution attempt is not simply a waste; it is a diagnostic experiment. The point at which the attempt breaks down reveals the constraint that is blocking the solution, often more precisely than any amount of reflection before trying. This reframe — from failure-as-waste to failure-as-data — changes both the emotional response and the cognitive strategy: instead of abandoning the approach, you interrogate the failure mode.

How to do it

1. After a failed attempt, write: "This approach failed at [specific step]. What constraint is that revealing?"
2. Ask: "Does this failure mean the constraint is real, or does it mean my implementation was wrong?"
3. If the constraint is real, ask: "Is it physical, logical, or assumed?" — then target the assumed ones first.
4. Design the next attempt specifically to test whether the identified constraint is as fixed as it appeared.

Evidence

Failure-as-information framing is consistent with a growth mindset (Dweck) and with engineering failure analysis. In insight problem research, subjects who reflected on failed attempts (rather than abandoning them) showed improved solution rates in subsequent attempts. (mechanistic)

The research support here is largely from educational psychology and engineering practice rather than directly from constraint-relaxation paradigms; treating failure as data is a sound heuristic with indirect empirical grounding.

Common mistake

Switching to a completely different approach after failure without diagnosing where exactly the first attempt broke down, which means the same hidden constraint will block the second attempt too.