Stuck for 30+ minutes? Switch abstraction levels — go one…
When stuck on a problem for more than 30-60 minutes at your current level of abstraction, force yourself to spend at least 5-10 minutes at an adjacent level (one step more abstract or one step more concrete) before continuing.
When This Fires
- Debugging for 30+ minutes without progress
- Writing for an hour without getting past a structural problem
- Design work that keeps producing the same unsatisfactory options
- Any problem-solving where effort isn't producing progress
Common Failure Mode
Continuing at the same level because "I'm almost there." Thirty minutes of fixation feels like progress because you're working hard — but effort without progress is fixation, not problem-solving. The level-switch breaks the pattern.
The Protocol
When stuck for 30-60 minutes: (1) Notice the fixation: "I've been working at [this level] for [this long] without progress." (2) Shift one level: Up (more abstract) → "What is the higher-level goal this serves? Am I solving the right problem?" Down (more concrete) → "What specific mechanism is causing the issue? What happens if I trace through step by step?" (3) Spend 5-10 minutes at the adjacent level. (4) Return to the original level with whatever insight the shift produced. The level-switch costs 5-10 minutes and often dissolves 30-60 minutes of fixation.