Simplification by Elimination
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
A design and thinking practice of stripping away elements that do not contribute to the goal. It is related to Occam's razor but broader, applying to products, processes, writing, and organizations. The key qualification is that the hard part is discrimination rather than deletion: the practitioner must separate essential complexity, which arises from the problem itself, from accidental complexity, which arises from how the solution was built. Deleting the latter improves clarity and lowers cost; deleting the former breaks the solution.
SCAFFOLDING EFFECT
Reduce cognitive load
- Element inventory: list every element and step in the current design before touching any of them. - Removal test: ask of each element what would break if it were deleted. - Merge check: look for elements that can be combined rather than removed.
Anchor fast decisions
Every element carries costs in cognition, maintenance, and coordination, and those costs are paid repeatedly while the element's benefit may be marginal. Removing accidental complexity therefore reduces ongoing cost without reducing function. The reason judgment is required is that complexity is often mistaken for sophistication, so teams add elements to signal effort and end up with a design that is harder to use and no more effective.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- zh.wikisource.orghttps://zh.wikisource.org/wiki/%E5%82%B3%E7%BF%92%E9%8C%84/%E5%8D%B7%E4%B8%8Averified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS