Case Study Template: A Project Write-up People Actually Read

Topic:

Many portfolios jump straight to final screens and skip the “why”. But context and trade-offs are what show maturity. A consistent template helps readers scan quickly and still understand the work.

A simple case study template:

• Context: who the user was, what hurt, why now.
• Goal: how success is measured (a metric or clear signal).
• My role: ownership and collaboration.
• Constraints: time, data, tech, policy, process.
• Options: 2–3 approaches and trade-offs.
• Decision: why you chose the path.
• Execution: key flows/screens, not an entire design dump.
• Validation: tests, feedback, what changed.
• Outcome: numbers, or at least measurable impact (fewer tickets, faster onboarding).
• Next steps: what you’d do next and how you’d measure it.

My opinion:

• The best case studies are understandable in a minute, with deeper detail available after.
• Metrics are great, but you can still show impact without vanity numbers: before/after, quotes, decisions, and lessons learned.