What should a UX portfolio include?

A UX portfolio should include 2-4 case studies that each show a clear problem, your specific role, your design process, the decisions you made and why, and a measurable or observable outcome. Add a short about section, contact details, and links to any live work or prototypes.

How many case studies should a UX portfolio have?

Two to four case studies is the right range for most early-career UX designers. Two strong, well-documented case studies will outperform eight shallow ones. Quality and depth of reasoning matter far more than volume.

What do hiring managers look for in a UX portfolio?

Hiring managers look for evidence that you can identify a real problem, structure your thinking, involve users, make design decisions with clear rationale, and communicate your process. They want to understand how you think, not just see polished final screens.

What are common UX portfolio mistakes?

Common mistakes include showing only final designs with no process, using vague language ('I improved the user experience'), hiding your individual contribution in group projects, missing measurable outcomes, and making the portfolio hard to navigate or slow to load.

UX Portfolio Review Checklist (Free)

Before you send your portfolio to a hiring manager, run it through this checklist. A strong UX portfolio is not about beautiful mockups - it is evidence that you think clearly, involve real users, and make design decisions you can defend.

Use this as a self-review tool. Work through each section honestly. Flag anything that does not pass, then fix it before you apply.

How to Use This Checklist

Print it, copy it into a doc, or work through it on screen. For each item, mark it as:

Pass - clearly in place
Fix - present but needs improving
Missing - not there at all

Aim for no "Missing" items before you apply anywhere. For senior roles, aim for no "Fix" items either.

Section 1 - Overall Portfolio Structure

A recruiter typically spends under two minutes on a first pass. Your structure needs to do the work.

Navigation and access

[ ] Portfolio URL is short, professional, and easy to share (no long random strings)
[ ] Site loads in under 3 seconds on a mobile connection
[ ] Navigation is immediately clear - visitor can find case studies within one click
[ ] No broken links or placeholder pages

First impression

[ ] Homepage or landing section states who you are and what kind of work you do
[ ] It is immediately obvious this is a UX design portfolio (not a graphic design or development portfolio unless that is your angle)
[ ] You have 2-4 case studies featured, not a grid of 10 thumbnail images
[ ] About section is present and is 2-4 short paragraphs (not a wall of text, not a one-liner)

Contact and credibility

[ ] Contact details or a contact form are easy to find
[ ] LinkedIn profile is linked and up to date
[ ] Any certifications, courses, or bootcamp completions are mentioned briefly

Section 2 - Each Case Study (Run This for Every Project)

This is where most portfolios fall short. Work through these questions for every case study individually.

Problem and Context

[ ] The problem is stated in plain language in the first paragraph
[ ] The business context is explained (what product, what company type, what user base)
[ ] It is clear why this problem mattered - what was at stake for the user or the business
[ ] You do not open with a paragraph about "what UX is" or your design philosophy

Your Role

[ ] Your specific role is stated clearly (solo designer, part of a team, lead, support)
[ ] If it was a team project, your individual contribution is explicitly described
[ ] The timeline and any constraints (time, budget, access to users) are mentioned briefly

Research and Discovery

[ ] You describe what research method(s) you used and why you chose them
[ ] You name real methods (user interviews, usability testing, card sorting, surveys, desk research) - not just "I did research"
[ ] You show what you learned from the research, not just that you did it
[ ] If you had limited access to users, you acknowledge it and explain what you did instead

Design Process and Decisions

[ ] You show process artefacts: wireframes, journey maps, affinity diagrams, prototypes - at least some working artefacts at different fidelities
[ ] Each major design decision has a rationale ("I chose X because...")
[ ] You show iteration - an early version and how it changed in response to testing or feedback
[ ] You do not just present the final polished screens as if they appeared fully formed

Outcomes and Evidence of Impact

[ ] The case study has a defined outcome - what happened when the design was implemented or tested
[ ] Wherever possible the outcome is specific: a usability score, task completion rate, conversion change, time-on-task reduction, or stakeholder decision made
[ ] If the project was academic or self-initiated and has no live outcome, you state that clearly and explain what you would measure if it shipped
[ ] You do not use vague phrases like "improved the user experience" as the outcome

