The Project Spread

The most common layout failure is the democratic grid: six images at the same size, evenly spaced, each given equal weight. It looks tidy, and it is deadly, because it tells the reader nothing about where to look or what matters. The eye lands in the middle, finds no lead, and bounces - and the six-second scan is spent before the reader has found anything to grab onto. A spread of equals is a spread with no hierarchy, and no hierarchy means no message.

The fix is to make one thing the hero - the single most important image on the spread, given clearly more size and weight than everything around it. Usually this is your strongest, most legible image: the best photograph, the key drawing, the render that shows the idea. It anchors the spread, gives the eye a place to land, and sets up everything else as support. The rule of thumb is decisive contrast: the hero should be visibly, unarguably bigger than the supporting images - not a bit larger, but two or three times the area - so there is no ambiguity about what to look at first.

Everything else on the spread is the supporting cast, sized by importance. The second-tier images (the plan, a key section) are medium; the third tier (details, small process, secondary views) are small. This creates a clear reading order - hero first, then the mediums, then the smalls - which is exactly the sequence in which you want the reader to take the project in. Text sits in the hierarchy too: the framing statement is prominent near the hero; captions are small and close to their images.

> Flat grid: everything the same size = the reader looks nowhere. > Hierarchy: one hero, clear support = the reader looks where you want, in the order you want.

A useful discipline when you lay out a spread: squint at it, or shrink it to a thumbnail. If one element does not clearly dominate, you have a flat grid, and you need to enlarge your hero and shrink your support until a single thing wins. If everything is shouting, nothing is heard.

The second discipline is about what each spread is for. A spread should carry one idea - one part of the project's story - not a bit of everything crammed together. When you try to fit the whole project onto every spread, each page becomes a dense, competing jumble and the story disappears. When each spread has a single job, the project unfolds cleanly, one clear beat at a time, and the reader is carried through it.

Map this onto the four-beat story spine from Lesson 1.2. A typical multi-page project might run: a first spread that establishes the project - hero image, title, framing statement (problem + idea); a second spread on development - the curated process, iterations and studies; a third spread on resolution - the resolved plans, sections and final images. Each spread does one thing. The reader meets the idea, watches it develop, sees where it landed - and never has to hold six unrelated things in their head at once.

This does not mean one image per spread, or sparse pages; it means one idea per spread, which may be carried by a hero and several supporting images all serving that single point. A resolution spread might have a hero photograph, two plans and a section - four images, but one idea: 'here is the resolved building'. The unity is the test: can you say in one short phrase what this spread is about? If you can ('the problem and the idea', 'how it developed', 'the resolved result'), it has a job. If the honest answer is 'a bit of everything', it needs to be split or focused.

How many spreads does a project get? It depends on the project and the format, but a common range is one to three spreads for most portfolio projects - a single strong spread for a minor project, two or three for a major one. Resist the urge to give every project a huge run of pages; more spreads dilute unless each one earns its keep with a real idea. As always in this course, the discipline is subtraction: give each spread one clear job, and cut the spread that does not have one.

Hierarchy tells the reader what is most important; reading order tells them what to look at next. On a page, most readers scan in a rough Z or F pattern - top-left first, across, then down - and layout that works with that natural movement reads effortlessly while layout that fights it feels awkward without the reader knowing why. So place your hero and your opening text where the eye lands first, usually the upper or left area of the spread, and arrange the supporting cast so the eye flows down and across in the order you want the story told.

A few concrete moves guide the eye without the reader noticing. Size leads first - the biggest thing is seen first, which is why the hero must dominate. Position leads next - top and left before bottom and right. Alignment and grouping cluster related things so the reader reads them together: a plan and its caption belong touching; three process images belong as a visible set, not scattered. White space is an active tool, not empty leftover - space around the hero isolates and elevates it, and space between groups tells the reader 'this is a separate thought'. Module 2.3 goes deep on white space; for now, the key idea is that generous, deliberate space reads as confidence and cramming reads as panic.

Crucially, treat the two facing pages as one composition, not two separate pages that happen to sit side by side. A reader sees the whole spread at once, so balance it across the gutter (the centre fold): a heavy hero on the left wants some counterweight on the right, and an image should rarely be split awkwardly across the gutter where the fold will swallow its middle. Design the spread as a single field with one hero, a clear path through it, and deliberate space - and the reader will move through your project exactly the way your story intends, without ever having to work at it.

A single well-laid spread is not the goal; a whole portfolio of them, reading as one considered document, is. That takes consistency - a repeating structure that lets each project feel individual while the portfolio feels unified. Decide a few things once and hold them across every project: the margins, the grid, where the project title and framing statement sit, the caption style, the type sizes for each level of the hierarchy. When these are consistent, the reader stops noticing the mechanics and simply reads the work - and the consistency itself signals a designer who can hold a system, which is exactly the competence a studio is hiring for. Inconsistency does the opposite: different margins, wandering title positions and random caption styles read as carelessness even when each individual page is fine.

Consistency is not sameness. Within a shared system, each project still gets its own hero, its own rhythm, its own number of spreads. Think of it like a magazine: every article uses the same underlying grid and type system, yet each feels distinct because the content and the hero differ. That is the balance to aim for - a recognisable, quiet framework that frames varied work without flattening it.

Finally, a spread earns extra points if it is one you can walk through, because in an interview you will literally do that - turn to a spread and talk. A well-built spread supports this: the hero gives you an opening ('this is the project, and here is the idea'), the development spread lets you tell the story of how you got there, and the resolution lets you land it. If a spread is a flat grid with no hero and no order, you have nothing to walk the reader along; if it has hierarchy and sequence, the layout itself gives you a script. So as you lay out each project, imagine talking a stranger through it in ninety seconds. If the spread makes that easy - a clear start, a clear middle, a clear end - it will work on the page and in the room. That is the whole of this module made physical: the right project, told as a story, showing your thinking, laid out so a busy reader takes all of it in and wants the next conversation.