Look for the actual problem
A strong case study explains the users and context, the problem the team addressed, and why the work mattered. Generic statements about “improving experience” are hard to compare.
Find the agency’s specific role
Was the team responsible for research, product strategy, interaction design, visual design, engineering, or a portion of those? Confirm the role from a dedicated case page or another direct source.
Distinguish outputs from outcomes
A prototype, design system, or shipped interface is an output. Changes in task success, conversion, retention, or support volume are outcomes. Check who reported an outcome, when it was measured, and whether the source states a baseline.
Notice what is missing
Case studies are selected stories. They may omit failed approaches, implementation constraints, or later results. Record limitations as questions for the agency, not as assumptions about quality.
This guide is original editorial advice, not a substitute for reviewing project sources and proposals specific to your work.