The Case Study Is the Strategy

There is a document we produce at the start of every significant engagement that clients never expect: the case study, written in advance. Before the kickoff, before the audit, sometimes before the contract, we draft the story we intend to be able to tell twelve months from now. Company faced X. We did Y. It produced Z, measured this way.

It takes an afternoon. It is routinely the highest-leverage afternoon of the whole project.

Why working backward works

Strategy documents fail in a predictable way: they are compendiums when they should be commitments. Forty slides of market context, personas, and frameworks, with the actual choices smeared thin enough that nobody has to feel the weight of them. Everyone nods, nothing is decided, and the deck goes wherever decks go.

The future-tense case study cannot cheat like that. Its format forces the three confessions every strategy tries to avoid:

• A specific problem. Not "the brand needed refreshing" but a named, costed business problem someone will admit to on the record. If we cannot write this paragraph, the project has no reason to exist yet, and finding the reason becomes the first phase of work.
• A causal claim. The "we did Y, therefore Z" sentence exposes whether anyone actually believes the work will move the number, or whether we are all just hoping proximity implies causation.
• A measurement plan. If the imagined case study says "conversion improved 30 percent," someone has to ask: from what baseline, measured how, against what counterfactual? Asking in month one costs nothing. Asking in month twelve is archaeology, and in this post-attribution era it is often impossible archaeology. Baselines, holdouts, and tracking must exist before the work ships, and the pre-written case study is what surfaces that requirement early.

What it does to the room

The first time we ran this exercise with a client, something unexpected happened. The CMO read the draft and said, "I would not believe this if a competitor published it." That single sentence reshaped the engagement. The claims were too broad, so the scope was too broad, so we narrowed both until the story became one a skeptic would accept. The project that shipped was smaller and sharper than the one that was briefed, and it is the one in our portfolio today.

That is the quiet function of the exercise: it recruits the client's own skepticism as a strategic tool. People will approve vague plans all day, but nobody wants to be the named subject of an implausible story.

The discipline it enforces later

The pre-written case study keeps paying after kickoff. When scope pressure arrives mid-project, and it always arrives, the question becomes "does this addition appear in the story we agreed to tell?" Most additions do not survive that question. When priorities blur, the document is a tiebreaker that predates everyone's current mood.

And when the project ends, the real case study takes an hour to write, because the evidence was designed in rather than excavated out. The delta between the imagined story and the actual one becomes the most honest retrospective the team will ever hold.

An admission

Yes, this is partly a trick. It smuggles accountability into a phase of work that usually runs on optimism, and it makes everyone commit to falsifiable claims while it is still comfortable to disagree. But the best strategic tools are usually tricks of exactly this kind: structures that make the honest conversation easier to have than the evasive one.

Strategy is choice under uncertainty, written down where it can be checked. If the case study cannot be drafted, the strategy does not exist yet. Better to learn that in an afternoon than in a year.