Shedding Obsolete Elements

Definition

One core mechanism for simplification is the "shedding" process: systematically examining every element in a system or process and asking whether it truly needs to be there. Things persist in systems long after their original purpose has expired—procedures, rules, even design elements—simply because nobody has formally challenged them. Shedding is the deliberate practice of identifying and discarding what is no longer essential.

In the Book

De Bono contrasts shedding with "provocative amputation." In shedding, you examine an element to determine if it is genuinely necessary; if not, you discard it. The book gives a real example: India's departure procedure once required paying a departure tax in local currency, then passport control, then a customs stamp. De Bono asks: "Why?" He observes that "in many cases procedures that were established many years ago, possibly for very good reasons, continue because no one has thought of changing them."

Rule 5 formalizes this: "You need to challenge and discard existing elements. Everything needs to be challenged. Everything needs to justify its continued existence." He notes that London taxi-cabs must reportedly be high enough to allow passengers to wear top hats—a requirement from horse-drawn days—and they must carry a bundle of hay. "Usually there is no inbuilt mechanism to kill laws when they have outlasted their usefulness. Perhaps every law should be allocated a lifespan at birth."

The book also points to the asymmetry in systems: we add features, regulations, and elements readily, but we rarely remove them. This is why "things evolve to become ever more complex—not more simple."

Why It Matters

This concept reveals that complexity is often inherited deadweight rather than necessary. Across law, software, bureaucracy, and product design, systems accumulate legacy constraints that no one has ever formally questioned. By treating shedding as a systematic discipline, you surface hidden efficiency gains and opportunities. It also explains why redesign from scratch is sometimes simpler than incremental modification: you are not bound by historical accretion and the inertia of "that's how we do it."