Layers of Innovation: Exploring Architectural Change

The Daily Interesting — Art & Design Edition

February 9, 2026

The idea

“A building is not one thing. It is layers that change at different speeds: Site, Structure, Skin, Services, Space Plan, Stuff.” (from How Buildings Learn; often summarized as “shearing layers”) [barnsworthburning.net] (barnsworthburning.net)

Who said it (and the context)

Stewart Brand is an American writer, curator, and systems thinker best known for the Whole Earth Catalog and for stewarding long‑horizon projects at The Long Now Foundation. In his 1994 book and BBC series How Buildings Learn, he adapted architect Frank Duffy’s insight that buildings consist of parts with different life cycles and expanded it into six “shearing layers.” The model explains why adaptable designs outlast brittle ones and later inspired Brand’s broader “pace layers” for civilizations. (en.wikipedia.org)

A small expansion

If every artifact ages in parts, then design should locate change where it can happen safely and cheaply:

  • Protect the slow layers (the “Site” and “Structure”) from fads.
  • Expose the fast layers (“Space Plan,” “Stuff”) to everyday edits by users.
  • Keep the “Services” legible and reachable so upgrades don’t require demolition.
    Brand’s simple drawing is really a governance diagram: decisions live at different tempos. Good art direction, product systems, and buildings all improve when fast layers can dance without tripping the slow ones. (barnsworthburning.net)

Another lens on the idea

Dutch architect N. John Habraken proposed “Supports” (long‑lived base building) and “Infill” (user‑changeable parts) decades earlier. Where Brand maps time, Habraken maps control: who gets to change what. Together they suggest a durable principle for art and design systems—stabilize the frame, liberate the fill. (en.wikipedia.org)


Why this matters across art and design

  • Visual identity

    • Treat your core mark and name as “Structure,” but make color, motion, and layout “Stuff/Space Plan” that can shift by context. Create a style matrix that lists which elements may vary daily, quarterly, or never. This yields identities that feel alive without losing recognizability.
    • Practical hint: document “upgrade paths” for type scales and color systems so future tweaks don’t force a total rebrand. (barnsworthburning.net)
  • Product & UX

    • Architectural “Services” maps to design tokens, API schemas, and navigation models; “Space Plan” maps to page layouts; “Stuff” to copy and micro‑interactions. Keep tokens and information architecture accessible and well‑separated so surface experiments don’t crack the backend.
    • Use pace‑layer thinking in roadmaps: fast experiments in features; slower, deliberate cycles for platform changes. (resilientwebdesign.com)
  • Architecture

    • Detail the routes for future service changes—pull wires, chases, removable panels—so the building welcomes tomorrow’s tech without surgery.
    • Borrow from Habraken: define which elements the community controls (support) and which belong to occupants (infill). This preserves both coherence and participation. (habraken.com)
  • Studio art

    • In installations and modular works, separate the “support” (armature, rigging, base software) from “infill” (media, light, behaviors). You can then recompose the fast layer per venue while refining the slow layer over years—an artist’s version of learning buildings. (en.wikipedia.org)

Two quick drills

  1. Layer Ledger
  • Take a current project (brand system, app, exhibition). List its parts under these columns: Site, Structure, Skin, Services, Space Plan, Stuff.
  • For each, note: a) expected change tempo, b) who decides, c) how to access/replace it. If a fast layer is tightly coupled to a slow one, introduce a seam or interface.
  1. Infill Sprint
  • Freeze one “support” decision (grid, palette core, rigging). In 90 minutes, generate five “infill” variations that can swap in without touching the support. Ship or show one today; schedule the rest as seasonal refreshes.

Thread to remember

We’ve explored perception, thresholds, and behavior. Today is about time. Design for layers that move at different speeds, and you’ll make work that keeps learning without tearing itself apart.


Sources

  • Central idea: Stewart Brand’s shearing layers (via BarnsworthBurning). (barnsworthburning.net)
  • Background on Brand and How Buildings Learn. (en.wikipedia.org)
  • Origins and definitions of shearing/pace layers (Duffy → Brand) and broader applications. (en.wikipedia.org)
  • Another perspective: N. John Habraken’s Supports/Infill and open building. (en.wikipedia.org)

Further reading

Tip: Stabilize what must endure; make everything else easy to change.