The reading room · Digna Legi
The Subtraction Instinct
/100
80–100: high value. 70–79: worth the time. Below 70: below the usual publication threshold.
Evidence-reviewed score based on available publisher text. Evidence supports the article’s synthesis, though the underlying studies and case statistics are not independently checked here.
Scores reflect one reader’s profile, not an objective quality rating. Best is a separate personal selection.
How scoring works →This brief · about 3 min with detail
Why read this
Subtraction often fails to occur to people, then organizations reward visible additions while making removal look like absence.
AI brief · Checked against source text
The main idea
The central claim is that people and organizations often try to improve things by adding, while failing to consider removal at all. The mechanism is partly cognitive: subtractive options do not reliably come to mind unless prompted, especially under mental load. Organizations then amplify that bias because additions are visible, ownable, measurable, and career-enhancing, while cancellations, simplifications, and refusals often look like absence rather than work.
Go a little deeper
Subtraction fails before evaluation
The key distinction is not that people compare adding and removing, then rationally choose addition. The stronger claim is that removal often never enters the candidate set. That matters because persuasion alone is too late; the intervention has to happen at search time, by making people generate subtractive options before additive ideas dominate the frame.
Organizations turn bias into accumulation
A workplace does not merely inherit individual cognitive bias; it rewards the additive version of it. New programs get names, sponsors, meetings, staffing, and promotion evidence. Removed steps, declined features, and cancelled meetings leave weaker traces. The result is an institutional ratchet: many small, sensible-seeming improvements accumulate into complexity because almost nothing gives removal equal status.
Metrics can punish the best simplifiers
The Apple lines-of-code story shows a precise measurement failure: the metric was not merely incomplete, it classified an improvement as negative productivity. When a system only counts production as more visible stuff, it trains people to avoid simplification or hide it. The practical lesson is to audit what counts as contribution before demanding better judgment from contributors.
Prompting is a design tool
The hopeful part of the research is that subtraction is recoverable. Explicit reminders, practice rounds, and protected review rituals can change what people notice. The essay’s strongest advice is therefore procedural: put the stop-question first, pair additions with removals, reward deletion publicly, and schedule simplification before crisis pressure makes additive defaults stronger.
A case from the article
Seoul removes an expressway
Seoul’s Cheonggyecheon project is the essay’s clearest non-corporate case. Instead of treating traffic as a problem requiring more road capacity, the city demolished an elevated expressway and restored the stream beneath it, while investing in public transit. The example illustrates subtraction as redesign, not mere austerity: removing one structure made room for cooler streets, public space, and a different transport pattern.
How the case is made
The case is made through a reported research program, organizational observation, and historical examples from urban planning and technology.
Where the idea has limits
The essay’s leadership advice depends on making subtraction visible and habitual; simple deletion without replacement, sequencing, or complementary support is not presented as sufficient in every setting.
A question to take away · from Digna Legi
Where are your current measures treating useful removal as failure, inactivity, or negative output?
What the original adds
The original adds several concrete applications, including agenda design, one-for-one removal rules, recognition practices, and timing subtraction reviews for lower-pressure periods.
About this brief
AI-written, then separately checked for source support, useful detail and clarity. The author’s claims and our editorial question are kept separate. The original remains the author’s work. How we select and summarise →
How was this brief?
Rate this summary, separately from the author’s article.
Optional. Saved in this browser; shared only if you allow analytics.
How was the original article?
Rate the author’s original after reading it.
Optional. Saved in this browser; shared only if you allow analytics.
Digna legi. Worth reading.