Shearing Layers
Stewart Brand’s framework for how things change at different rates within the same system — and why conflicts between layers cause damage.
The Idea
In How Buildings Learn (1994), Stewart Brand, extending architect Frank Duffy’s idea of shearing layers, observed that a building is not one thing but six things, each changing on its own timescale:
- Site — the land itself. Geological timescale, centuries.
- Structure — the load-bearing bones. Decades to centuries.
- Skin — the exterior envelope. Decades.
- Services — wiring, plumbing, HVAC. 7–15 years before replacement.
- Space Plan — interior walls, layout. Years to decades.
- Stuff — furniture, equipment, personal belongings. Days to months.
The trouble comes when fast layers get locked to slow layers. An architect who pours the wiring inside concrete walls has made Services as hard to change as Structure. When the HVAC needs replacing in twelve years, the building has to be partially demolished. The architect has imposed their timescale on a layer that wanted to move faster.
What It Teaches
The practical principle: design so that fast layers can change without disturbing slow layers. Services should be accessible. Space plans should not require structural permits to modify. Stuff should be movable by one person.
This principle transfers directly out of architecture. Software has shearing layers: data schema is slow, business logic is medium, UI is fast. Infrastructure has them: hardware lifespan is long, OS configuration is medium, application code is fast. An organization has them: culture is slow, processes are medium, individual projects are fast.
Problems reliably occur at layer mismatch: building a startup culture around individual heroics (fast layer) into founding documents (slow layer). Embedding application logic in SQL triggers (slow layer) because it seemed convenient. Writing DNS records into applications instead of config files.
The Tension
Shearing layers is descriptive more than prescriptive. It helps you see where layers are stuck, but identifying the problem doesn’t automatically produce the solution. Some layer conflicts are genuinely hard to resolve — the wiring is already in the walls, and the cost of fixing it may exceed the cost of working around it. The framework is a diagnostic, not a cure.
There’s also a risk of over-separating. Sometimes layers should be tightly integrated because the coupling provides value. The question is always: is this coupling load-bearing, or is it accidental?
Connections
- Stewart Brand — the concept’s origin
- how-buildings-learn — where it was first articulated
- Christopher Alexander — pattern languages as slow-layer design
- appropriate-technology — technology chosen for its layer’s timescale
- selective-technology — knowing which layer a technology belongs to
- repair-culture — maintenance is shearing layers in practice
Further Reading
- Brand, Stewart. How Buildings Learn (1994)
- Brand, Stewart. The Clock of the Long Now (1999) — the longest shearing layer applied to civilization