UX portfolio examples: what strong case studies teach

Summary

Choose two to four projects that match the work you want. Give every case study a one-screen summary with the problem, your role, scope, collaborators, outcome, and a link to the full story. In the detailed story, separate evidence from assumptions, show the options you considered, explain trade-offs, credit the team, and close with results and reflection. Test the finished portfolio on a phone, with a keyboard, on a slow connection, and with someone who did not work on the project.

What a UX portfolio must prove

A UX design portfolio is evidence for a specific decision: whether someone should interview, hire, or contact you. It should establish the kind of designer you are and the problems you can handle. It should also show how you work with others and whether your decisions create useful outcomes. A beautiful interface helps only when the story remains clear. Treat the portfolio itself as a user experience with known audiences, tasks, constraints, and success signals.

• A recruiter needs a fast match between your experience and the role, plus clear contact details.
• A design manager needs evidence of judgment, craft, collaboration, and ownership.
• A cross-functional interviewer needs to understand how you worked with research, product, engineering, content, data, or operations.
• A client needs confidence that you understand goals, scope, risk, communication, and delivery.

Four current UX portfolio examples

These are examples to study, not templates to clone. Each designer has different experience, permissions, visual material, and goals. Look for the communication choice behind the surface.

Simon Pan: lead with outcomes

Simon Pan's homepage pairs recognizable projects with short role statements and measured outcomes. The lesson is not to add impressive numbers without context. It is to help a reader understand the scale and result before opening a long case study. When you have a valid metric, name what changed and make your contribution clear. When you do not, use verified qualitative evidence instead.

Study Simon Pan's live portfolio and project summaries.

Gloria Lo: make positioning immediate

Gloria Lo identifies herself as a product designer. She says her experience covers end-to-end UX and UI work for software products. That direct positioning helps a visitor decide whether the work is relevant. Write a similar introduction in your own words: role, level or focus, type of problem, and current availability when appropriate. Avoid a vague slogan that makes the reader hunt for basic context.

Review Gloria Lo's current portfolio introduction.

Elizabeth Lin: use personality without hiding the work

Elizabeth Lin's portfolio uses a playful identity while still identifying her as a product designer. The useful pattern is controlled personality: distinctive voice can make a UX designer portfolio memorable, but the work and navigation still need to remain legible. Let expression support the story. Do not make a reader decode experimental interactions before they can find projects or contact you.

See how Elizabeth Lin balances identity and portfolio content.

Kurt Winter: show a specialist range

Kurt Winter describes a focus on visual, motion, and interaction design across TV, web, mobile, and tablet. His current portfolio also uses testimonials to support claims about collaboration and problem solving. When your work spans several surfaces, state the common capability that connects them. Then use selected evidence rather than presenting an unstructured archive.

Explore Kurt Winter's current portfolio and positioning.

A clear UX case study structure

Use a stable structure across projects so the reader can compare them. The structure should explain your reasoning without pretending that every project followed a perfect linear process.

1. 1Context: describe the product, user, organization, and reason the work mattered.
2. 2Problem: state the observed problem and distinguish it from the first proposed solution.
3. 3Role: name your responsibility, timeline, team, collaborators, and decision authority.
4. 4Constraints: include relevant limits such as time, platform, policy, data, technology, access, or budget.
5. 5Evidence: show how research, analytics, support signals, expert review, or testing informed the work.
6. 6Options: present important alternatives and explain why the team rejected or changed them.
7. 7Decisions: connect the chosen direction to evidence, constraints, and business or user goals.
8. 8Delivery: show the useful artifacts, prototypes, content, specifications, or collaboration that moved the work forward.
9. 9Outcome: report verified results, what remains unknown, and any unintended effect.
10. 10Reflection: explain what you learned and what you would change with another iteration.

Be precise about ownership and evidence

Do not turn a team result into a solo story. Use first person for decisions and tasks you owned, and use we when the team made the decision. Name important collaborators and explain the handoff. Label concepts, speculative work, and self-directed projects accurately. Keep conversion lifts, user quotes, research methods, and shipped states factual. Credibility is more valuable than a perfect narrative.

Handle confidential work without breaking trust

Check the agreement and ask the owner what you may share. If public detail is restricted, describe the industry, general problem, role, constraints, methods, and learning at an approved level. Remove customer data and sensitive interface details. A password is access control, not permission to disclose. If little can be shown, use another project or create an honest independent case study.

Build an entry-level UX design portfolio

You do not need a famous client to demonstrate sound UX practice. Improve a community or nonprofit workflow with permission. You can also study an open public service, document a class project accurately, or investigate a narrow problem you can research. Choose a scope small enough to test. A thoughtful project with interviews, observations, accessibility checks, prototypes, limitations, and reflection is stronger than a fictional redesign that jumps from opinion to polished screens.

Design for a quick skim and a deep review

Homepage

give a clear role statement, selected projects, relevant work preferences, and a contact route.

Project card

name the problem, your role, the product or service, and one honest outcome or learning.

Case-study opening

summarize scope, team, timeline, constraints, and result before the long story.

Page body

use descriptive headings, short paragraphs, captions, and visuals that add evidence rather than decoration.

Closing

state the result, limitations, reflection, and a clear next project or contact action.

Test the portfolio as a product

Check keyboard navigation, focus visibility, headings, links, contrast, text alternatives, zoom, motion preferences, form errors, and small screens. Compress images and avoid autoplay media that slows the first project view. W3C recommends evaluating accessibility early and throughout development. It also notes that automated tools alone cannot determine whether a site is accessible. Combine tools with knowledgeable human review and, when possible, feedback from disabled users.

Use W3C's accessibility evaluation overview for current testing resources.

UX portfolio review checklist

• The first screen says what kind of UX work you do and who it is for.
• Two to four relevant projects are easier to find than a large unfiltered archive.
• Every project identifies the problem, role, team, constraints, evidence, decisions, and outcome.
• Claims, metrics, quotes, shipped states, and responsibilities are accurate and appropriately credited.
• Confidential information, personal data, and internal artifacts have permission to appear.
• Navigation, text, media, forms, keyboard use, zoom, mobile layout, and loading behavior have been tested.
• A person unfamiliar with the work can summarize your contribution after a short review.
• Contact details work, the resume is current, and no unfinished placeholder or broken link remains.

Read Nielsen Norman Group's UX careers report for broader career and portfolio context.

Compare portfolio website templates after your content structure is ready.

See the freelancer portfolio guide when the main goal is winning client work.

Frequently asked questions