problem-solving

A dispatch-based technique map matches specific stuck symptoms to proven methods like Simplification Cascades or Inversion Exercise, providing a structured process to apply steps and document outcomes for resolving complex bottlenecks.

You resolve recurring complexity spirals by running the When Stuck flow to select a technique such as Meta-Pattern Recognition, reading the corresponding reference, and applying the structured steps to diagnose and break the recurring pattern.

Yes, you can apply these problem-solving techniques across product, engineering, design, data, and operations contexts to accelerate resolution of innovation blocks, recurring patterns, and production-scale questions.

No, you do not need external tools to run the Scale Game or Inversion Exercise, because the Skill requires no external tooling beyond the included references to load techniques, apply steps, and document outcomes.

The best way to diagnose stubborn production-scale bottlenecks is to match your symptoms to proven techniques like Collision-Zone Thinking or the Scale Game, then follow the reference-driven execution steps to reach clarity and decision.

Your problem-solving process gets stuck on innovation blocks because you lack a structured, repeatable approach to map symptoms to proven techniques, causing time to clarity to increase without a dispatch-based diagnosis method.