How to Show Impact in a UX Case Study When You Have No Metrics

This is the most common gap I see in junior and mid-level portfolios, and it has a practical fix. Mentors see it all the time too: portfolio and resume reviews are the most booked topic on ADPList, 30% of tagged sessions in the US over the past year.

How Do You Show Impact in a UX Case Study Without Metrics?

Show the decision you made and the evidence that it worked. When numbers are missing, behaviour from a usability test, quotes from users or stakeholders, a before and after, adoption by your team, and a decision that changed because of your work all count as impact. Name the evidence, name who saw it, and connect it to the problem you set out to solve.

Build Your Case the Way a Lawyer Does

In court, fingerprints settle a case quickly, and plenty of cases are won without them. A lawyer brings witnesses, photos taken before and after, and a clear timeline, and lets the jury connect them. A case study works the same way. Metrics are the fingerprints. When you don't have them, you build the case from everything else, and you present it in an order the reader can follow.

Six Kinds of Evidence, From Strongest to Weakest

1. Observed behaviour: in a usability test, 5 of 6 people finished the task that 2 of 6 finished before. Small numbers you collected yourself still count.
2. A decision that changed: the team dropped a planned feature, or moved it up the roadmap, because of your research or your prototype.
3. Adoption: other designers or developers reused your component, pattern or template.
4. Words from the people affected: a quote from a user, a support agent or a product manager about what changed for them.
5. Before and after: two screens side by side, with the reason for every change written next to it.
6. Process quality: a clear problem statement, the options you rejected and why. This is the weakest proof of impact and the strongest proof of thinking, so keep it, and put it after the evidence above.

Use the highest kind you honestly have, and combine two when you can. A before and after plus a quote from the product manager reads stronger than either one alone.

A One-Sentence Impact Formula

When you sit down to write the impact section, start from this sentence and fill it in:

Because of [the decision you made], [who] could [do what], which [result for the user or the business].

For example: "Because we moved the price above the fold, people in our test stopped scrolling back to find it, and the product manager put the same pattern into three other checkout screens." No dashboard needed, and the reader sees a decision, a behaviour change and adoption in one line.

What to Do While the Project Is Still Running

Most missing impact is lost at the end of a project. Three habits keep it:

• Screenshot the before: take it on day one, before anyone changes anything.
• Run one small test: even five people on a prototype give you behaviour to report.
• Write down reactions the day they happen: the stakeholder who said "this finally makes sense" will not remember the sentence in three months.

These habits are part of the case study structure in the free DesignPath course Building Your Design Portfolio, our course of the year, in the course library. The lesson Case Studies That Get Read covers the full order of a case.

Where the Impact Goes in the Case

Put it in two places. One line at the very top, right under the project title, so a recruiter who reads for thirty seconds still sees what changed. Then the full evidence at the end, after the decision it supports, so a hiring manager who reads every word sees the chain from problem to result.

The top line is the formula sentence, shortened. The end section holds the evidence itself: the test result, the quote, the before and after. Keep both honest. If the feature had not shipped when you left, say what you tested and what you expected, and label it as expected.

"My Project Is Under NDA"

Then describe the problem in general terms, blur or redraw the screens, and keep the evidence. "A B2B scheduling tool for clinics" tells a hiring manager enough. What they want to see is how you reached the decision, and in most cases you can describe your reasoning without naming the client. When in doubt, ask your former manager which details you can share.

Make Your Case Study Prove Something

Do you have a project whose impact section is empty right now? Did something change after your work shipped, even without a number? Would a clear order of evidence make that section easier to write?

If that is three yeses, open the guide to portfolio case study structure and rebuild one case with the formula above, or ask for portfolio feedback from a senior designer before you send it out. For more ux designer portfolio tips, the portfolio page walks through every section of a case.