UX Designer Portfolio: What to Include and How to Structure It

A UX design portfolio is unlike any other creative portfolio. The work is often invisible — decisions buried inside products people use every day, research that shaped a direction no one ever sees, flows that were simplified because someone argued for the user in a room full of engineers. The final screens tell almost none of that story.

And yet most UX portfolios are full of final screens.

If your portfolio looks like a gallery of polished Figma mocks, you are missing the thing that actually differentiates you as a UX designer: the quality of your thinking. This guide covers what to include, how to structure it, and the mistakes that quietly kill candidacy for senior roles.

Why UX Portfolios Are Different

Visual designers are selling aesthetics alongside their judgment. Illustrators, brand designers, and photographers can lead with finished work because the output is the argument.

UX designers are selling a process. A hiring manager or client looking at your portfolio is asking: How does this person approach a problem? Do they start with research or skip straight to wireframes? How do they handle ambiguity? Do they advocate for users when the stakeholders push back?

A gallery of screens answers none of those questions. A well-structured case study answers all of them.

This is not an excuse to bury your deliverables — final screens, prototypes, and flows still matter. But they should appear at the end of a story, not in place of one.

How Many Projects to Include

Three to five projects is the right range for most UX portfolios. Three is enough to show range without exhausting a reviewer. Five is the ceiling before the portfolio starts to feel like a catalog.

More important than quantity: every project you include should be something you could talk through in a 30-minute interview without losing your audience. If you include a project because it looks impressive but you cannot walk through your reasoning on every major decision, cut it.

Quality of documentation consistently beats quantity of examples. A portfolio with two deeply documented case studies outperforms one with eight surface-level project summaries. Hiring managers have said as much publicly — the Nielsen Norman Group's research on UX portfolios confirms that depth and specificity of process documentation strongly predict interview conversion.

What to Include in Each Case Study

A UX case study that actually works covers these things:

The problem

Start with the problem you were hired to solve. Not "redesign the onboarding flow" — go one level deeper. Why was the onboarding flow a problem? What was the drop-off rate? What were users saying in support tickets? What was the business trying to achieve?

One or two concrete sentences about the problem establish stakes. They tell the reader why this project mattered.

Your role and constraints

Hiring managers reading your portfolio are trying to determine what work was actually yours. Be specific: "I led the research and wireframing. A visual designer handled the high-fidelity screens and I collaborated on prototyping." Do not imply you did everything if you did not.

Also name the constraints: timeline, team size, technical limitations, stakeholder resistance. Constraints make your decisions legible. A design choice that looks obvious in hindsight often was not obvious under real conditions.

Your process (the actual work)

This is where most portfolios are too thin. Show the messy middle.

Include the research artifacts: interview synthesis, affinity diagrams, journey maps. Show early sketches or lo-fi wireframes that did not make it. Document the moments where you changed direction and why. If you ran usability tests, include a key finding and how it changed the design.

The goal is not to include everything — it is to show how you move from uncertainty toward a decision. Two or three specific examples of insight → decision → outcome carry more weight than a list of methodologies you applied.

The solution and final screens

Show the final product clearly. High-quality screens, annotated if the annotations add meaning. Interactive prototypes if the flow or motion is part of what you designed. Walkthrough the key UX decisions: why this pattern instead of another, what you simplified and what you deliberately kept complex.

Outcomes

What changed? If you have metrics, use them. Conversion rate, task completion rate, time on task, support ticket volume, NPS. If you do not have hard metrics — and many UX designers working inside larger product teams genuinely cannot access them — use qualitative outcomes: "The redesigned flow was adopted without modification by the engineering team," or "Usability testing showed all five participants could complete the task without assistance, compared to two of five in the original flow."

Be honest about what you measured and what you could not. Fabricated metrics are easy to spot in an interview and they end conversations immediately.

Handling NDA and Confidential Work

Most experienced UX designers have at least some projects they cannot show publicly. This is extremely common and rarely disqualifies you — but how you handle it matters.

There are several workable options:

Anonymize and abstract. Remove brand names, replace identifiable UI elements, and describe the industry in general terms. "A fintech company in the consumer lending space" is usually sufficient. Check your NDA carefully — many NDAs restrict disclosing client names, not the existence or nature of the work.

Show process work instead of final screens. User interview notes, journey maps, workshop outputs, and research synthesis are rarely protected even when the final product is. You can often show how you worked without showing what you shipped.

