Christopher Alexander’s A Pattern Language, published in 1977 with Sara Ishikawa and Murray Silverstein, is one of the few architecture books that changed how people outside architecture think. It set out 253 numbered “patterns” for building, from the scale of a region down to the height of a windowsill, and argued that ordinary people could use them to shape their own surroundings.

It is worth reading for anyone planning a house, even if you take only a few ideas from it. Here is what the book actually proposes, and what we find useful in it.

What a pattern is

The book’s structure is the idea. Every pattern follows the same shape:

• A name, short enough to remember and say out loud.
• A context — the situation in which the pattern applies, referring back to larger patterns that contain it.
• A problem, stated plainly, usually in terms of what goes wrong when it is ignored.
• A solution, described in words and a sketch rather than as a fixed specification.
• Smaller patterns that the solution leads into.

So patterns nest. A pattern about where people live leads to patterns about how a neighbourhood is arranged, which lead to patterns about a house, which lead to patterns about rooms, doors and light. The point is that you move between scales rather than starting from a floor plan.

Why “language”

Alexander’s claim was that good environments come from combinations of well-understood solutions, used in sequence, the way words combine into sentences. A pattern on its own is not a design. Patterns used together, adapted to the place, become one.

That is a humbler position than the architect-as-genius model, and it was deliberately so. The book’s underlying argument is that people understand their own needs better than any professional, and that a shared language gives them something to design with rather than a style to imitate.

The patterns people remember

Different readers fix on different ones, but a few recur in conversation because they name something obvious that design often ignores:

• Light on two sides of every room. A room lit from one direction only feels like a corridor; light from two makes it a room.
• Window place. A seat built into a window, sized for one person, does more for how a room is used than most furniture does.
• Entrance transition. The need for a threshold between public street and private house, rather than a door that opens straight into a living room.
• Half-hidden garden. A garden you cannot see all of at once.
• Things from your life, and the wider argument that a home should carry evidence of the people in it rather than looking like a showroom.
• Sequence of sitting spaces, a recognition that households need several places to sit at different scales, from a corner for one to a table for a crowd.

Many of these now feel obvious because the book helped make them so.

Beyond architecture

The pattern idea escaped architecture entirely. Software engineers borrowed the structure — a named problem in a context, with a reusable solution — and it became a standard way of writing about programming practice. Few books shaped a field they were not written for as directly as this one.

What we take from it

Three things, mostly.

Name the problem before solving it. A pattern only works because it starts from what goes wrong. In our briefs we do the same: “the kitchen has no relationship to the garden” is a problem we can design against, where “we want an open plan” is a solution looking for a reason.

Work at more than one scale. A house decision that ignores the street, the block, the climate and the neighbourhood tends to be wrong in a way that is hard to fix later. Patterns nested by scale keep those in view.

The occupant is the authority on their own life. Our job is to translate how people actually live into drawings, not to impose a taste. The best results we have been part of came from clients who told us plainly what their days look like.

Where the book needs care

A Pattern Language is a product of its time, and it shows in places. Some patterns are culturally specific to the places its authors studied. Some of the social claims are optimistic, and the idea that anyone can design and build their own home sits awkwardly against contemporary planning approval, bushfire and energy requirements, and structural engineering.

It is also not a substitute for the site. No pattern will tell you that your block slopes, that your soil is reactive, that the west elevation will cook in summer, or that a beam cannot span where you want it to. Patterns describe situations; they do not survey one.

Read as a set of well-argued observations about how buildings work for people, it remains unusually useful. Read as a system to apply mechanically, it becomes a style, which is the opposite of what it argued for.

Reading it, or using it

You do not need to read all 253 patterns. The book is arranged as a reference and can be opened anywhere. Start with the ones about rooms and light, then follow the links wherever they lead.

If you are planning a project, tell us which patterns you have reacted to. It is a remarkably efficient way of explaining what you want, and it usually starts a better conversation than a folder of photographs. We work across the Perth metro area and regional Western Australia, and we are always happy to talk about the ideas behind a brief.