Case Study Intelligence Framework — Editorial Intelligence

Version 0.2 — experimental framework. Refined through live customer-story work to add editorial memory and next-story learning.

Purpose

A customer story should not only prove product value.

It should also capture signals about customer pressure, operational change, decision-making, adoption, trust, risk, outcomes and future needs.

When analysed systematically, customer stories become part of the evidence base that strengthens broader strategic narratives. They stop being marketing assets with a single use and start being intelligence resources with compound value.

But there is a second layer of value as well. Producing a customer story teaches the organisation something about how to produce the next one: which questions generated useful specificity, what evidence was missing, which claims were hard to verify, where the narrative became confused, and what the review process exposed too late.

This framework provides the structure for making both forms of learning repeatable.

Why normal case studies lose value

The standard case study is designed for a single purpose: demonstrating that a customer achieved results with a product.

It answers a narrow question — did this work? — and then it is published, distributed briefly, and filed.

Six months later, the evidence it contains has disappeared from active use. The signals in the customer’s story — about the pressure they were under, the decision process they followed, the friction they experienced, the risks they weighed — are gone.

And the production learning usually disappears too. The interviewer forgets which question finally produced the useful example. The editor remembers that the strongest claim could not be substantiated, but the next brief does not. The customer correction is applied to the current draft and never becomes a clue about what should have been verified earlier.

This is not a publishing problem. It is a structural problem.

The case study was not designed to be evidence or organisational memory. It was designed to be content. The Case Study Intelligence Framework changes that design intention.

The framework

Stage 1 — Customer context

What situation created the need for change?

Capture the customer’s starting point in operational terms, not outcome terms. What was the environment they were operating in? What pressures, constraints or changes were already present before the decision to act?

This is the signal layer. Context reveals what the customer was already managing — often more significant than the problem the product solved.

Stage 2 — Pressure

What operational, financial or strategic pressure was the customer experiencing?

Name the pressure specifically. Not “they needed to be more efficient” but “they were absorbing three new compliance requirements with the same headcount and no additional budget.”

Specific pressure is the raw material of narrative. Vague pressure is noise.

This maps directly to the Signals stage of the Editorial Intelligence Cycle.

Stage 3 — Decision trigger

What made change necessary now?

Something moved the customer from tolerating a problem to acting on it. Identify that trigger — whether it was a regulatory deadline, a growth event, a leadership change, a competitive shift or a specific incident.

Decision triggers reveal structural patterns when seen across multiple stories.

Stage 4 — Adoption story

How did the customer move from problem to implementation?

Capture the friction, not just the outcome. What slowed adoption? What required adjustment? Where did human judgement have to override the process? What surprised the customer during implementation?

Adoption stories with friction are more strategically valuable than smooth adoption stories. They reveal where the real work happens.

Stage 5 — Value realised

What changed after adoption?

Capture value in operational terms first — time, cost, error rate, team capacity, compliance coverage — before translating it into business terms. Operational specificity is more credible and more reusable.

Stage 6 — Strategic signal

What does this story reveal beyond this individual customer?

This is the editorial intelligence step. Step back from the individual customer and ask: is this an isolated experience or part of a pattern? What does this story suggest about how a category of customer experiences this problem? What would we need to see in other stories to confirm or challenge that reading?

This is where case study content becomes narrative evidence.

Stage 7 — Reuse potential

Which narratives, frameworks or future assets can this evidence support?

Tag the story explicitly against existing narratives, frameworks and open questions. A customer story that supports the Hidden Hours narrative, validates a signal in the Customer Signal Framework and opens a new question for the Trusted AI narrative has compounding value.

But do not stop at evidence reuse. Record what producing the story taught the team about the next story as well.

The second output: editorial memory

Every completed customer story should leave behind two different forms of memory.

Evidence memory records what the customer story taught the organisation about the customer, problem, market, product or narrative.

Editorial memory records what producing the story taught the organisation about interviewing, evidence, verification, framing and review.

Useful editorial-memory signals include:

questions that generated specific, attributable evidence
questions that repeatedly produced generic or promotional answers
important evidence the interview failed to capture
claims that were difficult to verify after drafting
customer corrections that reveal a recurring proof or attribution problem
narrative choices that made the story clearer
competing themes that weakened the draft
review issues that a stronger brief or earlier QA step could have prevented

