Eliminate

Ask: what could be removed, simplified, or reduced without losing what makes this valuable?

Why it works

Complexity accumulates by default — features, steps, and rules are added but rarely removed. Systematic elimination asks which elements are actually load-bearing versus which are legacy, convenience, or habit. The tension between what to keep and what to remove forces clear thinking about what actually creates value, which is often clarifying in ways that addition prompts are not.

How to do it

1. List every element of your product, process, or argument.
2. For each, ask: "What is actually lost if this is removed? Can the loss be tolerated or addressed another way?"
3. Distinguish elements that are essential from elements that feel essential because they are familiar.
4. Try eliminating two to three elements and observe what the remaining structure reveals.

Evidence

Research on cognitive load and user experience consistently finds that removing elements often improves comprehension, usability, and appeal — contradicting the intuition that more features equal more value. Simplicity as a creative strategy is well-supported in design research. (observational)

Elimination can remove essential scaffolding that users or processes depend on; the judgment of what is truly eliminable versus what only appears eliminable requires understanding of the whole system.

Common mistake

Eliminating the visible complexity (surface features) while leaving the underlying complexity intact — which reduces apparent simplicity without producing the cognitive clarity that actual simplification would provide.