How Buildings Learn: What Happens After They're Built
Source: https://www.penguinrandomhouse.com/books/320919/how-buildings-learn-by-stewart-brand/ ↗
Brand's argument is that buildings are not static objects but processes that adapt over time, and that the best buildings are those designed to accommodate change rather than resist it.
His "shearing layers" model — site, structure, skin, services, space plan, stuff — each changing at a different rate, became one of the most productive metaphors in software architecture, adopted by people who never read the original.
The book is filled with before-and-after photographs spanning decades, showing how buildings actually evolve through use, and Brand is merciless about architectural vanity that sacrifices adaptability for appearance.
Not a technology book, but essential reading for anyone who builds systems intended to last.
The core insight — that the forces of change operate at different speeds and the design must respect all of them — applies to any complex artifact.
Central argument
Brand argues that buildings are not finished objects at the moment of construction but ongoing processes of adaptation, and that architectural success should be measured by how well a structure accommodates change over time rather than how resolved it looks at completion. His central analytical tool is the 'shearing layers' model, which identifies six layers of a building — site, structure, skin, services, space plan, stuff — each operating on a different timescale, from centuries to days. The key thesis is that design failures occur when faster-changing layers are locked to slower ones, and that the best-designed buildings anticipate and respect these differential rates of change rather than imposing a static vision that use will inevitably defeat.
Critique
Brand's model is built almost entirely on residential and civic buildings in wealthy Western contexts, which raises questions about how well the shearing layers framework generalizes to building typologies — and by extension, to systems — where economic pressures or deliberate obsolescence make long-term adaptability structurally irrelevant from the outset. There is also a tension in the argument between celebrating organic, user-driven adaptation and implying that designers could and should plan for it: if the most adaptive buildings are often the ones least controlled by their architects, it is unclear how much prescriptive design guidance the framework actually yields. The book's optimism about vernacular and incremental change can underplay the genuine cases where accumulated adaptation produces dysfunction rather than fitness.
Why it matters for product
The shearing layers model maps with uncomfortable precision onto the organizational and technical decisions a CPO makes daily: coupling product strategy cycles to engineering infrastructure cycles — or worse, to organizational restructuring cycles — is precisely the mistake Brand documents in buildings that fail to age well. A product leader who internalizes this framework will resist the impulse to unify layers that must move at different speeds, defending, for instance, the right of the space plan layer (team topology, squad missions) to change independently of the structure layer (platform architecture) or the skin layer (brand and surface design). The deeper provocation is Brand's finding that architectural vanity — prioritizing coherence of appearance over fitness for use — is a primary driver of fragility, which translates directly into the product tendency to over-specify roadmaps or design systems in ways that make them brittle precisely because they look finished.