Updated 2026-07-27
Portfolio reviews are fast and unfair. Whoever opens yours is deciding within seconds whether to keep scrolling, and they are doing it while tired, on a laptop, with fourteen other portfolios open.
That is not a reason to despair — it is a spec. Design for that reader specifically and you will beat portfolios with better work in them.
Show fewer projects than you want to
Three to five strong projects beat ten of mixed quality, every time. You are not judged on your average — you are judged on your weakest visible piece, because that is the one that tells them what you cannot yet see.
The test for including something: would you be happy to spend fifteen minutes defending this in an interview? If not, it is costing you.
Lead with the outcome, not the process
The first screen of each case study should show the finished thing, clearly, at a glance. Reviewers who are interested will read the reasoning; reviewers scanning need to see immediately whether your level matches their bar.
This is the exact opposite of the "my process: discover, define, ideate" opening that portfolio templates encourage, and it is why so many portfolios all feel the same.
But do show the thinking
Pretty mockups prove you can use software. What gets people hired is evidence that you make good decisions when the brief is unclear — because that is the actual job.
For each project, answer three things in a couple of sentences each: what the problem was, what you decided and why, and what happened. "We cut the signup form from nine fields to four and completions rose" is worth more than four artboards of visual exploration.
Be honest about what you did
Team projects are fine. Student projects are fine. Speculative redesigns are fine. Presenting any of them as something they were not is the fastest way to lose an interview, because experienced reviewers ask follow-up questions and the gaps show instantly.
A clearly-labelled personal project you can discuss deeply beats a real client project you contributed one screen to.
The portfolio is itself a portfolio piece
People forget this constantly. If your case-study pages have inconsistent spacing, unreadable line lengths and three typefaces, you have demonstrated the opposite of your claim — no matter how good the work inside is.
Design the container with the same care as the contents. It is the only piece where the reviewer sees your decisions applied to your own goals.
Quiet mistakes that cost interviews
- No indication of what you actually want to do — a reviewer should know within one screen whether you are a brand designer, a product designer or a generalist.
- Making people request access, hunt for a PDF, or wait on a heavy animated intro. Friction at the door loses more candidates than weak work does.
- Unreadable case-study text: pale grey on white, huge line lengths, walls of paragraphs with no headings.
- No contact route that works in one click, or a contact form that quietly fails.
- Nothing recent. A portfolio whose newest piece is three years old raises a question you never get to answer.
One test before you send it
Open it on a phone, on a bad connection, and give yourself thirty seconds. What did you learn about the person? If the answer is "they can make things look nice", it is not finished. It should be "they solve this kind of problem for this kind of client, and here is proof".