When improvement stalls despite effort, shift…

When improvement effort in a domain has stalled despite sustained attention, shift focus from single-loop correction (adjusting actions) to double-loop correction (questioning the framework generating actions) by explicitly listing and testing the assumptions underlying your approach.

When This Fires

When you've been working to improve something for weeks/months and results have plateaued
When increasing effort in the current approach produces no marginal improvement
When you feel stuck and keep trying variations of the same basic approach
After 3+ single-loop adjustments fail to move the needle on a specific problem

Common Failure Mode

Trying harder within the same framework: "My sales approach isn't working, so I'll make more calls." If the approach itself is wrong, more calls amplifies the wrong approach. The framework needs questioning: "Am I calling the right people? Is calling the right channel? Is my pitch addressing the right problem?" These are framework-level questions that single-loop adjustment (more calls, better script) can never reach.

The Protocol

(1) When improvement stalls despite effort, stop adjusting within the current framework. (2) List the assumptions underlying your current approach: "This framework assumes that [A], [B], [C]." Be explicit about things you've been taking for granted. (3) For each assumption, ask: "Is this still true? Was it ever true? What evidence supports or contradicts it?" (4) Identify the assumption most likely to be wrong or outdated. (5) Design an experiment that tests a different framework — one that replaces the questionable assumption. Not a parameter adjustment within the old framework, but a fundamentally different approach. (6) Run the alternative framework for a meaningful trial period. If it outperforms → the old framework was the constraint. If it doesn't → test a different assumption.