When a case study has no impressive numbers.
A useful case study can explain a difficult decision, show how the interface works, and acknowledge its limits without inventing a dramatic result.
Some projects come with a clear measurement plan. Others do not. A small cultural website may never have had reliable analytics, and a new publication has no previous version to compare against.
That leaves plenty worth explaining. A reader can learn from the brief, the constraints, the decisions, and the work itself.
Show the decision
“Improved the editing experience” is vague. Explaining that event dates now have their own fields, while venue details are managed in one place, gives the reader something to inspect.
A screenshot can show the relationship between those fields and the page. A short account of the alternatives can explain why the chosen structure fits the team.
Separate an intention from a result
A clear form is intended to help people make an enquiry. That does not establish an increase in enquiries. A smaller image file may reduce the amount transferred, but it does not establish how fast every visitor will experience the page.
When a result has been measured, describe the method and its limits. When it has not, keep the language close to what the work demonstrates.
Include the compromise
A project becomes more interesting when its boundaries are visible. Perhaps the catalogue has no checkout because the studio handles orders personally. Perhaps a tightly controlled page builder gives editors fewer layout choices in exchange for consistency.
Those decisions help a prospective collaborator understand how I work. A case study earns its space by making the project understandable, even when there is no percentage large enough to turn into a headline.