The most persuasive part of a case study is often not the final screen but the outcome showing what changed because of the work. Even when revenue metrics are unavailable, you can often measure behavior, efficiency, error rates and learning.

Define the baseline

To demonstrate an outcome, you first need a baseline. Record pre-project values such as completion time, support requests, conversion rate or task success in usability testing.

  • Show percentage change together with raw numbers where possible.
  • State the time period over which the outcome was measured.
  • Separate effects that cannot be directly attributed to your work.
A strong case study proves not only what you did, but why it mattered.