Adjacency is the only spatial rule.
Who This Matters To (And Why)
Critical: Architect (adjacency is the spatial constraint that produces the floor plan), Developer (adjacency requirements determine building configuration and efficiency), GC (adjacency-driven layouts affect trade sequencing and coordination).
Important: Engineer (MEP systems respect adjacency requirements for wet walls, mechanical rooms, and plenum zones), Banker (building configurations that optimize adjacency tend to be more efficient and more financeable).
Context: Broker, City, Investor.
Highest typology impact: Multifamily, Office, Hotel. Lower impact: Industrial (minimal adjacency complexity).
Adjacency is the only spatial rule because all other design constraints — circulation, structure, systems — are consequences of adjacency requirements. Get the adjacency diagram right and most other problems become tractable.
How It Shapes Development
An adjacency diagram is a graph where nodes are rooms and edges are relationships between rooms. Solid edges mean rooms must be adjacent. Dashed edges mean rooms should be adjacent. An X means rooms must be separated. This simple structure encodes almost everything that matters about a building's organization. The floor plan is an attempt to embed this graph in two-dimensional space with additional constraints (structural grid, egress, code) applied.
In multifamily design, adjacency requirements are largely fixed by unit type conventions. The bedroom must be adjacent to the bathroom. The kitchen must be adjacent to the living area. The utility space must be accessible from the unit interior. The entry must provide access to all spaces without requiring passage through the bedroom. These conventions are encoded in market expectations and code requirements simultaneously. A unit that violates them is unmarketable and possibly non-compliant.
Mixed-use adjacency is more complex and more consequential. Placing a parking garage adjacent to residential units requires acoustic mitigation. Placing a restaurant kitchen adjacent to residential units requires exhaust isolation and structural vibration control. Placing retail at ground level adjacent to residential above requires fire separation and often code-compliant separation assemblies. Each adjacency decision in a mixed-use building generates cost implications that compound as the building grows taller.
Wet wall adjacency is the mechanical engineer's version of the spatial rule. Plumbing requires wet walls — walls containing supply, waste, and vent pipes — and those walls must align vertically across floors to allow continuous pipe routing. In multifamily design, stacking bathrooms and kitchens directly above each other minimizes plumbing cost by minimizing the length of horizontal drain runs. Unstacked plumbing — where bathrooms on upper floors are offset from bathrooms below — requires longer horizontal runs, additional cleanouts, and typically more coordination and cost. The adjacency rule extends vertically.
The adjacency matrix is the design tool that most architects learn but few use systematically. Filling in an adjacency matrix before beginning schematic design — assigning every room pair a required, preferred, neutral, or avoid relationship — produces a bubble diagram that is algorithmically derivable from the matrix. This process converts program analysis into spatial analysis in a structured way. Algorithms that solve adjacency matrices to produce optimal floor plan configurations exist in research software. They don't exist in commercial design tools because the commercial tools don't represent rooms as first-class objects with adjacency properties.
Quick Wins: Connect This Applet To
- Applet #26 (Rooms Are the Only Primitive): Adjacency matrix input. User fills in adjacency requirements for a simple program (bedroom, bathroom, kitchen, living). Applet outputs a bubble diagram. One matrix, one diagram.
- Applet #47 (Plans Are Just Adjacency Made Visible): Direct pair. Show how satisfying adjacency requirements produces a recognizable floor plan. Toggle adjacency constraints, watch layout update.
- Applet #33 (Doors Are Edges in a Graph): Door requirement from adjacency. Show that wherever two rooms are adjacent, a door may be required. Input two adjacent rooms, output door type requirement from code.
For Other Professions (24-Hour Builds)
- Engineer: Add MEP adjacency analysis. Show which room adjacency pairs create the most MEP coordination complexity (restaurant-over-residential, parking-adjacent-to-units). Static priority list, one cost flag per pairing.
- Developer: Add adjacency-to-cost calculator. Show how each “must separate” adjacency requirement adds cost through fire separation, acoustic mitigation, or structural isolation. One constraint count input, one cost estimate output.