A portfolio isn't a gallery. It's an argument. Every piece you include, every case study you write, every layout decision you make should serve a single purpose: convincing the viewer that you can solve their kind of problem.
Most portfolios fail not because the work is weak, but because the presentation doesn't do the work justice. The design is beautiful but the story is missing. Or the case studies are thorough but the portfolio itself doesn't guide the viewer toward a decision. Let's fix that.
Start with the goal
Before touching layouts, answer two questions:
- What do you want someone to do after visiting? — Hire you? Contact you for a project? Advance you to the next interview round? The answer shapes everything.
- Who is the viewer? — A hiring manager at a tech company evaluates differently from a startup founder looking for a contract designer. Know your audience and design for their decision-making process.
A portfolio for a design systems role should emphasize systems thinking, documentation quality, and cross-functional collaboration. A portfolio for a brand design role should lead with visual impact and strategic rationale. Same designer, different portfolio emphasis.
How many pieces to show
There's a pattern recognition principle at work: once is chance, twice is coincidence, three times is a pattern. You need enough work to establish a pattern of quality and capability — but not so much that the strong pieces are diluted by weaker ones.
For most designers, 4–6 featured pieces on the main page is the right range. Additional work can live on secondary pages for viewers who want to go deeper. Each featured piece should be your strongest representation of a specific skill or project type.
As your work improves, swap out the weakest piece for a stronger one. Your portfolio should always represent your current best, not your complete history.
Case studies are the core
Beautiful screenshots get attention. Case studies get you hired.
A case study demonstrates how you think, not just what you produced. For each project, structure the story around:
- The problem — What was the situation? What needed to change? What constraints existed?
- Your process — How did you approach the problem? What did you explore, test, and learn along the way? Include the decisions, not just the deliverables.
- The outcome — What was the result? If you have metrics (conversion improvements, reduced support tickets, adoption rates), include them. If not, describe the qualitative impact.
Write during the project, not after. Keep a running document where you capture decisions, rationale, and process artifacts as they happen. Reconstructing a case study from memory months later produces thin, generic narratives. Real-time notes produce specific, compelling stories.
Presentation matters
Think of your portfolio site the way you'd think of a gallery: the work should be the focus, not the frame. A clean, well-organized portfolio lets the work speak. An overdesigned portfolio competes with it.
The first 5 seconds matter most. When someone lands on your portfolio, they should immediately understand:
- Who you are
- What kind of design work you do
- How to see more
If your hero section requires scrolling to understand what you do, you've lost people. Be direct.
Don't show work you don't want more of
Your portfolio attracts more of whatever it contains. If you show branding work, people will ask you to do branding. If you show dashboard design, people will bring you dashboard problems.
This means being selective. If you did a project you're technically proud of but it's not the kind of work you want to continue doing, leave it out. Every piece in your portfolio is a signal about what you want to be hired for next. Make it intentional.
Working under NDA
Non-disclosure agreements don't mean you can't have a portfolio. You have options:
- Write process-focused case studies that describe your approach, methodology, and results without showing proprietary visuals or naming the client.
- Create concept projects that demonstrate the same skills on non-restricted subject matter.
- List companies and roles you've worked with, supported by recommendations from colleagues who can speak to your contributions.
- Ask for permission — many companies allow portfolio use of specific, non-sensitive work with approval. It's worth asking.
Your portfolio is a living document
The designers who consistently land the roles they want treat their portfolio as an ongoing project, not a one-time build. Review it quarterly. Does the featured work still represent your current skill level? Are the case studies telling the right story for where you want to go next?
Your portfolio's job isn't to show everything you've done. It's to show the viewer exactly what they need to see to take the next step with you.