CASE STUDY TEMPLATE
PROJECT TITLE
PROJECT SUMMARY — Use one concise paragraph to explain the product, audience, problem space, and why the work mattered.
TAG ONE
TAG TWO
TAG THREE
TAG FOUR
ROLE
Your role and scope
TEAM
Collaborators or stakeholders
TIMELINE
Project duration or phase
OUTCOME
Result, learning, or impact signal
HERO PRODUCT SCREENSHOT
Place the primary product screen, workflow overview, or case-study cover image here.
CASE STUDY OVERVIEW
A reusable UX case study framework
Use this section to summarize the problem, audience, solution direction, and product value without overstating metrics.
Challenge
Describe the user, business, or workflow problem the project needed to clarify.
Users
Name the primary users, stakeholders, permissions, roles, or teams affected by the work.
Solution
Summarize the design direction, product framework, or workflow structure you created.
Product Value
State the expected value, decision quality, efficiency, visibility, or adoption signal honestly.
OPTIONAL SYSTEM, ECOSYSTEM, OR WORKFLOW DIAGRAM
Use this area for a simple architecture map, workflow model, product ecosystem, or process artifact.
PRODUCT CONTEXT
Explain what changed, why it mattered, and how the product evolved
Use this section for modernization, redesign context, platform migration, or product progression.
Before
Describe the legacy state, pain points, constraints, or fragmented workflow.
After
Describe the new product structure, workflow clarity, system model, or user benefit.
01 — Starting point
02 — Product framework
03 — Scalable direction
UX FOCUS
Summarize the product-design decision that helped users understand, complete, or trust the workflow.
UX ARCHITECTURE
Map the product areas, workflow structure, and decision model
Use these cards to explain how the product was organized into clear user paths or system areas.
01 — Product Area
Describe one major workflow, product area, or module.
02 — Product Area
Explain the data, actions, states, or permissions involved.
03 — Product Area
Clarify how this area supports the broader product flow.
04 — Product Area
Use this card for exception handling, admin flows, or adjacent product areas.
OPTIONAL CONNECTORS — Use concise labels or relationship notes here if the product areas depend on each other.
UX FOCUS — Summarize how the architecture reduced ambiguity, improved navigation, or made complex work easier to reason about.
USER CONTEXT
Define the people, goals, and UX needs behind the workflow
Use these cards for roles, personas, permission groups, or operational responsibilities.
Role
Goal: What this person is trying to accomplish. UX Need: What the interface must make clear, fast, or trustworthy.
Role
Goal: Add the role’s priority. UX Need: Add the decision, action, or visibility need.
Role
Goal: Add the work context. UX Need: Add the constraint, error risk, or collaboration need.
Role
Goal: Add the responsibility. UX Need: Add the information architecture or system-feedback need.
Supporting takeaway — Explain how role context shaped the product structure, permissions, language, or interaction model.
WORKFLOW DEEP DIVE
Reusable deep-dive section with media on the left
Use this section when the screenshot or artifact should lead and the insights support it.
WORKFLOW SCREENSHOT
TAGS: workflow · data · states
Insight One
Explain one decision, constraint, or pattern shown in the screenshot.
Insight Two
Describe how the interface helps users act, recover, compare, or decide.
Insight Three
Summarize the system, workflow, or product pattern this view demonstrates.
UX FOCUS — Explain the key experience principle this deep dive proves.
WORKFLOW DEEP DIVE
Reusable deep-dive section with media on the right
Use this mirrored section to vary pacing while keeping the screenshot dominant.
TAGS: interaction · validation · recovery
Insight One
Add the first product or UX decision this view supports.
Insight Two
Explain what users needed to compare, confirm, or complete.
Insight Three
Use this card for exceptions, empty states, permissions, or handoff details.
WORKFLOW SCREENSHOT
UX FOCUS — Explain what this view teaches about the project’s product logic.
TWO-STATE COMPARISON
Compare two related states, views, workflows, or product moments
Use this for before/after views, desktop/mobile, workflow states, or two connected product areas.
BEFORE STATE
AFTER STATE
What changed
Describe the meaningful difference between the two states.
Why it matters
Explain the user, operational, or product value of the change.
What to evidence
Add qualitative feedback, usage signal, shipped scope, or measurable result if available.
DESIGN SYSTEM / UX PRACTICES
Capture reusable patterns that made the work scalable
Use these cards for patterns, practices, components, interaction models, and design-to-development details.
UX Practice
Name a reusable pattern or design decision.
UX Practice
Explain how the pattern helped users or teams.
UX Practice
Use concise guidance, not fake project claims.
UX Practice
Describe interaction states, validation, navigation, or layout rules.
UX Practice
Add design system, content, or component contribution.
UX Practice
Describe what made the solution reusable or maintainable.
UX Practice
Add accessibility, responsive, or edge-case guidance.
UX Practice
Use this card for documentation or handoff systems.
UX FOCUS — Explain how reusable patterns improved quality, speed, consistency, or implementation clarity.
PRODUCT VALUE
Document outcomes honestly without inventing metrics
Use these cards for qualitative impact, adoption signals, measurable results, evidence, or learnings.
Product Value
Describe the outcome in plain language without overstating certainty.
User Value
Add evidence from research, usability, support, or stakeholder feedback.
Business Value
Use this for adoption, efficiency, risk reduction, or product alignment signals.
Evidence
Point to evidence: interviews, shipped work, analytics, testing, or adoption notes.
Learning
Add what the work clarified about users, systems, or product direction.
Next Step
Use this for what shipped next, what changed, or what remains open.
EVIDENCE NOTE — Add qualitative impact, adoption signals, measurable results, research findings, or honest limitations here.
MY CONTRIBUTION
Clarify your role, decisions, and ownership
Use this section to separate your contribution from team outcomes or company-wide work.
MY CONTRIBUTION — Briefly summarize your responsibilities, product decisions, collaboration model, and artifacts you personally drove.
Workflow Architecture
Add how you mapped, structured, or simplified the workflow.
UX Design
Add screens, flows, prototypes, or design system work you created.
Interaction Patterns
Add states, validation, navigation, actions, or recovery patterns.
Research
Add discovery, interviews, audits, synthesis, or validation work.
Product Ownership
Add prioritization, stakeholder alignment, roadmap, or scope decisions.
Design-to-Development
Add documentation, component specs, QA, or delivery collaboration.
CASE STUDY SUMMARY
Close with the clearest product story this project proves
Summarize the case study’s strongest evidence, product clarity, and your role in the result.
Product Story
What this project demonstrates.
UX Strength
The UX capability shown here.
Evidence
The proof or signal to cite.
Contribution
The role you personally played.
“Use this quote space for a concise reflection on what the project proves about your product design approach.”