Amogh N P
✦ In loving memory of Amogh N P — Architect · Designer · Visionary ✦
Students on a site visit — surveying and sketching the plot.
Lesson III25ARS121 · Architectural Design I

The Brief, Site & Programme

Understand the problem before you draw the answer.

≈ 35 min

The temptation is to start drawing. Resist it. The best schemes come from designers who first understood the problem — the brief, the people, the site. As Peña & Parshall put it, “programming is problem seeking; design is problem solving.”

Learning objectives

By the end of this lesson, you will be able to — mapped to the course outcomes for Building Materials & Construction I:

1
CO3 · Understand

Read and interrogate a design brief — givens, opportunities and constraints.

2
CO3 · Apply

Programme a building: a schedule of spaces, users and adjacencies.

3
CO3 · Apply

Turn a programme into bubble and adjacency diagrams.

4
CO3 · Analyse

Analyse a site — sun, wind, access, views, context, constraints.

Understand before you draw

The brief & the programme

Interrogate the brief, then programme: list the spaces, who uses them, how big, and what must be near what. Turn that into bubble and adjacency diagrams before you commit to a plan.[1, 2]

Reading the brief

A brief states needs, goals, users, site and budget. Interrogate it: separate the givens from the assumptions, the needs from the wants, the opportunities from the constraints.[1]

Programme → bubble → zoning → plan schedule bubbles zoning plan
DiagramFrom brief to programme to bubble diagram to zoning to plan
Bubble Diagram PlannerTurn your programme into adjacencies, interactively.Room Programming WorksheetBuild a schedule of accommodation for your brief.
Grid & matrix

Two more ways to organise space

The bubble diagram is the start. An adjacency matrix records the same relationships more rigorously — which spaces must adjoin, sit near, or stay apart — while the classic nine-square grid exercise teaches you to organise space, structure and circulation within a simple order.

Adjacency matrix EntryLivingKitchenBedroomBath ELKBW must adjoin near keep apart
DiagramAn adjacency matrix marking which spaces must adjoin, which sit near, and which stay apart
The nine-square grid served servant A classic first exercise: explore column, wall, plane and void — and served vs servant space — within one simple grid.
DiagramThe nine-square grid exercise — columns, walls, served and servant space within a 3x3 grid
Read the place

Analyse the site

Inventory the site systematically — sun, wind, access, views, contours, trees, context and bylaws — then read it for opportunities and constraints that will shape your design (Edward T. White).[4]

Read the site before you draw EW · sun path prevailing wind access good view Sun, wind, access, views, contours, trees, context, bylaws — inventory them, then read the opportunities and constraints.
DiagramA site analysis diagram showing sun path, wind, access, views and contours
A site-analysis board — sun, wind, access, views, contours.
PhotoA site-analysis board — sun, wind, access, views, contours.
A sun-path study checked against a massing model.
PhotoA sun-path study checked against a massing model.
A white card context model of the site and its surroundings.
PhotoA white card context model of the site and its surroundings.
A desk mid-programming — bubble diagrams and a schedule.
PhotoA desk mid-programming — bubble diagrams and a schedule.
Check your understanding

Self-assessment

1. Peña & Parshall famously summarised programming as:

2. A bubble diagram primarily shows:

3. Which belongs in a site analysis?

In a nutshell

Recap

Interrogate the brief — separate givens, needs and wants, opportunities and constraints.
Programme first: 'programming is problem seeking' (Peña & Parshall's five steps).
Turn the programme into bubble and adjacency diagrams before drawing a plan.
Analyse the site — sun, wind, access, views, context, bylaws — into opportunities and constraints.
The evidence

References & further reading

  1. [1]Reading and writing an architectural design brief. Archisoup; First In Architecture checklist. https://www.archisoup.com/the-architecture-design-brief
  2. [2]Peña, W. & Parshall, S. Problem Seeking: An Architectural Programming Primer (5th ed., Wiley) — the five-step method. https://www.wiley.com/en-us/Problem+Seeking:+An+Architectural+Programming+Primer,+5th+Edition-p-9781118084144
  3. [3]Bubble diagrams and adjacency in architectural planning. Archisoup. https://www.archisoup.com/architecture-bubble-diagrams
  4. [4]White, E.T. Site Analysis: Diagramming Information for Architectural Design. Architectural Media. https://www.re-thinkingthefuture.com/rtf-architectural-reviews/a4981-book-in-focus-site-analysis-diagramming-information-for-architectural-design-by-edward-t-white/
  5. [5]SWOT and site inventory in architecture. Learn Architecture; Archisoup site-analysis presentation. https://www.archisoup.com/architecture-site-analysis-presentation

Further reading

  • Peña, W.M. & Parshall, S.A. (2012). Problem Seeking: An Architectural Programming Primer (5th ed.). Hoboken, NJ: Wiley.
  • White, E.T. (1983). Site Analysis: Diagramming Information for Architectural Design. Tucson, AZ: Architectural Media.

Sources gathered and fact-checked June 2026. Published values vary by source, sample and method — treat as indicative and confirm against the cited standard before structural use.