Create a password-protected case study. Share the link directly with recruiters or clients during active conversations. This keeps the work off a public index without making it inaccessible.

Our full guide on sharing NDA work in your portfolio covers the legal and practical angles in more detail.

Common Mistakes That Sink UX Portfolios

No context before the solution

The most common structure mistake: opening a case study with a final design. "Here is the new checkout flow. I redesigned it." A reader has no idea why, from what, or with what result. Context is the frame that makes every subsequent image meaningful.

Describing activities instead of thinking

"I conducted five user interviews and created a journey map" is a list of activities. It says nothing about what you learned or how it changed your approach. Describe the insight, not the method. "User interviews revealed that most abandonment happened not during checkout but during account creation — users did not want to commit before knowing the price. That finding redirected us from optimizing the payment form to questioning whether account creation needed to come first at all." That is the kind of entry that makes a hiring manager lean forward.

Treating every project identically

A research-heavy discovery project and a rapid prototyping sprint are fundamentally different kinds of work. Your case study structure should reflect the project, not a template applied uniformly. Vary the depth, the emphasis, and the artifacts based on what the project was actually about.

Missing the "why you" angle

Every case study should implicitly argue for hiring you specifically. What judgment call did you make that someone else might not have? What did you push back on, and why? What made this project hard in a way that is not immediately obvious? The best UX portfolios read like a window into a specific person's way of seeing problems.

The About Page and Bio

Your bio for a UX portfolio should specify your area of focus, not just your title. "UX designer" is not specific enough when every applicant has the same title.

Describe your sweet spot: "I specialize in simplifying complex workflows for enterprise products" or "I focus on consumer-facing mobile experiences at the research-through-delivery stage." Specificity filters in the right opportunities and signals self-awareness.

For ideas on how to frame this clearly, the guide on writing a bio for your website covers the short and long format with examples by profession.

Format and Presentation

UX portfolios do not need to be elaborate. They need to be readable.

Long-form case studies work well on a single scrollable page per project. Keep the reading pace fast: short paragraphs, clear headers, images that advance the story rather than pad the word count. A case study that takes fifteen minutes to read will not be finished by most reviewers.

If you work in a browser-based design tool, a live prototype or interactive Figma link embedded in the case study adds something a static portfolio cannot — the ability to actually experience the flow you designed.

Tools like the UX Collective on Medium publish hundreds of real designer case studies at every career level. Reading ten of them — good and mediocre both — calibrates your baseline faster than any advice can.

For the site itself, mnml.page is built around exactly the structure UX designers need: case study blocks, project grids, and long-form text sections without requiring you to touch code. The default layouts are minimal enough that the work stays center stage.

Before You Launch

Run your portfolio through the questions a hiring manager will ask in the first thirty seconds:

• Is it immediately clear what kind of UX work this person specializes in?
• Can I tell what their role was on each project?
• Do I understand the problem, not just the solution?
• Is there any evidence of outcomes or impact?
• Can I contact them without hunting around the site?

If any of those answers is "no" or "not quickly," fix it before sending the link. The portfolio launch checklist covers the full pre-flight review, including mobile, load time, and form testing.

---

A UX portfolio that shows genuine thinking is rare. Most are galleries of polished work with no story around them. That gap is your opportunity: if you document your process with the same rigor you bring to the work itself, you will stand out from the majority of applicants who are submitting the same type of portfolio everyone else has.

Start with one case study. Do it thoroughly — problem, process, decision rationale, outcome. Then build from there.

Tools & Resources

• Nielsen Norman Group — UX Portfolio Research — NNG's research-backed guidance on what hiring managers actually evaluate in UX portfolios. The specifics on depth vs. breadth are directly useful when deciding what to cut and what to expand.

• UX Collective — A large Medium-based publication with hundreds of real UX case studies from designers at every career level. Reading both strong and weak examples quickly recalibrates your understanding of what good documentation looks like.

• Figma Community — Browse and remix publicly shared design files from other practitioners. Useful for understanding how experienced designers structure and annotate their work before documentation.

• How to Write a Portfolio Case Study — Step-by-step template for writing a case study that documents both the work and the thinking behind it. Applies directly to UX project documentation.

• mnml.page for Designers — Minimal portfolio builder designed for creative and UX professionals. Case study blocks, project grids, and text sections — built to present process-heavy work without getting in the way of it.