Showing Process, Not Just Results

In a maths exam you are told to show your working, because the answer alone does not prove you understood - you might have copied it. A portfolio is the same. The finished render, plan or photograph is the answer; on its own it tells a reader that you (or someone, or some tool) arrived at a result, but not that you can get there again, on a different problem, in their office. The working - your sketches, options and tests - is what proves the thinking is yours and repeatable. That is why experienced reviewers, tutors and studio principals alike say they look hardest at process pages.

This has become more true, not less, as tools have grown more powerful. When anyone can generate a slick visualisation quickly, the polished result is a weaker signal of ability than it once was - it no longer separates the person who understands from the person who pressed a button. What a machine cannot fake is the trail of judgement: why this option and not that one, what you learned when the first idea failed, how a constraint reshaped the design. Showing that trail is now one of the clearest ways to demonstrate that there is a real mind behind the images. It is also, quietly, a matter of honesty - process work shows how much of the thinking was genuinely yours, which is a theme this course returns to in Module 7.

There is a second reason, just as practical. Process work is where your personality as a designer lives. Two students can arrive at similar final buildings, but their sketchbooks reveal completely different minds - one obsessed with structure, one with light, one with how people move. A reader trying to decide whether you would fit their studio learns more from how you think than from what you produced, and process is where how-you-think is legible. Hiding it to look 'professional' throws away your most distinctive asset and leaves you looking like everyone else with a clean render.

'Show your process' does not mean photograph your entire sketchbook and dump it on the page. It means select the process that shows thinking, which is a small, curated subset of everything you produced. Here is what earns space:

Concept sketches - the early drawings where the idea appears. Not every doodle, but the two or three that show the move being found. A rough, honest sketch that captures the idea is worth more than a tidied-up 'concept diagram' made afterwards, because readers can tell the difference and they value the real thing.

Iterations and options - two, three, four versions of a plan, a massing, a facade, shown side by side, ideally with a word on why you moved from one to the next. This is the single most persuasive kind of process, because it proves you generated alternatives and chose - the essence of design judgement.

Tests and studies - the daylight study, the physical massing models, the structural sketch, the material sample, the mock-up. Anything where you tried something to find out whether it worked. These show rigour and a willingness to check your ideas against reality.

Decisions and turning points - the moment the project changed direction, and why. 'The first scheme put the stair here; it killed the daylight, so it moved' is a tiny story that shows more judgement than a page of finished plans.

What does not earn space: process that is just mess with no thinking in it, every version of everything, tidied-after-the-fact fake sketches, and process shown purely to prove you worked hard. The test is the same as everywhere in this course - does this show my thinking to this reader? A single page of well-chosen iterations beats twenty pages of undifferentiated sketchbook. Curate your process with the same ruthlessness you curate your projects.

The danger at the other extreme is real: a portfolio can drown in process. Pages of tiny sketches, endless near-identical options, and mess for its own sake read not as a rigorous mind but as someone who cannot edit - which is the opposite of the impression you want. The goal is curated process: enough to prove the thinking, presented clearly enough to be read, and always in service of the result rather than competing with it.

A few principles keep process legible. Sequence it. Process shown in the order the thinking happened - sketch, then options, then the study that resolved them, then the outcome - tells a story; the same images scattered randomly read as clutter. Annotate lightly. A few words on an iteration ('too tall for the street', 'this version freed the corner') turn a set of images into visible reasoning; without them the reader sees shapes and guesses. But keep the words few - the images should carry most of it. Give it less space than the result, but real space. A common, effective structure is a project that opens and closes on strong resolved images, with a curated process section in the middle - the development beat of the story from the last lesson. Process supports the result; it does not replace it. Make it readable. Process pages are where portfolios most often fail on legibility - tiny thumbnails, no captions, no order. If a reader cannot tell what they are looking at in a couple of seconds, the process is not working for you, however rigorous it was.

One honest caution: do not manufacture process you did not do. If you designed something quickly and directly, do not fake a trail of tortured iterations to look rigorous - experienced readers smell it, and it reads worse than an honest, direct process. Show the real thinking you did, chosen and clarified, and if a project genuinely had little process worth showing, lean on a different project for your process story rather than inventing one.

Knowing you should show process, and having curated it, the last question is placement - within a single project, and across the whole portfolio.

Within a project, the natural home for process is the development beat of the story: after you have framed the problem and stated the idea, and before you resolve it. This mirrors how the project actually unfolded and gives the process a job in the narrative rather than making it a random gallery. A reliable shape for a multi-page project is: open on a strong hero and the framing statement (problem + idea), move into a spread of curated process (the iterations and tests that developed the idea), and close on the resolved drawings and images. The reader meets the idea, watches you earn it, and sees where it landed - process doing exactly the work the story needs.

Across the whole portfolio, you do not need to show deep process for every single project, and trying to will bloat the document. A strong strategy is to make one or two projects your 'process' projects - the ones where you show the thinking in real depth - and let others lead more on resolved results, especially where the process was thin or the images are the point. This gives the reader both signals - 'I can think' and 'I can finish' - without every project carrying the full load. For interviews and grad-school applications especially, having at least one project that shows deep, honest process is close to essential, because those readers are buying your mind above all. Finally, keep your process material as you go. The single most common regret is finishing a project, keeping only the final renders, and discovering months later that the sketches, study models and working files - the most valuable portfolio material you had - are gone. Photograph the sketchbook, save the iteration files, shoot the study models before you dismantle them. Process is evidence, and evidence has to be kept.