UX Research Portfolio: How to Show Research That Changed Decisions

A research case study opens with twelve sticky-note photos, an affinity map and a list of methods. The hiring manager scrolls past all of it looking for one thing: what changed because of this research? A UX research portfolio wins when the answer is on the first screen.

Learn on the move: press play and turn your commute, walk or drive into time that grows your design career.

Share
Share

In this guide I go through what a research case study should show, how to present methods without drowning the story, and how to handle work under NDA.

What Makes a Strong UX Research Portfolio?

A strong UX research portfolio shows research that changed decisions. Each case explains the question the team needed answered, how you chose the method, what you found and what the team did differently because of it. Methods matter as proof of judgment, and the decision is the headline.

Think of an investigative journalist. Readers care about the sources, and they remember the story that changed something.

The Structure of a Research Case Study

  1. The decision at stake: what the team had to decide and why it was uncertain.
  2. The research question: one or two questions, written plainly.
  3. Method and why: what you chose, with how many participants, and why it fit the time and budget.
  4. Key findings: three at most, each with one quote or one data point.
  5. What changed: the decision, design or roadmap change, and what happened next.

How to Present Methods Without Losing the Reader

Keep the method to a short block with the essentials: type, participants, duration. Explain the choice in one sentence, for example small usability rounds because, as Jakob Nielsen showed in 2000, five users find about 85% of usability problems. Put the artifacts, such as discussion guides and synthesis boards, in an appendix or a linked page.

Showing Impact and Handling NDA Work

Impact can be a changed decision, a feature the team stopped building or a metric that moved. If the work is under NDA, change the product name, blur sensitive screens and describe the problem and outcome in general terms. Reviewers care about your thinking far more than the brand.

For more ways to present results, read how to show impact in a UX case study.

A Quick Review Checklist

  • Does each case name the decision the research informed on the first screen?
  • Is there at least one real quote or data point per finding?
  • Is the method explained in a short block, with the reason for choosing it?
  • Does each case end with what changed?
  • Is sensitive data removed or anonymized?

Where to Start

Do your research cases open with methods instead of decisions? Does any finding lack evidence? Are you moving into a research or research-heavy design role?

Start with the free course Building Your Design Portfolio, see a short format in the UX portfolio PDF guide, read UX portfolio case studies and check your Research & Insights score with the UI/UX skills assessment.

Questions Designers Ask

What Should a UX Research Portfolio Include?

Two or three case studies that show the decision at stake, the research question, the method and why, key findings with evidence and what changed.

How Do You Present Research Methods in a Portfolio?

Keep them to a short block with type, participants and duration, explain why you chose them and link the detailed artifacts separately.

How Do I Show UX Research Done Under NDA?

Rename the product, blur sensitive screens and describe the problem and the outcome in general terms; your reasoning matters more than the brand.

How Many Participants Should a Usability Study Have?

Jakob Nielsen's 2000 analysis showed that five users find about 85% of usability problems, so several small rounds often work better than one large one.

Is There a Free Course on Building a Portfolio?

Yes. Building Your Design Portfolio on DesignPath is free, with practice tasks that take you to a reviewed case study.

Sources

  1. DesignPath free course Building Your Design Portfolio: description and lessons. designpath.app/free-ux-design-courses
  2. Jakob Nielsen, Nielsen Norman Group, 2000. Why You Only Need to Test with 5 Users. www.nngroup.com/articles/why-you-only-need-to-test-with-5-users/
Found this useful? Pass it on.
Share
Reading is the easy half

Practice This with a Plan Behind It.

DesignPath turns notes like these into real exercises, feedback on what you make, and portfolio cases you can send to a hiring team.