Keep a simple, few-list system

Use the fewest lists possible — one inbox, a few context lists, and nothing elaborate.

Why it works

Complex productivity systems generate their own maintenance overhead — time spent organizing, tagging, and refiling that was meant to be spent doing. A minimal system (one inbox to clear, a short next-action list, and a someday list) has enough structure to keep open loops off the mind without becoming a project in itself. Simplicity keeps the system trustworthy because it is sustainable to maintain.

How to do it

1. Reduce your task infrastructure to its minimum: one inbox, one daily action list, one someday list.
2. Resist adding new categories, labels, or tools unless a genuine problem demands them.
3. Use a regular (weekly) review to keep each list current and short.
4. If the system takes more than a few minutes a day to maintain, simplify further.

Evidence

Mechanistically consistent with cognitive-load theory: the mental effort required to maintain a complex filing system reduces the resources available for the actual work. Simpler systems are also more likely to be used consistently, which is the variable that matters most. Sweller’s foundational work established that extraneous load — effort spent on how information is organized rather than on the task itself — directly competes with the working-memory capacity available for the real work, the exact tax an over-built system imposes. (mechanistic)

Optimal system complexity is individual; roles with very high task volume may genuinely need more structure than minimalism allows.

Sources

• Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science, 12(2), 257–285.

Common mistake

Spending more time designing and reorganizing the productivity system than actually completing work — "productivity porn" in which the tool becomes the task.