Base120 · Inversion
Subtractive Thinking
Improve systems by removing elements rather than adding complexity
When to use
"Use when a system feels bloated or complex. Before adding a feature, process, or layer, ask what could be removed to achieve the same goal. Addition is the default reflex; subtraction requires deliberate effort."
Example
"A product team is asked to add a notifications panel to reduce user confusion. Subtractive thinking asks — what existing UI element is causing the confusion? Removing the redundant sidebar eliminates the confusion without adding anything."
Common misuse
"Subtracting without understanding why the element was added in the first place. Some complexity exists for a reason; removing it without tracing its purpose creates regressions that surface later."