Writing the Project Statement
The project statement is where narrative begins. Before you arrange images or design layouts, you need to define what a project is about: its central question, its intent, and its scope. Writing clarifies intent. Without a clear statement, a project becomes a collection of images without coherence, and your layout decisions become arbitrary rather than purposeful.
A project statement is not a description of what you built. It is a declaration of what you investigated and why it matters. It defines the central question your design asks and the specific approach you took to address it.
The Project Question: Weak vs. Strong
"This project is a mixed-use development in downtown." (Describes a building type, not a design position. Could apply to dozens of different projects.)
"How can a mixed-use tower use its ground plane to repair a fractured pedestrian network while maintaining structural efficiency above?" (Identifies a spatial problem and implies a design strategy specific to this project.)
PRO TIP: If you can swap your project statement between two different projects and it still makes sense, the statement is too generic. A good statement should only be true for the specific design it describes. It should guide both the reader's interpretation and your own decisions about which drawings to include.
From Statement to Narrative Outline
Once you have a clear project statement, translate it into a narrative outline before touching any layout. The outline answers three questions: What information comes first? What follows? How does the story unfold? This is the bridge between writing and design.
A narrative outline for a single project might look like:
- Context and Problem Framing: Site conditions, the spatial or social condition that motivated the project, the constraints you worked within
- Conceptual Position: Your specific approach or thesis. What is the design idea?
- Design Development: How the concept evolved through iteration, testing, and refinement. Key design moves and the evidence behind them.
- Resolution: What was achieved, what evidence demonstrates the outcome, how the final design addresses the problem you framed
Every image in the project should map to one of these stages. If a drawing does not serve any stage of the narrative, it probably does not belong.
The Two-Paragraph Project Description
Paragraph 1. Context and Intent: Establish the design problem, site conditions, and your conceptual approach in 4–6 sentences. Answer: Why does this project matter? What condition triggered the design response? What is your core design thesis?
Paragraph 2. Development and Outcome: Describe how the concept evolved through design and what was resolved. Answer: What evidence demonstrates that your approach worked? What were key design moves? How does the final design address the problem you framed?
Clarity and Specificity
Use concrete, precise language. Avoid abstractions. Instead of "The design promotes community interaction," write "The ground-floor plaza incorporates tiered seating and weather protection, enabling informal gathering even during light rain, which architectural surveys identify as the primary barrier to plaza use in this climate."
The reader should be able to understand your project's core idea in 30 seconds of reading your statement. Everything in the visual sequence should reinforce and elaborate that central idea.
Tone and Voice
Your project statements collectively establish your architectural voice. They should sound like the work of a thoughtful designer who understands design as problem-solving, not as aesthetic exercise. Write in clear, active voice. Use present tense for the design ("The plaza incorporates") and past tense for the process ("I researched," "I analyzed").
KEY INSIGHT: The project statement drives the narrative outline, and the narrative outline drives the image sequence. If you start by arranging images without a clear statement, you are decorating rather than communicating. Focus on clarity and structure, not polish.