Portfolio Development
Write a UX Case Study Without Inventing Metrics
No analytics access, an unshipped concept, a student brief, or confidential results? Build the outcome around evidence you can defend—and name what remains unknown.
The short read
Core move
Replace missing metrics with the strongest evidence you actually have
Label clearly
Separate shipped, tested, proposed, estimated, and confidential outcomes
Add context
Name the source, sample, period, and limits of every result
Never do
Invent numbers or imply a product impact you did not measure
What an Outcome Section Must Do
An outcome section is not a trophy shelf. It helps a reviewer understand what changed, what evidence supports that change, how your work contributed, and what is still uncertain. A precise limitation is more credible than a confident claim you cannot verify.
Use this sentence pattern
We observed [evidence] through [method or source]. This informed [decision or change]. Because [limitation], I would next measure or test [open question].
The Evidence Ladder
Start at the top and use the strongest level available. Lower levels are not fake outcomes; they answer narrower questions. Pair them when that makes the story clearer.
1. Product or service outcome
Examples: Observed changes in completion, conversion, error rate, retention, support volume, or another defined measure.
Caution: Name the period, data source, and your level of influence. Correlation is not automatically causation.
2. Behavioral research evidence
Examples: Task completion, observed errors, comprehension, confidence, or repeated themes from research sessions.
Caution: Include the method, participant count, task, and limits. Do not turn a small study into a population claim.
3. Delivery and adoption evidence
Examples: A direction selected, feature shipped, component reused, workflow adopted, or accessibility issue resolved.
Caution: This shows movement and influence, not necessarily customer or business impact.
4. Decision evidence
Examples: A prototype ruled out a risky approach, research changed the brief, or a constraint led to a better tradeoff.
Caution: Show the evidence that changed the decision, not just the decision itself.
5. Reflection
Examples: What you learned, what remains unproven, and what you would measure or test next.
Caution: Reflection is valuable, but it should not be presented as proof that the solution worked.
Write Only What You Know
Weak: conclusion without traceability
“The redesign made checkout much easier and improved conversion.”
Stronger: observation, source, and limit
“In moderated prototype sessions, six of eight participants completed the revised checkout without facilitator help. The study did not measure live conversion.”
The numbers above are an illustrative writing example, not a recommended sample size or a real project result. Replace them with your own evidence and method.
Student and Concept Work
Label the project near the beginning: course assignment, independent concept, redesign exercise, or client-sponsored student work. Then define the real constraints—time, access to participants, team roles, and what was or was not implemented.
- Do show: decisions changed by research, iterations tied to evidence, critique you acted on, and open questions.
- Do not claim: market adoption, revenue, retention, or organizational impact for a concept that never entered that environment.
- End with: what you would validate before release and what data would tell you whether the design worked.
Confidential and NDA Work
An NDA is a specific agreement, not a generic portfolio rule. Review the agreement and your company's policy, then get written approval for the material you plan to publish. Do not assume that percentages, screenshots, customer quotes, or anonymized details are automatically safe.
If public proof must stay limited, focus on your role, the kind of problem, non-sensitive constraints, decision logic, and a sanitized reflection. A private interview walkthrough is still subject to the agreement; “private” does not mean permitted.
Before-and-After Examples
Instead of: “Users loved it.”
Try: “Four of five interview participants described the revised status language as clearer. This was a directional finding from a small study, so the next step was testing it in the shipped flow.”
Instead of: “The design saved the team time.”
Try: “The engineering team reused the new component across three planned flows, reducing duplicate design and implementation work. We did not measure hours saved.”
Instead of: “Improved completion by 40%.”
Try: “Prototype task completion increased from the first round to the second. Because the participant groups and prototype fidelity differed, I treated the result as directional rather than a product-performance metric.”
All examples in this section are fictional and demonstrate claim structure only.
Plan Better Evidence Next Time
- 1. Name the decision. What choice should the evidence help the team make?
- 2. Define success before designing. Choose a signal connected to the user behavior or service outcome you want to improve.
- 3. Record the baseline and method. Save the source, date range, task, participant criteria, and known limitations.
- 4. Ask about portfolio permission early. Agree on what can be shared, how it can be anonymized, and who approves publication.
- 5. Keep an evidence log. Capture decisions, research notes, implementation status, and outcomes while they are still traceable.
For the full story structure, continue with the UX case study structure guide.
Sources and Further Reading
- Nielsen Norman Group: 5 Steps to Creating a UX-Design Portfolio — portfolio purpose, audience, format, and case-study guidance.
- Nielsen Norman Group: User Experience Careers report — research on what UX hiring teams look for, including reasoning, process, and business understanding.
- GOV.UK Service Manual: Measuring success — defining performance measures around user needs and service goals.
QuestionsAnswers
Case Study Evidence Questions
A few practical details before you keep going
Share this resource
Written by
Nikki KippleProduct Designer & Design Instructor
Designer, educator, founder of The Crit. I've spent years teaching interaction design and reviewing hundreds of student portfolios. Good feedback shouldn't require being enrolled in my class — so I built a tool that gives it to everyone. Connect on LinkedIn →
Too close to your own work?
Send one screen, case study, or URL. We'll show what's working, what's getting skipped, and what to fix next.