Opening Adjacency Lab…

Adjacency Lab is taking longer than expected to open.

Check your connection and try again, or get help.

How bubble diagrams and adjacency matrices actually work?

Adjacency Lab, , Space planning

Two ways of recording the same decisions, with different failure modes. One is easy to read and easy to fool. The other is exhaustive and nobody enjoys it.

Every architecture student draws a bubble diagram. Most are taught it as a warm-up: a loose sketch you make before the real drawing starts, somewhere between a mind map and a plan. That framing is why so many of them are useless by week three.

A bubble diagram is not an early plan. It is a record of decisions about relationships, and it is worth exactly as much as the rigour behind those decisions.

Where they came from

Both notations come out of the same mid-century effort to make architectural programming systematic rather than intuitive. The period produced a body of work now loosely called design methods, and its central question was whether the allocation of spaces in a building could be reasoned about explicitly instead of being left to the designer's instinct.

The bubble diagram survived because it is legible. The adjacency matrix survived because it is complete. Neither replaced the other, and the reason is worth understanding before you use either.

What a bubble diagram is good at

A circle for each space, sized by area, with lines between the ones that relate. Its strength is that a person can look at it and understand a building programme in about ten seconds. Nothing else in the early stage does that.

It is good at:

  • Showing clusters. Departments emerge visually. You can see that four

spaces belong together before anyone labels them a department.

  • Showing proportion. When bubbles are sized by real area, an oversized

circulation allowance is obvious in a way a spreadsheet column never is.

  • Being argued over. People who cannot read a floor plan can point at a

bubble diagram in a meeting. That matters more than architects usually admit.

What it is bad at

It lets you leave things undecided. This is the important one. If you do not draw a line between two spaces, you have not decided they are unrelated. You have simply not thought about them. The diagram looks equally finished either way.

For a programme of forty spaces there are 780 possible pairs. A busy diagram might show sixty lines. The other 720 pairs are not decisions, they are silence, and silence and "no relationship required" look identical on paper.

It flattens different kinds of relationship. A line usually means "these relate". But "must share a door" and "would be convenient" are not the same claim, and when the site gets tight you need to know which lines you can cut. Most hand-drawn diagrams cannot tell you.

It drifts from the numbers. The bubble is sized by area at the moment you draw it. Change the area later and the drawing lies.

What a matrix is good at

Put every space along both axes. Every pair now meets in exactly one cell, and the cell has to say something.

That is the whole idea, and it fixes the bubble diagram's worst failure: you cannot leave a pair undecided, because the cell is visibly empty. An empty matrix cell is a question you have not answered. An absent diagram line is nothing at all.

It is also good at:

  • Recording strength, not just existence. A cell can hold "required",

"undesirable", "prohibited", or a weight, and those distinctions survive into the decisions that come later.

  • Catching the pairs you would never have drawn. The clean store and the

dirty utility are usually nowhere near each other on a bubble diagram, so no line gets drawn, so the separation never gets recorded as a requirement. In a matrix, that pair has a cell like every other.

  • Being checkable by someone else. A reviewer can read a matrix for

completeness. Reading a bubble diagram for completeness is close to impossible.

What a matrix is bad at

It is tedious, and the tedium scales badly. Pairs grow as n(n-1)/2, so:

Spaces, Pairs to decide

10, 45

20, 190

40, 780

60, 1,770

Forty spaces is an ordinary mid-sized building. 780 decisions, by hand, is why most matrices get started and abandoned.

It is hard to read spatially. A matrix will tell you that A must be near B and B must be near C and A must be away from C. It will not tell you that you have just described something impossible. The diagram shows you that in a glance.

Use both, in this order

They are not alternatives. They are the same information with opposite strengths, which is why the sensible workflow uses each for what it is good at.

  1. Write the programme first. Names, areas, departments. The diagram is not

a substitute for knowing what rooms the building has.

  1. Fill the matrix second. It is the boring step and the one that produces

the decisions. Do it while the programme is small enough that the pair count is survivable.

  1. Read the diagram third. Let the relationships you just committed to

arrange themselves, then look for what is impossible or absurd.

  1. Go back. Something in step three will change something in step two. That

loop is the work.

The order matters because it puts the exhaustive step before the legible one. Draw the diagram first and the matrix becomes a transcription exercise that agrees with whatever you already drew, which tells you nothing.

The thing to check

Whichever notation you use, ask one question of the finished artefact: can you point at any relationship and say which kind it is?

Required, forbidden, or merely convenient. If the answer is "it is a line", the diagram will not help you when the site shrinks by fifteen per cent and something has to give. If the answer is specific, you already know what to give up, which is the only reason to have drawn it.

All articles