Write a UX portfolio case study for [PROJECT OVERVIEW] using my project evidence in [PROJECT NOTES AND ARTIFACTS]. The intended reader and portfolio context are [AUDIENCE AND PORTFOLIO GOAL]. My role, team, timeline, and constraints are [ROLE AND CONSTRAINTS]. The verified outcomes and unresolved limits are [OUTCOMES AND LIMITATIONS]. Create a case study that demonstrates judgment and contribution, not a retrospective success story. Identify the user problem, business or product context, evidence available at the time, alternatives considered, decisions made, and what changed after release. Distinguish my work from the team’s work. If research was limited, describe the limitation and how it affected the decision rather than pretending the process was complete. Produce 800 to 1,100 words in these sections: 1. Snapshot: product, users, problem, my role, team, duration, and one verified outcome. 2. Context and problem: the user need and why it mattered, supported by supplied evidence. 3. Discovery: research methods, key findings, and what remained uncertain. 4. Framing and decisions: requirements, trade-offs, alternatives rejected, and the rationale for the chosen direction. 5. Design and validation: the most important flow or interaction, feedback or usability evidence, and resulting iterations. 6. Outcome and reflection: measured results where supplied, limitations, and what I would test or change next. Suggest bracketed locations for visuals such as [INSERT BEFORE/AFTER FLOW] only where an artifact would clarify the story. Do not invent user quotes, research sessions, accessibility testing, metrics, business impact, stakeholder approval, or design tools. Before answering, flag unsupported outcome claims and confirm that each section shows evidence, a decision, or a learning. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [PROJECT OVERVIEW] | Describe the product, project goal, users, and the feature or experience you worked on. | Redesign of the appointment-rescheduling flow for a regional clinic network’s patient portal. |
| [PROJECT NOTES AND ARTIFACTS] | Paste research notes, design rationale, testing notes, links or descriptions of artifacts, and project chronology. | Reviewed 46 support tickets, interviewed 6 patients, mapped the existing three-screen flow, and ran 5 moderated prototype sessions. Patients wanted to see provider availability before cancelling. |
| [AUDIENCE AND PORTFOLIO GOAL] | State who will read the case study and the role or capability you want it to demonstrate. | Hiring managers for mid-level product designer roles; demonstrate research synthesis and work with operational constraints. |
| [ROLE AND CONSTRAINTS] | State your responsibilities, collaborators, timeline, technical or organizational constraints, and decision authority. | I was the product designer on a team with one PM and four engineers over six weeks. Scheduling API could return availability only by provider and day. |
| [OUTCOMES AND LIMITATIONS] | List verified metrics, feedback, release status, what was not measured, and remaining limitations. | Released to 20% of users; support contacts about rescheduling fell 18% over four weeks. We did not measure completed reschedules by user segment. |
How to use
- Collect your project timeline, research evidence, design files, and outcome data before drafting; the strongest narrative comes from contemporaneous records.
- Paste rough notes rather than polishing them first, then compare the draft’s sequence of decisions with what actually happened.
- Replace broad visual placeholders with specific artifacts that prove a decision, such as an annotated flow, research affinity map, or test iteration.
- Follow up with: “Cut this to 650 words for a hiring manager scan while preserving the problem, my decision, and the verified outcome.”
Variations
Case study outline
Use this before you begin writing a portfolio narrative.
Build a UX case-study outline for [PROJECT] from [EVIDENCE AND ARTIFACTS]. My role and constraints were [ROLE AND CONSTRAINTS], and the audience is [AUDIENCE]. Return a section-by-section narrative arc, the proof each section needs, suggested visuals, and a list of evidence gaps to resolve before writing. Prioritize problem framing, decisions, trade-offs, and learning over a screen-by-screen tour. Do not assume research, metrics, or launch results that I have not supplied. Flag where team work and my individual contribution must be distinguished.
Research narrative
Use this when research is the strongest part of the project.
Write a 600 to 800 word UX research section for [PROJECT] using [RESEARCH NOTES]. Explain the decision the research needed to inform, recruitment or data source, methods, findings, limitations, and how findings changed [DESIGN DECISION]. Include only actual participant counts, quotes, and findings supplied in my notes. Do not imply statistical representativeness from a small qualitative sample. End with remaining uncertainties and the next validation step. Check that each finding is connected to evidence and a product decision.
Interview version
Use this to prepare a spoken walkthrough.
Turn [UX CASE STUDY NOTES] into a 5-minute interview walkthrough for [TARGET ROLE]. Structure it as context, problem, my role, evidence, key trade-off, outcome, and reflection. Write it in spoken first person and include two likely interviewer follow-up questions with evidence-based answers. Make clear what I personally did versus what the team did. Do not invent impact figures or research detail. Before answering, identify claims that need a portfolio artifact or metric to substantiate.
Tips
- Lead with the user and product problem, then show the decision trail; a gallery of polished screens does not establish design judgment.
- Use a research finding only when you can explain the method, participant or data source, and how it changed a decision.
- Show constraints such as legacy systems, policy, or time limits when they shaped the solution; constraints make trade-offs legible.
- Report outcomes with a timeframe, metric definition, and caveat, and state plainly when a project was not launched or results were not measured.
FAQ
How long should a UX case study be?
A portfolio version is often 800 to 1,200 words plus purposeful visuals. Recruiters should be able to grasp the problem, your role, decision, and outcome quickly.
What if the project did not have metrics?
Do not invent them. Use verified qualitative feedback, release status, or learning, and state the measurement you would run next.
Can I include confidential work?
Only with permission. Anonymize product details where necessary, remove sensitive data, and avoid showing internal research or screens that are not cleared for sharing.