Active List and Ordered Queue
Expose workload and cap active work before accepting more
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 98%
The Active List and Ordered Queue makes workload visible to everyone who creates it. A shared document separates a small active list from an ordered queue of work waiting to begin. New requests go into the queue instead of instantly becoming active, so they do not generate meetings, updates, and messages before work starts. Requesters can see when their item is likely to move and decide whether it is still worth adding. If a manager needs something immediately, the conversation changes from an abstract demand to a concrete tradeoff: they must choose which active item moves out. The mechanism reduces Newport's “overhead tax,” protects concentration, and replaces reflexive yes-or-no decisions with a transparent capacity system.
Origin
Extracted from Modern Wisdom. Newport presented a shared active list and ordered queue as a direct workload-transparency tactic used by real teams.
Core principles
- 01Every accepted commitment creates administrative overhead
- 02Active work must be separated from waiting work
- 03A visible queue makes expectations realistic
- 04Urgency requires an explicit tradeoff
How to run it
- 1
Expose the workload
Create one shared document that colleagues and managers can inspect. Use it as the authoritative view of current and future commitments.
Pro tip Keep the system simple enough that others will actually look at it.
Watch out A private list does not make workload transparent to requesters.
- 2
Cap active work
Place only a few items in the active section. Newport's example uses three active commitments.
Pro tip Treat active status as a promise that real execution is underway.
Watch out Do not label the entire backlog active.
- 3
Order the queue
Put waiting work below a clear dividing line in the sequence it will be started. Include any information needed when each item becomes active.
Pro tip Let requesters monitor movement through the queue instead of asking for updates.
Watch out An unordered backlog does not set realistic expectations.
- 4
Route every request
Invite the requester to add new work to the queue. Do not let a conversational yes silently activate it.
Pro tip The visible delay may prompt the requester to withdraw low-value work themselves.
Watch out Accepting work outside the system recreates hidden overload.
- 5
Force explicit reprioritization
When a boss declares a new item urgent, ask which existing item should move. Notify the affected owner of the tradeoff.
Pro tip Keep the decision with the person changing the priority.
Watch out Do not absorb every urgent request by extending your day.
In the wild
An employee has three active projects and fifteen queued requests in a shared document. A manager asks for a report immediately. Instead of quietly adding a fourth active project, the employee asks the manager which current item should move and who should be told about the delay.
→ The priority changes transparently without creating an invisible extra commitment.
Common mistakes
Using the queue as a dumping ground
A queue only calibrates expectations when it is ordered and regularly advanced.
Allowing side-door commitments
Work accepted in chats or meetings without entering the queue restores the overload the system is meant to prevent.
Is it for you?
Best for
It is best for people who receive work from colleagues or managers and struggle to make their true capacity visible.
Not ideal for
It is not ideal for genuinely interrupt-driven emergency roles where priorities cannot wait in a stable queue.
From the transcript
“everything you say yes to generates overhead tax”
“here's what I'm actively working on right now and you should have like three things under there”
“great tell me which one to move”
From the episode
The Delicate Art Of Mastering Work-Life Balance - Cal Newport - #764
Cal Newport