What's your best advice on showing metrics for a hypothetical case study?

Published on:

Do not index
Do not index
ℹ️
For context: There might be some metrics from user testing, but they just never feel that impactful.

How to showcase metrics for a hypothetical case study (or an unlaunched product)

For hypothetical case studies it’s a lot harder. The goal is to communicate that this was a job well done.

You can think of some numerical metrics:

  • Number of users interviewed (or feedback received)
  • Number of screens designed (or iterations)
  • Number of hours spent on the project
  • Anything that's quantifiable—which implies the project was impactful

If you don’t have hard numbers to show, try these alternatives:

  • Test metrics: example could be usability test first round vs second round, A/B testing results
  • Positive reviews or feedback (direct quotes often work the best)

You should also brainstorm potential impacts once the solution is released:

Example: If a user tells you in an interview that they spend 10 hours doing X, and your solution aims to cut that down to 5 minutes
↳ You could frame it as: 'Potential hours saved: 9.9’

Keep in mind, businesses value impact in two ways:

  • Increasing revenue (e.g., driving sales)
  • Saving resources (e.g., optimising processes)

Learn to write engaging case studies with Anfisa ⤵️

Video preview
 

Get free UX resources

Get portfolio templates, list of job boards, UX step-by-step guides, and more.