Two-status workload management: cutting busyness at the root

Executive overview

Knowledge workers feel frantic all day — emails, meetings, Slack — yet accomplish little. The cause isn't bad habits; it's a structural problem created by the front-office IT revolution: more tasks per person, and lower friction to assign work, creating runaway administrative overhead.

The fix isn't managing overhead better. It's having fewer active projects generating overhead in the first place.

Reduce the number of active projects and administrative overhead collapses proportionally — freeing time to actually finish things.

Why digital knowledge work became deranging

• Pre-IT revolution: roles were specialised; executives didn't type, book travel, or build slides
• Personal computers made everyone capable of everything — so organisations fired support staff and loaded the remainder
• Digital networks eliminated the social friction of assigning work: send a message, offload a problem in seven seconds
• Each commitment brings administrative overhead: emails, check-ins, meetings — all day-fragmenting
• Result: days consumed by collaboration overhead, with no time left to do the actual work

The two-status workload system

• Every project you've agreed to gets one of two labels: active or waiting
• Active projects generate overhead freely — meetings, emails, check-ins are fine
• Waiting projects generate no overhead; they queue for their turn
• When an active project finishes, pull the next item from the waiting list
• Collapse from 10 active projects to 3 and overhead drops by a factor of three or more
• Treat-the-symptom fixes (email batching, meeting-free days) don't work because overhead is still needed — reducing project count does

Implementing it as an individual

• Use a shared Trello board with three columns: Active, Waiting queue (ordered), Back burner
• The queue is explicit and visible — stakeholders can watch their project advance
• Attach all files, notes, and updates to the relevant card so nothing gets lost
• Notify people the moment their project moves to active: signal you're all-in
• The real problem you solve for colleagues isn't fast email replies — it's "my thing won't be forgotten"
• Soft-commit to new requests by adding them to the queue; reprioritise later when less pressured
• Regularly reorder the queue with stakeholders; items that keep getting bumped reveal they weren't important
• De-accession: move stale items to back burner, then off the list entirely

Implementing it as a team

• Maintain a shared wall (physical or virtual) with a column for "ideas/backlog" and a column per team member
• Each person's column shows what they're actively working on — one to three items maximum
• Hold a short structured check-in every one to two days: review status, unblock dependencies, assign next items
• Log decisions and commitments at each meeting so nothing slips
• Items that keep getting bypassed in prioritisation reveal themselves naturally; remove them
• This is a knowledge-work adaptation of Kanban-style agile methodology

Productivity systems: what they can and can't do

• Systems serve two purposes only: help you make consistent decisions about what to work on, and reduce unnecessary drains on time and attention
• Going from no system to a basic system is the large gain; optimising beyond that yields diminishing returns
• Review and prune quarterly — don't over-engineer, don't abandon; just trim what isn't working
• Systems cannot do the work; concentrated cognitive effort on hard problems still feels hard regardless of system

Managing a full calendar as a director or manager

• Replace scattered meetings with structured office hours: 30–60 minutes of open drop-in time each afternoon
• Add bookable 15–30 minute slots for issues needing more than five minutes
• Reserve simple questions for asynchronous messaging; complex ones for booked slots
• Require a written briefing before any scheduled meeting (Jeff Bezos two-page memo model)
• Consolidating interactions to a defined window frees mornings for deep thinking and strategy work

Protecting the start of the day

• Prepare at shutdown the day before: review the next day's plan, gather materials, close open loops
• Block the first 90 minutes like a meeting — go to a different location if needed
• Process meetings immediately after they finish: capture decisions, action items, follow-ups before moving on
• Schedule prep and processing time alongside each meeting, not during the morning block

Small business workload for predictable work

• Simple client folders or Trello boards suffice — avoid over-engineering with Notion or Airtable when data isn't complex
• Run a weekly two-hour planning session to review all clients and set the week's schedule
• Use autopilot scheduling for recurring work: fixed time blocks for monthly filings, client calls, recurring tasks
• Consolidating like work with like work surfaces opportunities for efficiency improvements over time

Immersive single-tasking and virtual environments

• VR and mixed-reality workspaces (Apple Vision Pro, Quest 3) are approaching viability for focused work
• Resolution problems are solved; hand-tracking and keyboard passthrough are now close to seamless
• The commercial driver is virtual multi-monitor setups, not focus per se — but focus benefits may follow
• Whether immersive environments genuinely improve cognitive output remains to be tested at scale

Books read in March 2024

• A Short History of England — Simon Jenkins: England's messy history produced a self-regulating tension between crown and people that proved more durable than cleaner European alternatives
• Into the Impossible — Brian Keating: interviews with seven Nobel Prize-winning physicists; a format more fields should adopt
• The Amen Effect — Sharon Braus: theology of communal presence and shared suffering; powerful but weighted heavily toward tragedy as its primary example
• Sink the Bismarck — C.S. Forester: less cohesive than The Good Shepherd; useful contrast that elevated appreciation of the earlier book
• Hidden Potential — Adam Grant: classic Grant format — research-backed, story-driven, applicable; Grant has claimed the accessible social-science niche decisively