A case study is a narrative with a job to do: convince a skeptical reader — a program officer, a journalist, a board member — that an intervention actually worked. That means the elements that make fiction absorbing (a clear subject, real stakes, a resolved arc) apply here too, but each one has to be built from verifiable material rather than invention.
A real subject, not a composite
Impact narratives are strongest when they follow one real person, cohort, or site — named where consent allows, described precisely where it doesn’t — rather than an unnamed composite. A composite reads as marketing; a specific, traceable subject reads as evidence.
Stakes drawn from the baseline
What was actually at risk, or actually missing, before the intervention? This has to come from program data or documented context, not from assumed hardship. Overstating the starting point to make the ending look more dramatic is the fastest way to lose a funder’s trust once they check the numbers.
Conflict is the implementation, not a plot device
The obstacles in an impact story should be the real obstacles the team navigated — funding gaps, logistics, a policy barrier, a slow first quarter — not a manufactured complication. Naming what was genuinely hard is what makes the eventual result credible.
An ending with evidence attached
Close on a specific, dated, sourced outcome — a measured change, a documented milestone, a direct quote — rather than a general statement of success. This is also where the narrative and the measurement work should meet: the story’s ending and the report’s headline number should be the same claim, told two ways.
This is exactly what Content Factory’s Impact Story and Impact Report packages are built to produce — narratives constructed from an organization’s own program data, not from invented drama.