There is a particular kind of agency presentation that has become universal. It goes like this: here is the client, here is the problem, here is what we made, here are the results. Neat. Clean. Completely unreadable as a story.
A story requires something else. It requires a moment of genuine conflict — not "the client needed better awareness" but something that was actually at stake, something that could have gone wrong, something that did go wrong. It requires a character who wants something and meets resistance. It requires the reader to care about the outcome before they are told what it is.
Most agency case studies fail this test because they are written backwards. The outcome is known before the story begins, so all tension drains away. We knew we would succeed. We always know we will succeed, in the retelling. The question is how to make someone who wasn't there feel the uncertainty that was actually present.
The answer is specificity. Not "we identified a unique insight" but the specific thing — the conversation, the brief, the offhand comment from the client that suddenly reframed everything. The brief that everyone ignored is usually the only one worth reading. Because it contains the thing no one thought was important, which is almost always the thing that matters most.
We have made it a practice at SFS to keep the brief. Not the final version — the early one, with the crossed-out sections and the contradictory requirements and the aspirations that don't quite cohere. That document is where the story is. The polished brief is already a sanitised version of the problem. The early one still has the mess in it.
Mess is where stories live. The clean version is what you tell after you know how it ends.