Reflection

[ ] The case study ends with at least a brief honest reflection
[ ] You name something you would do differently with more time or resources
[ ] You mention what you learned from this project
[ ] The reflection sounds genuine, not like a cover letter sign-off

Section 3 - Visual Presentation

[ ] Mockups and screens are shown at a readable size - not tiny thumbnails
[ ] Image quality is crisp (no blurry exports or low-resolution screenshots)
[ ] Annotated wireframes include legible labels - zoomed in enough to read
[ ] You are not relying entirely on Dribbble-style aesthetic shots with no process context
[ ] Colour and layout are consistent across the portfolio (not a different visual style per project)
[ ] Prototype links work and are tested on the device a recruiter is likely to use
[ ] If you include video walkthroughs, they have captions or a text summary alongside

Section 4 - Written Clarity

Bad writing undermines good design thinking. Your writing is part of the portfolio.

[ ] Case study titles describe the project and problem, not just the company name ("Redesigning the checkout flow for a B2C fashion retailer" not "Nike Project")
[ ] Paragraphs are short - three to five sentences maximum before a break
[ ] You use plain language throughout - no unnecessary jargon
[ ] Passive voice is minimised ("I ran five user interviews" not "five user interviews were conducted")
[ ] You write in first person and take ownership of decisions
[ ] No spelling errors or grammatical mistakes (ask a trusted reviewer to read it fresh)
[ ] UK English or US English is used consistently - do not mix them

Section 5 - Red Flags to Fix Before You Apply

These are the most common reasons a portfolio gets passed over. Check each one specifically.

Process red flags

[ ] You are not showing only final deliverables with no process work
[ ] You are not describing every project as "a team effort" with no individual contribution stated
[ ] You have not included a project where you never spoke to a single real user (if you have one, acknowledge the limitation)

Content red flags

[ ] You have not included more than one "redesign a famous app" speculative project as a main case study
[ ] Your projects are not all from the same brief or bootcamp template - they show some range
[ ] You have not described your role as "UX/UI/graphic/brand designer" with no clear positioning

Presentation red flags

[ ] Your portfolio does not require a PDF download to see the work (PDF as a supplement is fine; PDF as the only format is not)
[ ] You do not have a case study that is one page of text with no visuals at all
[ ] You have not listed 15 tools in your skills section as a substitute for showing what you can do with them

Section 6 - Final Pre-Application Check

Run this final sweep immediately before each application round.

[ ] You have re-read every case study in the last 30 days and it still represents your best current thinking
[ ] Any dates, timelines, or project statuses are accurate
[ ] Your portfolio loads correctly in Chrome, Firefox, and Safari
[ ] You have tested it on a phone - a significant proportion of recruiters will view it on mobile
[ ] The email address or contact form on the site goes to an inbox you check regularly
[ ] If you have a password-protected case study for confidential client work, you have included the password in your application email

What to Do With Your Results

If you have a cluster of "Fix" or "Missing" marks in Section 2 (the case study criteria), that is the highest-priority area. One case study with outstanding depth and clear evidence of impact will carry a portfolio. Five thin ones will not.

If Section 4 (written clarity) has issues, treat it as a skills gap worth addressing seriously. UX designers communicate in writing constantly - to stakeholders, in design specs, in research reports. A portfolio with weak writing signals something a hiring manager cannot overlook.

For a broader view of building your portfolio from scratch, read our UX design portfolio guide. If you are just starting out, getting a UX job with no experience covers how to approach the job search before your portfolio is complete. And if you are still deciding whether UX design is the right move, what does a UX designer actually do is a good place to start.

Build a Portfolio-Ready Project During Your Course

The most common gap in early-career portfolios is a real client project - one where you worked with actual users and a real brief, not a fictional scenario.

UX Academy's beginner UX design course includes a live client project built into the curriculum. You work with a real organisation, run your own user research, and produce a deliverable you can put straight into your portfolio. Taught live online, based in the UK, with the next cohort starting 5 September 2026.

If you want to see what the course covers before committing, the free UX and UI masterclass is a good first step.