Simplify by reducing commitments

Regularly eliminate projects, roles, and obligations that don’t align with your most important work.

Why it works

Productivity gains from better systems are capped by the volume of commitments they are asked to handle. Reducing that volume by eliminating non-essential projects removes work permanently rather than handling it more efficiently — the highest-leverage move in any overloaded system. Saying no is not a failure of ambition; it is the condition for doing fewer things well.

How to do it

1. List every project and ongoing obligation you currently carry.
2. For each, ask: does this align with my most important goals right now? Would stopping it meaningfully harm me or others?
3. Eliminate or hand off at least one thing that does not pass both tests.
4. Build a lightweight check before accepting new commitments: "Is this more important than what I’m dropping to make room for it?"

Evidence

Mechanistically grounded in resource constraint: time is finite, and work added without removing something else comes at the expense of existing commitments. Essentialism and related frameworks rest on this straightforward accounting principle rather than a studied intervention. (mechanistic)

For people in early career or constrained roles, the option to decline commitments may be limited; the practice is most actionable for those with some autonomy over their portfolio.

Common mistake

Accumulating a "someday" category of commitments you intend to eventually do rather than making honest cuts — so the system is tidier but the underlying overcommitment is unchanged.