A UX portfolio should make your research and design decisions understandable, not merely display polished screens. Explain the task, your contribution, the evidence available and how it influenced the proposal. Keep real observations, assumptions and fictional practice material distinct. A small honest case study is more credible than an elaborate process narrative built around invented users or outcomes.
Build the evidence before polishing the presentation
Begin with a specific user task and the project setting. State whether the work was commissioned, academic or self-initiated. Identify your responsibilities and the constraints you could actually investigate. Do not create a research stage retrospectively just because a case-study template expects one.
For each important design change, connect the observation or constraint to the decision. If participants were involved, describe the method and relevant recruitment limitations while protecting identities. Show alternatives and explain what remains uncertain. A prototype demonstrates a proposal, not successful implementation. The portfolio’s own navigation and readability should support the same attention to users that the case study describes.
| Area | Useful approach | What to check |
|---|---|---|
| Research evidence | Describe the method and observed behaviour with limits | Do not invent participants or generalise a convenience sample |
| Design reasoning | Connect alternatives and revisions to evidence or constraints | Do not present attractive screens as self-explanatory |
| Project outcome | State prototype, implementation and evaluation status accurately | Do not claim business impact from an unlaunched concept |
A fictional worked example
Fictional example: a student explores how volunteers choose shifts for a community event. She observes consenting peers attempt a prototype and records confusion about whether a selected shift is final. She revises the confirmation step and explains the evidence behind that change.
She does not invent a representative persona from three acquaintances or claim the redesign improved real volunteer retention. The page includes the task, prototype states, a small observation summary and limitations. Her contribution is visible, and the reader can see why the revised interaction differs from the first version rather than receiving only a before-and-after image.
Research evidence
Show: Describe the method and observed behaviour with limits
Check: Do not invent participants or generalise a convenience sample
Design reasoning
Show: Connect alternatives and revisions to evidence or constraints
Check: Do not present attractive screens as self-explanatory
Project outcome
Show: State prototype, implementation and evaluation status accurately
Check: Do not claim business impact from an unlaunched concept
Apply the process to your own material
- Frame: Identify the user task, project setting and your actual responsibilities.
- Trace: Connect evidence or explicit assumptions to the important design choices.
- Show: Use selected artefacts and captions to explain alternatives and revisions.
- Qualify: State research limits, current status and what would need further evaluation.
Use an actual piece of your own work for this exercise, or create a clearly labelled practice example. Keep the original and revised versions so you can explain what changed. Ask a reviewer to identify the main contribution without additional explanation, then note where their interpretation differs from what you intended. Revise the evidence or wording that caused the mismatch rather than adding an unsupported claim to make the result sound stronger.
- Frame
Identify the user task, project setting and your actual responsibilities.
- Trace
Connect evidence or explicit assumptions to the important design choices.
- Show
Use selected artefacts and captions to explain alternatives and revisions.
- Qualify
State research limits, current status and what would need further evaluation.
Move forward only when the previous step is clear enough to explain. A finished-looking file still needs a content and usability review.
Review the result before sharing
Review the case study for unsupported research language. Replace “users proved” with a precise account of who did what and what you inferred. Remove unnecessary artefacts that do not support a decision. Ask someone unfamiliar with the project to identify the task, your role and a major revision. Check captions, alt text and the accessibility of the portfolio presentation itself.
A closer check that strengthens the evidence
Review each research artefact for its purpose. A journey map should help explain a task or difficulty; an observation table should support a finding; a prototype should expose a proposed interaction. If you cannot explain how an artefact affected a decision, it may be unnecessary in the case study. This prevents the portfolio from becoming a collection of familiar UX deliverables that appear rigorous without providing evidence. It also gives you more space to discuss one real revision carefully, including the uncertainty that remains and what a further study would need to establish.
Common questions
Do I need a complete design process in every case study?
No. Describe the work that actually occurred and the methods appropriate to the question. Do not fabricate research, personas or testing to fill a familiar sequence of headings. A focused project can be useful when its decisions and limits are clear. The case study should reflect reality rather than imitate an idealised process diagram.
Can I include research with only a few volunteers?
Yes, as a limited practice study if consent and appropriate handling are in place. Explain recruitment and avoid claiming the sample represents all users. The evidence may reveal a problem worth investigating without establishing its prevalence. Do not attach statistical certainty or broad market conclusions that the method cannot support.
Should I show personas in my portfolio?
Only when they were useful and grounded in appropriate evidence, or clearly labelled as assumptions for an exercise. A decorative persona does not demonstrate research by itself. Explain how it affected a decision and what its limitations are. Avoid inventing detailed user biographies and presenting them as findings from interviews that never happened.
How do I present a self-initiated redesign?
State that it was independent and not commissioned or endorsed by the organisation. Explain the public information and assumptions you used. Show the decisions and checks you actually performed, while avoiding claims about internal business goals or real outcomes you could not observe. The honesty of the scope strengthens the sample.
What makes a before-and-after comparison useful?
Explain the problem in the earlier version, the evidence behind the change and the tradeoff in the revised version. Images alone may show a visual difference without demonstrating better usability. State whether the revision was tested and what remains uncertain rather than assuming a more polished appearance proves improvement.
Should I publish interview notes?
Only in a permission-appropriate, privacy-conscious form. A concise anonymised evidence summary may be enough. Do not expose names, sensitive details or recordings merely to make the case study look rigorous. The reader needs to understand the reasoning and limits, not obtain unrestricted access to participants’ personal information.
How much visual polish is necessary?
The work should be clear enough to assess and suitable for the role, but polish should not hide weak reasoning. A research-focused sample may need different artefacts from a detailed UI sample. Explain the capability each case study demonstrates and make the presentation readable without implying every UX role is judged by the same visual standard.
What should I ask a portfolio reviewer?
Ask them to identify the task, your contribution, the evidence behind a major decision and the current outcome. Notice where they have to guess. Request feedback on the clarity of the reasoning rather than only whether the screens look attractive. Revise the confusing connection between evidence and decision before adding more decorative material.
Sources and further reading
Reviewed 7 November 2026. Examples and exercises are original editorial guidance. University advice reflects its own context; employer instructions and local requirements take priority.
Resume & Workplace Desk
MP Job Hub’s organisational byline for presenting genuine work and communicating clearly in professional settings.
Resumes · Portfolio evidence · Interviews · Workplace communication
View profile →Read our research process or request a correction.