This is not a rule-writing exercise. One occurrence remains an observation. A repeated, checkable issue across comparable stories may become a candidate lesson. A candidate lesson should only become a reusable standard after a human editor has validated it and later work shows that it improves the process.

A simple maturity model is:

observation → repeated pattern → candidate lesson → human validation → tested system improvement → retain, revise or retire

That keeps the framework from turning every previous decision into a permanent formula.

The next-story loop

The case study should improve not only the evidence base but the conditions under which the next customer story is produced.

A practical loop is:

previous stories + transcripts + review history → evidence and editorial-memory signals → human judgement → stronger brief and question guide → interview → draft → editorial QA → human, SME and customer review → new evidence + production learning → next story

The goal is not to automate interviewing or editorial judgement. It is to stop the next story from starting with organisational amnesia.

A stronger brief should therefore know:

what the organisation already knows about this customer/problem
what evidence is still missing
which claims will require verification
which previous question patterns produced useful specificity
which recurring narrative or review problems should be watched for
which open strategic questions this interview could help answer

The interviewer should still follow the conversation rather than a script. Editorial memory prepares the human to listen better; it does not replace the judgement required in the room.

Signal types

When reviewing customer stories for strategic intelligence, look for signals across these categories:

Operational pressure — workload, compliance burden, process complexity, capacity constraints

Growth pressure — scaling challenges, new markets, acquisition integration, team expansion

Trust and risk — data concerns, governance requirements, stakeholder confidence, liability considerations

AI readiness — current AI use, attitudes to automation, concerns about accuracy or accountability

Workflow friction — handoffs, manual processes, tool proliferation, communication breakdowns

Decision-making — how decisions are made, who holds authority, what evidence is required

Customer experience — how the customer’s customers are affected by the problem or solution

Productivity — time spent on low-value work, bottlenecks, rework, duplication

Human impact — stress, job satisfaction, skill development, team culture

Financial control — cash flow, cost visibility, budget pressure, late payments

How to use it

The framework can be applied in four contexts:

Before the interview Review previous evidence and editorial memory. Decide what is already known, what still needs to be learned, which proof requirements matter and what earlier customer stories suggest about how to investigate the topic well.

During the interview Use the seven stages as an interview guide. Do not follow them linearly — let the conversation lead, but ensure all seven areas are covered before the interview ends. Use follow-up questions to pursue specificity, consequence and attributable evidence rather than simply completing a questionnaire.

During evidence review Apply the signal classification to existing case studies and customer stories. Most contain more strategic intelligence than was captured at the time. This review process often surfaces patterns that were invisible when each story was treated in isolation. Record production-learning observations separately from approved customer evidence.

During narrative development When building or strengthening a strategic narrative, use the framework to identify which customer stories provide the strongest supporting evidence, and where gaps in the evidence base exist. Those gaps can then inform future interview briefs.

Example application

Hidden Hours narrative — evidence from customer stories

The Hidden Hours narrative identified structural operational pressure on accounting professionals. Customer stories, reviewed through the Case Study Intelligence Framework, provided evidence from the other side of the relationship.

Clients of accounting practices were describing the same pressures from their perspective: slow turnaround on queries, unexpected fees for additional work, confusion about compliance requirements they had delegated.

Stage 6 of the framework — strategic signal — made visible what individual stories obscured: the hidden hours were not just a practitioner problem. They were a client experience problem. The evidence from both sides, connected, made the narrative more authoritative.

The same process can now feed the next story in the other direction. If previous interviews repeatedly show that broad questions about efficiency produce weak evidence but questions about a specific task, week or consequence produce useful detail, that becomes editorial memory available before the next customer conversation begins.

This is the compounding effect in practice: evidence strengthens the narrative, and the work strengthens the next investigation.

Open questions and next iteration

What minimum editorial-memory record is useful without creating another heavy administration layer?
How many repeated occurrences should normally be required before an observation becomes a candidate lesson?
Which customer corrections indicate a reusable editorial problem, and which are simply one customer’s preference?
Can AI surface candidate patterns across transcripts, drafts and review history without being allowed to promote them automatically into standards?
How should evidence memory and editorial memory be separated in shared systems so approved customer proof is not confused with internal production learning?
What is the best way to test whether a retained lesson actually improved the next brief, interview or draft?

These questions will shape Version 0.3.