Cognitive Engineering & Self-Mastery — Part 4A: Attention Architecture for Complex Work

Track: Work Graphs · WIP Limits · Attention Gates · 4C Loop · Reviews · Context Switch Audits

Attention is your only non-renewable currency during the day. Architect where it flows or entropy will spend it for you.

1) The Work Graph (Route Attention, Don’t Chase Tasks)

Model your work as a simple graph:

• Nodes: Projects, Tasks, Routines, Standards, Parking Lot.
• Edges: Dependencies (A→B), Cadence (weekly, monthly), and Gates (definition of ready/done).
• Views: Today (focus), This Week (commitments), Season (themes).

2) WIP Limits (Keep the Lane Clear)

• Major initiatives: ≤ 3 active.
• Minor tracks: ≤ 5 active.
• Rule of One: one true priority per day; the rest support it.

3) Attention Gates (Permission to Start/Stop)

Before starting any block, pass two gates:

• Ready Gate: scope ≤ 90 minutes, first line written, assets available.
• Boundary Gate: timer set, notifications off, “First Line” visible.

Stop when one of these triggers fires: timer ends, quality dips twice, or dependency unmet.

4) The 4C Loop — Capture → Clarify → Compose → Calibrate

• Capture: inbox everything (notes, links, ideas) without judgement.
• Clarify: convert to next steps, attach to a node, add gate.
• Compose: build in peak blocks; protect via gates and WIP.
• Calibrate: review outcomes; re-route attention for tomorrow.

5) Context Switching Audit (Find the Leaks)

• Count switches/hour for one day. Aim ≤ 4/hr outside deep work, ≤ 1/hr during deep work.
• Batch communications into two windows; pre-write fast replies.
• Single-tab rule in peak blocks; new idea → capture, not click.

6) Deep Work Contracts (Make Focus Visible)

• Start ritual: breath ×1 min, First Line, 90-minute timer.
• No-novelty clause: no new tabs/apps; capture instead.
• Outcome receipt: export artifact link + 3-sentence summary.

7) Review Cadence (Daily → Weekly → Monthly)

• Daily (5 min): mark done, move blockers, pick One Thing.
• Weekly (30–45 min): WIP check, dependency fix, schedule peaks.
• Monthly (60–90 min): theme health, kill/continue/scale decisions.

8) Environment & Cues (Design the Room)

• Two modes only: build desk (clean, horizon gaze) and plan desk (calendar, boards).
• Soundtrack per project; scent as on/off switch; phone in another room.

Templates (Copy/Paste)

Work Graph Canvas

SEASON THEME: ______________________   MONTH: ___________
MAJOR (≤3): 1) ______  2) ______  3) ______
MINOR (≤5):  1) ______  2) ______  3) ______  4) ______  5) ______
DEPENDENCIES:
A → B: ____________   C → D: ____________
STANDARDS (quality gates): _____________________________
  

Attention Router (Today/Week)

ONE THING (7 words max): _______________________________
Peak 1 (90±20m): ________  Node: ______  Gate ready? Y/N
Peak 2 (90±20m): ________  Node: ______  Gate ready? Y/N
Comm Windows: __:__ and __:__  Batch list: ______________
Kill/Park candidates (WIP relief): ______________________
  

Deep Work Contract

Block: __:__–__:__   Location: ______   Distractions off? Y/N
First Line: ____________________________________________
Rules: single-tab · capture, don’t click · outcome receipt
Outcome (link): __________   Summary (3 lines): __________
  

Context Switch Log (1-Day Audit)

Hour → Switches:   09:00 ____   10:00 ____   11:00 ____   12:00 ____
Deep work hours (≤1/hr)? Y/N   Top triggers: ______________
Patch (batch/blocks/tool lock): __________________________
  

Weekly Review Script (30–45 min)

1) Score KPIs (below)   2) Reduce WIP   3) Fix dependencies
4) Schedule peaks   5) Choose One Thing for Mon/Tue
Kill/Continue/Scale decisions: __________________________
  

KPIs (Attention & Throughput)

• Deep work hours: ≥ 8–12/week
• Context switches during deep work: ≤ 1/hr
• WIP within limits (3 major / 5 minor)
• Daily 4C loop completed: ≥ 5/7 days
• Weekly review done: 4/4 weeks

Seven-Day Attention Sprint

1. D1: Draw your Work Graph; set WIP limits; pick One Thing.
2. D2: Run a context switch audit for 1 day; patch.
3. D3: Write three Deep Work Contracts; execute two.
4. D4: Build Attention Router for the rest of the week.
5. D5: Fix one dependency; kill or park one item.
6. D6: Weekly review; schedule next week’s peaks.
7. D7: Rest + monthly micro-review (30 min).

Free Execution Prompt — Attention Systems Architect (10-Year Proof)

You are my Attention Systems Architect (Part 4A).
Goal: build a Work Graph with WIP limits, attention gates, a 4C loop, and review cadence for complex work.

ASK FIRST:
1) List my current projects (major/minor) and any hard deadlines
2) My natural peak windows and weekly time constraints
3) Biggest blockers/dependencies in the last 14 days
4) Tools I already use (notes, tasks, calendar)
5) My “One Thing” for the next 48 hours

DO THIS:
1) Draft a Work Graph (projects, routines, standards) with Ready/Done gates and dependencies.
2) Propose WIP limits (≤3 major, ≤5 minor) and identify kill/park candidates.
3) Create an Attention Router plan for the next 7 days (two peak blocks/day + comm windows).
4) Write three Deep Work Contracts for my top nodes this week.
5) Design a 4C loop for daily execution (5–10 min) and a Weekly Review script (30–45 min).
6) Provide a 1-day Context Switch Log and patch recommendations.
7) Define KPIs (deep work hours, switches/hr, 4C adherence, review cadence).

OUTPUT / ARTIFACTS:
- Work Graph v0.x (text)
- WIP plan + kill/park list
- 7-day Attention Router
- 3 Deep Work Contracts
- Daily 4C loop + Weekly Review script
- Context Switch Log + patches
- KPI sheet with targets

EVIDENCE GRADING:
- High: ≥8 deep work hours/week; switches ≤1/hr in deep blocks; 4C ≥5/7; weekly review complete.
- Moderate: 6–7 deep hours; 4C 4/7.
- Low: below → reduce WIP, shorten blocks, move comms to windows, strengthen gates.

LINK-FORWARD:
Advance to Part 4B — Multiscale Planning: From Day Craft to Seasonal Strategy.
    

FAQ (Part 4A)

Next: Part 4B — Multiscale Planning: From Day Craft to Seasonal Strategy.

Apply It Now (5 minutes)

1. One action: What will you do in 5 minutes that reflects this essay? (write 1 sentence)
2. When & where: If it’s [time] at [place], I will [action].
3. Proof: Who will you show or tell? (name 1 person)

You are my Micro-Action Coach. Based on this essay’s theme, ask me:
1) My 5-minute action,
2) Exact time/place,
3) A friction check (what could stop me? give a tiny fix),
4) A 3-question nightly reflection.
Then generate a 3-day plan and a one-line identity cue I can repeat.

🧠 AI Processing Reality… Commit now, then come back tomorrow and log what changed.