Are most campaign case study mistakes about borrowing someone else's proof?

There are two separate skills here and both fail predictably. Writing a case study goes wrong when the document is built to persuade rather than to be used later. Reading one goes wrong when a description is treated as evidence.

This page covers both. The reading framework is in campaign case studies; what follows is the catalog of ways it gets abandoned.

What to take away

Mistakes when using someone else's

Taking the result as an expectation. A published campaign worked in a context you do not share: a different product, a different offer, a different season, a different everything. It tells you a thing is possible, not what you will get.

Ignoring what else was running. The campaign described is almost never the only marketing that quarter. Where the document does not mention the rest, the main competing explanation has been omitted rather than ruled out.

Accepting a comparison to the previous period. That is a description of a sequence, not a measurement of an effect. Concluding causation from order alone is post hoc ergo propter hoc, and the before-and-after chart is unusually good at making it feel rigorous.

Reading a ratio without its denominator. Any return figure depends entirely on what was counted as cost, and the exclusions are rarely stated.

Generalizing from one market to another. Whether a finding transfers is a separate question from whether it was true where it was measured, and the default answer is that it does not until someone checks; the concept is external validity.

Using a case study to end an internal argument. This is the most common practical misuse. The document arrives as evidence for a decision somebody already wanted to make, and its selection problem is exactly what makes it available.

Mistakes when writing your own for external use

Leading with the number. A striking result with no method attached invites the reader to discount everything, including the parts that were solid.

Describing the campaign and not the mechanism. Readers want to know how it was structured, who did what and in what order. That is the reusable part and it is usually the part cut for length.

Omitting anything that did not work. One honest difficulty makes the whole document more credible, costs almost nothing commercially, and is left out of nearly every case study ever published.

Implying causation with careful wording. Phrases like "coincided with", "saw an increase of" and "helped drive" are doing work the evidence does not support. If the evidence is a correlation, say so.

Naming a partner without asking. Their permission is a contract question and a courtesy question at the same time. What the agreement allows is covered in contracts and disclosure.

Forgetting that the case study is itself promotional. If it is published by the brand and features a partner, the relationship between them is exactly the sort of connection an audience should be told about. The reasoning is the same as for any endorsement, and the current expectations are in the FTC's material on endorsements, influencers and reviews.

Mistakes when writing your own for internal use

The first row has a plain cost. Writing from the reporting deck records what was said, not what happened. A deck notes that posts went live, not that two slipped a week after the brief changed, so the next campaign plans the same window.

The second row does most of the damage. An internal archive holding only wins repeats whatever produced the last win. It never learns what fails.

That failure also shapes what campaign case studies examples reveal, since only wins tend to be written up.

The fifth row is what causes the second. Separate the decision from the outcome: a well-designed campaign that did not work is a good decision with a bad result. Where that is not the culture, nobody will file the useful document.

The story-versus-finding confusion

Confusing a story with a finding. A case study is a narrative, and narratives are persuasive in proportion to how well they are told rather than to how well they are evidenced. That is true of other people's and it is true of yours.

The defense is mechanical. Before citing any case study, internal or external, write one sentence: this claim is X, compared with Y, over window Z. If you cannot complete it, the document is a description and should be cited as one.

A worked version: this claim is a 2.1x return on ad spend, compared with a 1.2x baseline on the same channel over the prior quarter, over a six-week window. The figures are illustrative; the shape is the test.

The methods to complete it are in measurement and ROI. The material for an honest internal version comes from campaign briefs.

Bottom line

When reading, ask what was compared, over what window, with what denominator, and what else was running. When writing, lead with mechanism, not the number, and include one thing that did not work.

Never let careful phrasing imply a causal claim you cannot support, and internally record failures and mid-flight changes, or the archive will teach you nothing.

Common questions

Can a case study ever justify a budget decision?

It can justify trying something. It cannot tell you what you will get, and treating it as a forecast is how programs get over-committed.

Is it worth writing internal case studies for small campaigns?

Yes, and it can be brief. Three paragraphs on what was asked for, what happened and what to do differently is enough.

How do you get honest internal write-ups?

Make them routine rather than exceptional, and never use them in performance discussions. The moment they are evidence about people, they stop being evidence about campaigns.

What if a partner asks not to be named in a public case study?

Respect it. Anonymize the partner and describe the mechanism, which was the useful part anyway.

Should failures be published externally?

Rarely as their own document, and one honest difficulty inside a successful case study is worth a great deal of credibility.