The anatomy of a credible case study

The genre has a problem. Most published case studies tell you that a transformation happened, surface a logo, drop a quote, and end with a metric the reader cannot verify. They are decorations, not evidence.

The buyers I respect — heads of data, CTOs, COO-types — read those and quietly rule the consultant out. The case study is a credential. If it does not read like one, it is doing the opposite of its job.

The mindset shift is to write for the operator who will read your work and try to copy the playbook. They want to see the model under the metric. Concept, logic, physical — the same discipline a senior architect applies to a system, applied to the story of how the system got built.

If a serious reader cannot reverse-engineer the engagement from your case study, the case study is theater.

1. The metric without a model. '4× revenue' with no causal chain.

2. The model without a metric. Beautiful diagram, no P&L impact.

3. The hero narrative. 'I joined and fixed it' — no team, no constraints, no honesty about what almost did not work.

4. The stack list dressed as a story. Logos in a row are not an architecture.

Concept — what worldview did the engagement adopt? What is the one-paragraph mental model that explains every decision that followed?

Logic — what is the logical model? Data flows, process logic, the entities and the relationships. This is where most case studies should add a diagram and almost none do.

Physical — what was actually shipped? The stack, the team, the operating cadence. The boring details a serious reader uses to evaluate whether the work was real.

Overview — the brief, in one paragraph the client would sign off on.

Challenge — the structural friction, framed as the engagement saw it.

Approach — the sequence of moves, in order, with their constraints visible.

Concept / Logic / Physical — the three-layer breakdown.

Outcome — numbers, deliverables, what shipped.

Reflection — what stuck, what almost did not, what would change next time.

Start with the concept. One paragraph, written as if it were the cover memo. If I cannot write it, I do not yet understand the engagement.

Sketch the logical model on paper before any prose. If the entities and the flow are not stable, the prose will paper over the gaps.

Inventory the physical reality from notes, not memory. Stack, team, cadence — checked against the actual artifacts that shipped.

Only then write outcome. Pick numbers I am willing to defend in a deposition; ignore the rest.

The case study is the only artifact most prospects will ever read. It either reads like a credential or it does not. Concept, logic, physical is the discipline that separates the two. Everything else is jacket choices.