Tunnel Vision & Slack

Activate when: user says 'I'm always firefighting,' 'I never have time to think,' 'everything feels urgent,' 'I can't get ahead,' or 'we keep pushing strategic work because of day-to-day fires.' Do NOT activate when: the urgency is a single bounded crisis with a clear end date; or the person lacks goal clarity and does not yet know what strategic work to protect time for.

deciqAI@deciqai

Install

openclaw skills install @deciqai/tunnel-vision-slack

Tunnel Vision & Slack

Overview

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.

Cross-skill sequencing: Use BEFORE [deep-work] (diagnose why protection keeps failing) · WITH [metacognition] (catch tunnel-entry early) · AFTER [ooda-loop] (slack restores the strategic Observe phase tunneling collapses).

When to Use

Use when: 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."

When NOT to use: urgency is bounded and temporary · problem is prioritization skill not bandwidth scarcity · true existential emergency · first 30 days in a new role.

Coaching Novices (Adaptive Front Door)

Engine mode: user has a concrete case → run The Process directly.
Coach mode: user is unfamiliar or skeptical → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

Frame it: "The tunnel isn't laziness — it's structural. When urgent work consumes bandwidth, strategic thinking is physically crowded out. Slack is the fix."
Check fit: "What did your last two weeks look like — responding vs. planning? What strategic work got displaced?"
Elicit the real case: "What specifically has been getting pushed? For how long?" > [WAIT — do not advance until user responds]
One step at a time: "Pick one displaced strategic activity. What would protecting 90 min/week for it actually require — in the calendar, not in intention?" > [WAIT — do not advance until user responds]
Name the insight: "That protected time is where you catch opportunities before they become urgent and prevent fires before they start." > [WAIT — do not advance until user responds]

The Process

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

Audit allocation. Map last 2 weeks: % inside tunnel (urgent/reactive) vs. outside (strategic). Most find 80–95% inside.
Name top 3 tunnel-entry triggers. Which recurring demands most reliably consume bandwidth?
Design structural responses. For each trigger: eliminate / delegate / batch / time-box. Design, not willpower.
Reserve 20% slack in calendar. Block as recurring protected time. If 20% feels impossible, start with 10%.
Define outside-the-tunnel activities specifically. "Thinking time" gets consumed; "competitive landscape review" gets done.
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.

Output: Slack Architecture Map

text

Current allocation: Inside tunnel ___%  /  Outside tunnel ___%

Top 3 tunnel-entry triggers:
1. [Trigger] → [eliminate/delegate/batch/time-box] → [Specific mechanism]
2. [Trigger] → [Response] → [Mechanism]
3. [Trigger] → [Response] → [Mechanism]

Protected slack: ___ hrs/week = ___%  |  Slots: [Day/time — purpose]
Protection mechanism: [auto-decline / delegation authority / stated policy / ...]
Outside-the-tunnel activities: [Activity 1] / [Activity 2] / [Activity 3]
30-day review: [Date] — Did slack hold? What consumed it? Fix needed?

→ Method in Action: Eisenhower's Time Management System (1943–1954)

Slack Design Packs

Product & Engineering: Teams at 90–100% capacity ship features but miss architectural problems. 20% slack is where refactoring and cross-team insight happen.
Founding & Leadership: Founders spending 90% on firefighting lose positioning and competitor-move time. One protected half-day/week is the minimum viable slack.
Research & Knowledge Work: Researchers who protect 30% for uninterrupted exploration produce breakthrough work; fully-scheduled researchers produce consistently adequate work.

Applying It Well

Diagnose structurally, not morally. Identify the structural trigger and design it out — not willpower.
20% is the minimum viable slack. Below 20%, strategic work happens only during crises or by accident.
Protect slack with systems. Blocked calendar + auto-decline + delegation authority + physical separation.
Name outside-the-tunnel activities specifically. "Thinking time" gets consumed; "competitive landscape review" gets done.
Review weekly whether slack held. "I got busy" is the tunnel — add a structural barrier next week.

→ Primary sources: references/sources.md

Common Rationalizations

[D] = designed upfront | [O] = observed in real use. [O] entries are more valuable.

Rationalization	Why It's a Trap
[D] "Once this quarter's fires are out, I'll have time to think."	New fires always start. Waiting for the tunnel to end is how people spend entire careers in it.
[D] "Full capacity = maximum productivity."	Zero buffer for variance or adaptation. 100%-utilized systems fail first under unexpected load.
[D] "If I don't respond immediately, things fall apart."	This belief is itself a symptom — delegation and systems have not been built.
[D] "Slack is a luxury for large organizations."	100% utilization is fragility; 20% slack is resilience.
[D] "I tried protecting time before and it never held."	The mechanism was insufficient — add structural barriers, not willpower.
→ Add [O] entries here after each real use — paste the actual failure pattern	What went wrong and why

Red Flags · Verification

Red flags: Cannot name one strategic initiative advanced in the last 2 weeks · every slot is a meeting or urgent · team escalates decisions that should have been delegated · "strategic planning" happens at end of day or weekends.

Verification checklist:

Inside/outside-tunnel allocation measured (not estimated) for last 2 weeks.
Top 3 triggers named with a structural response designed for each.
Slack blocked as recurring calendar events with clear purpose; protection via systems not intentions.
Outside-the-tunnel activities named specifically; 30-day review date set.

Part of deciqAI Knowledge Skills — open-source thinking skills that make rigor executable for AI agents. Built by deciqAI · https://deciqai.com · Contributions welcome — see the template at the repo root.