Stop designing case studies. Start designing arguments.
The traditional case-study template — challenge, approach, solution, results — is so widespread it feels like a law of nature. It is not. It is one specific narrative structure, inherited from consulting decks, optimized for showing process. And it is the wrong structure for an agency website.
This is the essay where we explain why our case studies are getting rewritten this quarter.
The traditional case-study format (and why it fails)
The four-act template — Challenge → Approach → Solution → Results — is a chronology. It tells the story of the project in roughly the order it happened.
The problem: nobody reading a case study is interested in chronology. They are interested in whether you can solve their problem. The chronology buries the answer to that question in the middle of the article, behind setup the reader has to wade through.
A typical reader's actual journey:
- They land on the case study from a Google result or a homepage link.
- They scan for proof: "Did they solve a problem similar to mine?"
- If proof is visible, they read more.
- If proof is buried, they bounce.
The four-act format puts the proof in act four. Most readers don't make it.
What an argument-shaped case study looks like
An argument-shaped case study reverses the order. It starts with the conclusion — the proof — and then unpacks the reasoning behind it.
The structure we now use, in order:
- The headline outcome — one sentence, with numbers if possible
- The argument — the insight that produced the outcome, in one paragraph
- The proof — the specific work, with visuals
- The why — what was non-obvious about the approach
Put the two structures side by side and the difference is mostly about what each one asks the reader to do first:
| Four-act chronology | Argument-shaped | |
|---|---|---|
| Opens with | The client's situation before you arrived | The outcome you produced |
| Reader's first question | "How long is this?" | "Could they do that for us?" |
| Proof appears | Act four | The first line |
| Organizing logic | The order things happened | The order a sceptic needs convincing |
| Rewards | Readers who finish | Readers who scan |
| Fails when | The reader leaves early — most of them do | You have no outcome worth leading with |
The last row is the honest catch. Argument-shaped case studies are harder to write, because they will not let you hide a project that didn't produce much.
The reader sees the headline outcome on screen one. If it's relevant to them, they keep reading. If not, they bounce — which is fine. The case study has done its job.
The 4 questions a great case study answers
When we audit our own case studies now, we test each one against four questions:
1. What did the client get out of this?
Not "we delivered a brand identity system." That's the deliverable. The outcome is what changed for the client because of the deliverable. "Their close rate on enterprise demos went from 12% to 28% in the quarter after launch." "They were able to onboard their first three Fortune 500 clients with the new positioning." Outcomes are measurable changes in the client's world, not artifacts produced by us.
2. What was non-obvious about how we got there?
If the approach is "we did research, then design, then refinement," there's no insight to communicate. The case study has nothing to teach. But almost every project we've worked on contains one specific insight that wasn't obvious at the start — a reframing of the problem, an unusual constraint we accepted, a decision to not do something the brief asked for. That insight is the case study.
3. What does this tell a future client about how we work?
A case study isn't a portfolio piece. It's a sample of working with us. A potential client reading it is asking, "If I hire them, what's the texture of the engagement?" The case study should leave them with a clear sense — confident about some things, aware of constraints about others.
4. What would I, as a designer, want to take away from this if I read it?
A case study that other designers can learn from is also a case study that clients can trust, because it reveals craft. We write our case studies to be useful to peers, not just to potential clients. That double-purpose tightens the writing.
A case study isn't a portfolio piece. It's a sample of working with us. — Internal case-study principle
The Wealthora case study, redesigned
The previous version of our Wealthora case study followed the four-act template. It opened with "Wealthora is an enterprise asset management platform redefining…" Three paragraphs of setup. Then the brief. Then the design. Then a results section at the bottom that nobody made it to.
The redesigned version opens with: "Wealthora's close rate on enterprise demos went from 18% to 41% within six months of the new design system shipping."
That's the first sentence. The rest of the page argues why — the specific design insight that produced that lift. The visual work is downstream of the argument, not the lead.
Templates and traps
The argument-shaped case study has two failure modes to watch for:
Trap 1: Inflating the outcome. If you don't have a real measurable outcome, do not invent one. "Increased engagement" is meaningless. "Achieved positive client sentiment" is fluff. Better to lead with a qualitative claim that's specific — "The client now uses this brand system across three product lines without modification" — than to lead with a hollow number.
Trap 2: Substituting opinion for insight. The argument has to be specific. "We focused on simplicity" is opinion. "We removed three of the seven menu items from the navigation because user research showed task-completion improved with fewer choices" is insight. The first is decoration. The second is craft.
A good case study should communicate the outcome and the insight within 30 seconds of landing on the page — usually within the first scroll. Read your own case studies on a phone with a 30-second timer. If you can't answer "what did the client get?" and "what was non-obvious about how?" in 30 seconds, the structure is wrong.
Why agencies resist this
The four-act template is comforting because it shows us — the agency — doing work. Our process. Our approach. Our research. The argument-shaped template shows the client — their outcome, their world, their problem.
That's the right framing for marketing, even though it feels counterintuitive. Clients don't hire agencies because the process is interesting. They hire agencies because they trust the outcome.
If you only have time to fix one thing on your agency website this quarter, fix the case-study lede. Replace "Client X is a leading provider of…" with "Client X's [specific metric] improved from [number] to [number] within [timeframe]." Then watch your demo bookings move.
