Tagline for skimmers, more in depth than the Sub-title
(3–4 lines max. Written for a 10-second skimmer.)
- Problem: What was broken or missing, in plain language.
- What I did: Your specific intervention — not “led UX” but the actual design move.
- Outcome: The most concrete result you can honestly claim.
Problem
Problem statement hook, one sentence.
Problem description section: 2–3 paragraphs
- What users were experiencing — grounded in observation, data, or research, not assumption
- Why it mattered — the business or human stakes, not just the UX inconvenience
- What had been tried before, or why it hadn’t been solved yet — this shows you understood the terrain
Constraint hook, one sentence.
(A short list — each constraint paired with its design implication)
For each constraint, two sentences:
- The constraint: e.g. “No access to end users directly during the project.”
- What that meant for my decisions: e.g. “I leaned heavily on support ticket analysis and internal SME interviews as a proxy for user feedback, which shaped how I framed the problem.”
Aim for 3–5 constraints. Don’t list constraints you didn’t actually adapt to.
Process
(This is the heart of the case study — prioritize decision points over activities)
Rather than a chronological diary of what you did, structure this around 2–3 pivotal decisions:
Decision point format:
- The fork: What were the options you were genuinely weighing?
- What I chose and why: The reasoning, not just the outcome
- What I learned or what changed: Did this decision get validated, challenged, or revised?
Supporting artifacts (sketches, flows, research synthesis) go here — captioned with the decision they informed, not just what they depict.
Solution
(Show and explain, not just show)
For each key part of the final design:
- A visual (screenshot, flow, prototype)
- A caption that explains the design decision, not just the screen contents
Bad caption: “The remediation summary screen.”
Good caption: “A summary card surfaces before any destructive action — added after testing showed users were acting without reviewing context first.”
Outcome
Result
(Be honest; be specific; don’t oversell)
Structure it in three parts:
- What shipped — exactly what went live, including scope limitations
- What we measured or observed — quantitative if you have it, qualitative if you don’t, but be explicit about which it is
- What I’d do differently — one or two honest observations. This signals maturity more than any metric.
Reflection
Reflection
(1 short paragraph)
What did this project teach you about design, users, or how you work? How did it shape something that came after? This isn’t a summary — it’s a forward-looking close. Write it in first person and make it specific to this project, not generic.
