Curating Your Best Work

By now the principle is familiar - a portfolio is an argument, judged by its weakest included piece - but living by it is the hard part, because it asks you to leave things out. Curation is the act of deciding what stays and what goes, and it is the single highest-leverage skill in portfolio-making. It is also the most resisted, because every instinct pushes the other way: you want to show range, to prove you worked hard, to not 'waste' a project that cost you a whole semester.

Here is the arithmetic that should settle it. Imagine two portfolios. One has your six best projects, each strong and well presented. The other has those same six plus four weaker ones you added to look thorough. The second is not more impressive - it is less. Adding weaker work does two things, both bad: it lowers the reader's average impression, and it signals that you cannot tell your strong work from your weak. That second signal is quietly fatal, because judgement is exactly what a studio or school is trying to assess. A curated portfolio says 'I know what my best is'; a padded one says 'I hoped volume would do the arguing for me'.

This is why the honest guidance is almost always fewer than you think: for most students and early-career designers, four to eight strong projects for a main portfolio, and as few as three to five for a specific job application. There is no magic number, and a senior architect's book may hold more - but the principle never softens with experience; if anything it sharpens. The best portfolios you will ever see are defined by what their makers had the confidence to leave out.

Quantity feels safe and is not. Every extra page dilutes attention in the six-second scan, buries your strongest work deeper, and gives a tired reviewer another chance to find something that disappoints. Fewer, stronger, better-presented is not the compromise you make when you run short of good work - it is the strategy that wins even when you have plenty of it.

'Curate ruthlessly' is useless as advice until you have a way to actually decide. Here is a simple, honest method you can run on any project list. Score each project out of five on three axes, then let the scores - and your judgement - draw the line.

Strength - how good is the design thinking and the work itself, on its own merits? Set aside for a moment how well you can show it: is the idea good, is it resolved, would you be proud to talk about it? A brilliant concept that fizzled scores lower than a modest idea carried all the way through.

Showability - how good is what you actually have to present it with? A strong project with only blurry phone photos, missing drawings or no resolution is, for portfolio purposes, weak - because the reader can only judge what they can see. This axis is why re-shooting a model or redrawing a plan can rescue a project, and why an amazing project you cannot document well may still have to sit out.

Fit - how well does it serve this reader's decision (Lesson 0.2)? The most technical project scores high for a corporate role and lower for a design studio; the most conceptual, the other way round. Fit is the axis that changes between applications while strength and showability stay roughly fixed.

Add the three and you have a rough ranking - but treat the number as a conversation-starter, not a verdict. Two human tests finish the job. First, the proud-to-talk test: could you speak about this project for five minutes in an interview with genuine energy? Work you are bored by reads as boring. Second, the range test, used carefully: once your top projects are chosen, check they are not all identical - a little breadth (a public building beside a house, a drawing-led project beside a built one) can strengthen the argument - but breadth is a tie-breaker among strong work, never a reason to promote weak work. Quality first; range only among equals.

Cutting weak work is easy once you accept the principle. The real test - the one that separates a strong portfolio from a merely full one - is leaving out good work. There will be projects that are genuinely strong and that still should not be in this portfolio, and letting them go hurts. Three traps make it harder than it needs to be.

The sunk-cost trap. 'I spent four months on this, it has to go in.' Effort is not the criterion; the reader neither knows nor cares how long a project took, only what it does for their decision. A project that cost you a semester and does not serve the argument is still a cut. Time already spent is spent either way - do not let it buy space in your portfolio.

The range trap. 'I need to show I can do everything.' Trying to prove breadth by including a weaker example of a different type almost always backfires, because it drags the average down and blurs your identity. It is far stronger to be clearly excellent at a few things than mediocre-but-versatile at many. If a reader wants to know whether you can do something you have not shown, they will ask.

The darling. Every designer has a project they love that simply does not land for others - too personal, too niche, poorly documented, or strong in ways only they can see. Learning to 'kill your darlings' - to cut work you are attached to when it does not serve the reader - is a mark of real editorial maturity. Keep it for yourself; leave it out of the argument.

A test that helps with all three: for each project ask, if this were the only thing the reader remembered, would it help my case? Because in the six-second scan, one weak or off-key piece can be exactly what sticks. It also helps to borrow a second pair of eyes - a tutor, a working friend, a mentor - because we are all blind to our own darlings. Ask them not 'is this good?' but 'which two would you cut, and which one should open?' The answers are usually clarifying, and occasionally a relief.

Curation sounds like deletion, but the healthiest way to do it is the opposite: you are not throwing work away, you are drawing a line for a particular reader, with everything below it moved to a cut list you keep. Nothing is lost; it is simply not in this argument.

Draw the line like this. Take your ranked, scored list. Decide the target length for this reader - say five to eight projects for a main portfolio, three to five for a job application. Draw a hard line at that point. Above the line: your portfolio. Below: the cut list. Resist the urge to smuggle a ninth project back in because it is 'nearly as good' - the discipline of the line is the whole point.

The cut list is genuinely useful, not a consolation prize. It holds three kinds of work worth keeping: re-shoot / redraw candidates (strong projects whose only problem is showability - fix that and they may make the next cut); reader-specific reserves (good work that does not fit this reader but will lead beautifully for another); and the longer-version material you send only when a reader specifically asks to see more. A well-kept cut list is what lets you tailor fast for the next application instead of starting over.

One more discipline closes the loop: the portfolio is never truly finished, so the cut line moves over time. As you make stronger work, it should push weaker work off the bottom - a new project does not simply get added, it competes for a place, and if it is better than your current weakest, that weakest one drops to the cut list. This keeps a portfolio improving in quality even as your quantity of work grows, and it is the habit behind Module 10's 'living portfolio'. Curate once and you have a snapshot; curate as a habit and you have a portfolio that gets stronger every year.

So: score honestly, draw a hard line for the reader, keep everything below it on a living cut list, and let new work fight for entry. That is ruthless curation made practical - and repeatable.