Most portfolios are archives. A grid of thumbnails, a client list, a line about being passionate about branding. Three projects, treated properly, will beat that every time — not because three is a magic number, but because depth is the only thing a stranger can genuinely evaluate. A finished logo tells a reviewer almost nothing. A case study that shows the brief, the wrong turns and the reasoning behind the final layout tells them whether you can be trusted with their problem.

Three is a decision, not a compromise

A reviewer will spend a couple of minutes on a first pass through your work. You cannot control that. What you can control is what happens on the second pass, when they open a single project and start reading. Three deep case studies invite that second pass. Forty thumbnails do not.

There is a second benefit, and it is the one people underestimate: choosing three forces you to judge your own work. That judgement — deciding what is good enough to show and what is not — is the same skill clients pay for. Three is a floor rather than a ceiling, though. If a fourth project adds something the others do not, include it. If it repeats what the first three already prove, it is diluting the argument.

Choose three projects that prove three different things

Your three projects should not all demonstrate the same strength. A portfolio of three beautiful packaging projects says you can do one thing well. That may be enough for a specialist studio; for most roles it is a risk.

Run every candidate through these questions before you commit:

• Does it contain a decision? Not just an output. Somewhere in the project, something could have gone another way.
• Can you talk about it for twenty minutes? If the honest answer is "the client asked for a leaflet and I made a leaflet", it cannot carry a case study.
• Is there evidence? Photographs, sketches, earlier versions, feedback, real constraints on time or budget.
• Do you still stand behind it? Enthusiasm reads clearly on a screen. So does its absence.

Aim for a spread: one project that shows craft — typography, illustration, image-making or layout done with real care; one that shows thinking at a system level, such as an identity or a campaign that had to work across many touchpoints; and one that shows you can collaborate or work inside a tight constraint, because that is what most jobs consist of.

What to do when your paid work is thin

Plenty of strong portfolios are built from work that was never invoiced. Self-initiated projects, a redesign you did for practice, a publication for a local club, a poster series for a gig, a collaboration with a photographer or a developer.

Two rules apply. Be precise about what the project was — speculative, personal, coursework, unsolicited — because presenting a redesign of a live brand as client work is the fastest way to lose trust in an interview. And invent the constraint if there was not one. Give yourself a fixed format, a fixed audience and a fixed reason for existing. A poster series explaining a subject you actually understand will read better than a poster series with no subject at all.

Build each case study around decisions, not screenshots

This is where most portfolios collapse. The images are lovely and the text describes the images. Nobody learns anything.

This structure works well, and you can adapt it:

1. Summary. Two sentences: what it was, who it was for, what changed.
2. Context and constraints. The audience, the budget, the deadline, the thing that made it difficult.
3. Your role. Be exact. "Sole designer" and "one of four, responsible for layout and image research" are different claims, and the second is often more convincing.
4. Process. Two or three decision points, with the rejected options shown alongside the chosen one.
5. Outcome. What shipped. If it never shipped, say so and explain what you learned.
6. Reflection. One thing you would change. This signals that you are still thinking.

Show the work you rejected

Rejected directions are the most valuable images in the whole case study. They prove the final answer was chosen rather than fallen into. Two or three alternates beside a sentence explaining why each one failed is worth more than ten polished mockups.

Write captions that carry information

"Logo explorations" tells the reader nothing. "Version three, after we dropped the colour-coded system because it broke down in print" tells them how you think. Treat every caption as a small piece of the argument.

Write like a person, then tighten it

Short sentences. Fewer adjectives. First person is fine, and usually warmer than the passive voice. A line like this does more work than a paragraph of description:

We had four weeks and one photographer, so the identity had to work with type alone.

Read your case study aloud. Anywhere you stumble, rewrite. Anywhere you find yourself typing "I was tasked with", delete it and start again from what you actually did. If a paragraph runs past four sentences, split it or cut it.

Lay it out so it can be skimmed and read

Most visitors will look before they read. Make that easy without making deep reading unpleasant.

• Lead with your strongest project. The order is part of the argument.
• Keep each project to roughly six to ten images. More than that and the good ones get lost.
• Show work in context — a poster on a wall, a page held, a screen at a realistic size — not only flat artwork.
• Check every project on a phone, a laptop and a large monitor. Type that feels refined on a desktop is often unreadable on a phone.

An order of work for the next three weeks

Start by writing, not designing. Take an afternoon to draft the summary, context and process sections for all three projects in a plain document, then read them back. The gaps will be obvious: a project with no decisions, a role you cannot describe precisely, an outcome you are fudging. Fix those before you touch a layout tool.

Next, gather the material. Chase up old files, photograph physical outputs properly, export the alternates you buried. Then write the final copy, edit it twice, and only then build the pages. Finish one project completely before starting the second — a single finished case study is worth more than three half-built ones, and it gives you a template for the rest.

When it is live, send it to two people whose judgement you trust and ask one question: what do you think I am good at? If their answer matches what you wanted to say, the portfolio is doing its job. If it does not, you have a rewrite to do — and it will be a much smaller one than starting from scratch.

Photo: StockSnap / Pixabay