── ── Mental model

Tunnel Vision & Slack

When urgent demands consume all your bandwidth, the future becomes cognitively inaccessible — not a choice, but a structural block. Mullainathan & Shafir (2013) call this the scarcity trap: scarcity captures the mind and perpetuates itself. The fix is structural: leave slack — protected time that cannot be consumed by tunnel demands.

How it works

Gate: Confirm structural bandwidth scarcity, not missing goal clarity. Solve goal clarity first if needed.

1. Audit allocation. Map last 2 weeks: % inside tunnel (urgent/reactive) vs. outside (strategic). Most find 80–95% inside. 2. Name top 3 tunnel-entry triggers. Which recurring demands most reliably consume bandwidth? 3. Design structural responses. For each trigger: eliminate / delegate / batch / time-box. Design, not willpower. 4. Reserve 20% slack in calendar. Block as recurring protected time. If 20% feels impossible, start with 10%. 5. Define outside-the-tunnel activities specifically. "Thinking time" gets consumed; "competitive landscape review" gets done. 6. Build system-level protection. Calendar blocking + auto-decline + delegation authority + stated policy + weekly review.

Stop-rule: If slack keeps getting consumed despite structural design, add a harder barrier before concluding slack is impossible.

When to use it

• ** recent weeks described as "firefighting" or "just keeping up" · strategic initiatives keep getting pushed · important-but-not-urgent work absent >2 weeks · capacity >85–90% · team says "no time to improve the system."

Worked example

Eisenhower's Time Management System (1943–1954)

Dwight Eisenhower faced a tunnel-generating environment of unmatched density: as Supreme Allied Commander (1943–1945) and then President (1953–1961), the volume of urgent demands was effectively infinite. His documented response was not to process more urgency faster — it was to architect protected slack for important-not-urgent work.