Most design portfolios are competent and interchangeable. They contain attractive final screens, a device mockup on a soft gradient, a colour palette laid out in circles, a typeface specimen, and a short paragraph beginning with the words the client wanted. They demonstrate that the person can operate the software and has taste. They do not demonstrate that the person can think, and thinking is what is being hired.
The gap is not a matter of polish. It is a matter of what is being shown at all.
Show the decision, not the deliverable
A portfolio’s job is to let someone reconstruct how you reason, using evidence.
That means every project should make four things visible: what the actual problem was, what constrained the solution, what you decided and why that rather than the obvious alternative, and what happened afterwards.
The third of those is where almost everyone is silent. A designer will show a final identity and never mention that the first direction was rejected, or that the client’s existing customers could not read the original typeface at the sizes their packaging required, or that the whole thing had to work when printed in one colour on a corrugated box. Those constraints are the interesting part. They are what separates a design from a picture.
Write one sentence per project of the form: we chose X rather than Y because Z. If you cannot write it, you either did not make a decision or you have not worked out what it was.
Fewer projects, properly told
Four to six pieces of work is the right number. Beyond that you are diluting, and the reader stops at the third anyway.
Choose them for range rather than for quality alone. One that shows systems thinking, one that shows craft at close range, one that shows you working within a hard constraint such as budget, regulation or an existing brand, and one that shows what you do when nobody is telling you what to do.
Cut the rest. A weak fifth project does more damage than a missing one, because a portfolio is read as a statement about your standards.
Show the middle
Finished work all looks inevitable. The value is in what it was before it was inevitable.
Include real intermediate material: sketches, rejected routes, a screenshot of the version that did not work with a line about why, the typographic tests, the grid, the states of a component. This is the single most effective differentiator available and it costs nothing but the discipline to photograph your desk occasionally.
One warning, and it is where the discipline breaks down: process theatre is not process. Photographs of sticky notes on a wall, a persona named Sarah, 34, marketing manager, and a four-arrow diagram labelled discover, define, develop, deliver are not evidence of thought. They are evidence of a workshop having occurred. Reviewers who hire designers have seen thousands of them and read them as filler. Show the artefacts that changed the outcome, not the artefacts that documented the meeting.
Be honest about what you did
Most substantial work is made by teams, and everyone reading knows it.
State your role plainly, in a line: art direction and typography, with illustration by someone else, in a team of four, over three months. Naming your contribution precisely makes the rest of the portfolio more credible, not less. Presenting a team project in the first person singular is the fastest way to fail a portfolio review, because the reviewer will ask about a decision you did not make and the conversation ends there.
The same applies to student and speculative work, which is fine to include when clearly labelled. Unlabelled speculative rebrands of famous companies are the weakest material in circulation, and there are a great many of them.
Evidence of craft, at actual size
Taste is claimed everywhere and demonstrated rarely. Demonstrate it by showing work at a scale where craft is visible.
For anything typographic, include a detail at reading size, not a hero shot of a heading. Show the spacing, the hierarchy, the way long text behaves, the awkward paragraph. For interface work, show the empty state, the error state, the loading state and the version with a name three times longer than the design assumed, because those are the screens that reveal whether a system was designed or a screen was decorated.
For print and packaging, show the physical object, photographed properly, including the parts that are hard: the fold, the spine, the die-cut, the special finish, the back. Name the stock and the process. People who make things love this material and it is almost always absent.
Outcomes, without inventing them
Everyone advises showing results, which pushes designers into asserting improvements they cannot support. Do not do that. An unverifiable claim of a large uplift is worse than no claim, because the reviewer either does not believe it or asks a question you cannot answer.
What you can honestly say is often more persuasive anyway. The system is still in use three years on. It was extended by another team without input from us. It cut the number of templates the marketing team maintained. The client returned for further work. The packaging went into production unchanged. These are checkable, specific and they describe design working in the world.
The portfolio is itself a piece of work
It is the only project where you are the client, and it is read as such.
Two failure modes. The first is the portfolio as personal art project: unreadable navigation, animation that delays every interaction, a scroll that hijacks the mouse, body text at nine pixels in light grey. It says that you prioritise your own expression over the reader’s needs, which is exactly the trait nobody wants to hire.
The second is the template, unmodified, with a stock hero and a generic sans. It says nothing at all.
Aim for something plain, fast, well set and slightly opinionated. Make sure it works on a phone, because a substantial share of first views happen on one, often by someone glancing at a link between meetings. Make sure the images load. Make sure it does not require a login, because a portfolio behind a password request is frequently not opened.
Write properly
Design portfolios are full of bad writing, and it is more visible than bad kerning to the people doing the hiring.
Short sentences. Concrete nouns. No leveraging, no elevating, no crafting bespoke experiences, no journey. Say what the thing was for and what you did. If a sentence would survive being pasted into any other designer’s portfolio unchanged, delete it.
Rehearse the talk-through
If the portfolio is doing its job, it gets you into a room where you will be asked to walk through two projects in ten minutes. Prepare that version deliberately, out loud, more than once.
The structure that works: here was the problem, here is the constraint that made it difficult, here is what we tried, here is what we chose and why, here is what I would do differently. That last clause matters more than people expect. A designer who can identify a weakness in their own strongest project is demonstrating judgement, and judgement is what is being bought.
The self-initiated project
One last thing, and it is the fastest way to change how a portfolio reads. Include something you made because you wanted it to exist: a typeface, a small tool, a poster series, a book, a documented investigation into something specific.
It does not need a client and it does not need to have succeeded. It shows what you do when nobody is paying you, which is the only reliable evidence of what you actually care about, and it is the thing interviewers remember a week later when they are deciding between two people whose client work was equally good.
