How to Write a UX Case Study When You Don’t Have Metrics

The real problem

Many designers get stuck because they think a case study needs a dashboard number to be credible. Metrics help, but they are not the only way to show impact. If you do not have conversion rates, retention data, or adoption numbers, you can still explain what changed through qualitative evidence, stakeholder alignment, reduced confusion, faster workflows, clearer decisions, or validated learnings.

The missing-metrics problem is a specific version of this: the designer knows something changed, but cannot point to a number that proves it. So the outcome section either gets padded with vague claims, or left empty. Neither is honest, and both undercut the rest of the case study.

What to focus on instead

Writing an outcome section without metrics means being precise about what you do know. Not what you hope happened, not what you estimate might have happened. What you can specifically point to. Stakeholder feedback. A change in how the team made decisions. A user behavior that stopped being a support ticket. These are real outcomes.

Key principles:

• Be transparent about the data you do not have.
• Use qualitative feedback carefully.
• Describe before-and-after user behavior when possible.
• Show what the team learned or decided because of your work.
• Never invent impact to make the case study sound stronger.

A practical structure

Use this simple flow:

1. Context: What was the product and the scale of the work?
2. Problem: What needed to change, and how did you know that was the problem?
3. Role: What were you specifically responsible for?
4. Decision: What choices did you make, and under what constraints?
5. Reasoning: What shaped those choices: research, feedback, or constraints?
6. Outcome: What can you point to honestly, even without a hard number?

The Outcome row is where you apply the most discipline when you have no metrics. Write only what you can point to. If the outcome was qualitative, say what specifically changed and for whom. Precision without numbers is still credible.

Example framing

Weak framing:

I redesigned the flow and improved the user experience.

Stronger framing:

I focused on the onboarding step where users were unsure what to do next. Instead of adding more explanation, I simplified the sequence and made the next action more visible. This helped the team align around a clearer first-use experience.

The stronger version describes what actually changed, at whatever level of specificity is honest. It does not need a dashboard number to be credible. What makes it credible is that the description is specific and the claim is scoped to what the designer can actually account for.

What to avoid

• Do not turn the case study into a gallery of screens.
• Do not hide your role behind vague “we” language.
• Do not overclaim impact if you do not have evidence.
• Do not describe every step equally; highlight the decisions that mattered.
• Do not copy another designer’s case study structure without adapting it to your own project.

Final thought

A case study without metrics can still be an honest one. The question is not whether you have numbers. The question is whether the outcome section describes something real. If it does, the reader will trust it, even without a percentage.

More case study guides

• what hiring managers look for in UX case studies
• showing your contribution in a team project
• preparing your UX case study for a design interview