Energy-Context Task Queues
Pre-sort tasks for tired, sick, or constrained moments
- Difficulty
- Starter
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 97%
Maintain separate task queues for recurring states or contexts in which normal work is difficult. Wolfram saves informational organizing and deferred videos for times when he is tired or sick, and keeps a call-while-driving list for conversations that do not require a computer. When the state arrives, he does not need to decide from his entire workload; he selects a task already matched to the available energy, tools, and attention. The constraint also creates a specific occasion for work that would otherwise be postponed indefinitely. Build queues around states you genuinely encounter, define what is safe and feasible in each, and review them so stale items do not accumulate. The method is not about filling every idle moment, but about making constrained time useful when you choose to work.
Origin
Wolfram described keeping tasks for tired or sick periods and a separate list of phone calls suitable for driving.
Core principles
- 01Different states support different kinds of useful work
- 02Preselected tasks remove decisions when capacity is limited
- 03Constraints can create a reliable occasion for neglected work
- 04A prepared queue can turn frustration into progress
How to run it
- 1
Name recurring contexts
Identify states such as tired, sick, traveling, waiting, or away from a computer that regularly limit what you can do.
Pro tip Use contexts that occur often enough to make a queue worthwhile.
- 2
Define safe task criteria
For each context, specify the acceptable energy, tools, attention, and safety requirements.
Watch out Do not assign tasks that create distraction or risk while driving.
- 3
Build the queues
Move suitable deferred tasks into the matching list before the constrained state occurs.
Pro tip Favor tasks that matter but rarely win against deep work in normal conditions.
Watch out Do not use the queues as a dumping ground for work you should delete.
- 4
Select within the constraint
When the context appears and you choose to work, pick from its prepared queue instead of reviewing everything.
Pro tip Choose the smallest useful item when energy is especially low.
- 5
Refresh the lists
Remove completed and obsolete items, then add new tasks whose requirements match each context.
Watch out A stale queue adds friction at the moment it is supposed to remove it.
In the wild
Wolfram saves informational organizing and videos he has meant to watch for periods when illness makes normal work less suitable. The queue gives him a prepared set of feasible tasks rather than leaving him focused only on being sick.
→ Low-capacity periods can advance deferred work without demanding peak performance.
Wolfram keeps a list of phone calls that need to happen sometime but do not require him to sit at a computer. Driving creates a bounded occasion in which those otherwise postponed interactions can occur.
→ A recurring constraint becomes a reliable trigger for appropriate calls.
Common mistakes
Matching the wrong task
A task that exceeds the available energy, attention, tools, or safety limits defeats the method.
Optimizing every idle moment
The queue should support useful choices, not eliminate needed rest or turn all downtime into work.
Keeping zombie tasks
Repeatedly skipped items may no longer matter and should be removed rather than recycled forever.
Is it for you?
Best for
People with recurring low-energy periods, travel time, waiting time, or contexts where their normal tools are unavailable.
Not ideal for
Tasks requiring deep concentration, sensitive decisions, or unsafe divided attention while driving.
From the transcript
“I tend to organize it so that there are things that I save up for. I'm going to do this if I'm feeling tired, or…”
“One of the things I found that, for me, it's keep the list of things to do when I'm tired because, for me, in terms…”
“I always maintain a call-while-driving list of phone calls that are slightly more, "I've got to do this sometime. I don't need to be in…”
From the episode
#637: Stephen Wolfram — Personal Productivity Systems, Richard Feynman Stories, Computational Thinking as a Superpower, Perceiving a Branching Universe, and The Ruliad... The Biggest Object in Metascience
Stephen Wolfram