5.2 Programming: Programmatic Diagrams

Why Diagrams Come After the Program

The program is text and numbers. Programmatic diagrams translate that text into visual relationships before any design is drawn. They are analytical, not schematic — they show what must be true, not what the design will look like. Diagrams let the designer and client test the program, expose conflicts (two required adjacencies that are mutually exclusive), and communicate the organizing logic to stakeholders. Five diagram types appear on the NCIDQ IDFX, each used at a different moment in the process.

The Adjacency Matrix

An adjacency matrix (also called a relationship matrix) rates every pair of spaces against a relationship scale. The most common scale:

Build the matrix by listing every program space along both the top row and the left column. Each cell holds the rating for that pair. Some matrices add a numeric weight (1–4) so the ratings can be summed into a score. Reading a completed matrix tells the designer the most-connected space — the one with the most ● marks — which is often the workroom or copy center and should be placed centrally. A matrix can also expose a fatal conflict: if space A must be adjacent to the exterior wall (for daylight) and space B must also be adjacent to the exterior wall but must be separated from A, no single-floor solution exists and the program must change.

Bubble Diagrams

A bubble diagram turns the matrix into a picture. Each program space becomes a circle (bubble) sized in proportion to its area — a 2,000 sf open office is a large bubble, a 100 sf storage room is a small one. Lines between bubbles show relationships, often using the same symbols (● for required, ○ for desirable). Bubble diagrams are quick, hand-drawn, and exploratory: designers generate several alternatives to test organizations without committing to a layout. They are intentionally loose so the client can understand the logic at a glance and participate in choosing a direction.

Block Diagrams

A block diagram is the next refinement. It replaces circles with scaled rectangles drawn inside the actual building shell — the partition outline, core, and column lines are shown. Each rectangle is labeled with the space name and area. Block diagrams:

• Test whether the program actually fits within the available floor plate
• Show circulation corridors as connecting bars
• Begin to establish orientation (which spaces get windows)

A block diagram is the bridge between program analysis and schematic design. If the blocks do not fit, the program is over-allocated relative to the shell and the designer returns to the client before proceeding.

Parti Diagrams

The parti is the organizing concept — the big idea in a single sketch. It might be an axis, a center, a courtyard, a spine, a grid, or a progression. The parti is drawn before the plan is detailed and is referenced throughout the project to keep the design coherent. A project may have a parti such as "a central daylit atrium with wings radiating outward" that originated in the bubble diagram and is realized in the block diagram. The parti is the one diagram the designer pins above the studio table for the duration of the project.

Stacking Diagrams

A stacking diagram distributes program areas across multiple floors of a building. Each floor is a horizontal band; each program space is a block sized by area. Stacking diagrams answer:

• Which functions belong on the ground floor (lobby, retail, loading)
• Which functions need the top floor (executive suite, mechanical, outdoor terrace)
• Which functions can repeat on multiple floors (typical office floors)
• Where vertical circulation (elevators and stairs) should land

Stacking is produced early in multi-floor projects and is often iterated as the program is refined.

When Each Diagram Is Used

Exam Scenario

A 12-space office project has a completed adjacency matrix showing the break room has four ● marks (required adjacency to lobby, restrooms, kitchenette, and open office) — the most of any space. The bubble diagram places the break room centrally. The block diagram tests whether that central location fits the floor plate's core location; if the building core occupies the center, the break room must shift and the diagram is redrawn. This iteration catches the conflict before the design is drawn — the entire purpose of programmatic diagrams.