Operational Storytelling: Narrative Evidence for Leaders
Operational storytelling is the disciplined practice of capturing, organizing, and deploying short narratives drawn from everyday work so that decisions, risks, and changes become intelligible to the people who must act on them. It differs from brand storytelling in its purpose: the objective is not persuasion of an external audience but shared understanding inside the organization, particularly where data alone leaves the causes and consequences of a situation unexplained. The following analysis defines the practice, summarizes the available research on its effectiveness and its limits, and outlines a method for embedding it in existing routines.
TL;DR
- Operational storytelling treats narrative as infrastructure embedded in existing workflows, not as a separate communications campaign.
- Narrative is most defensible as evidence that explains quantitative metrics, and the research suggests it is weaker than analytical data when the aim is to convey complex technical reasoning.
- Stories used to soften or obscure bad news tend to erode trust, so the practice requires an explicit ethical constraint.
- Participation is sustained by short submissions (about five minutes) placed inside forums that already exist, such as retrospectives and all-hands meetings.
- Stories that specify cause and decision, rather than describing traits, remain coherent under crisis conditions.
Table of Contents
- What the term means, and what it does not
- The empirical case for narrative in organizations
- Where narrative is weaker than data
- Narrative evidence: the operational use case
- Structure: the character as a causal engine
- Four modes of persuasion and the shared story
- Narrative infrastructure and the risk of constraint
- Embedding the practice in existing workflows
- Applying the method to change management and executive briefings
- Storytelling beyond operations
- Our perspective
- Where PROJECT-JTH can help
- FAQ
- Sources
What the term means, and what it does not
The phrase is used in two overlapping senses. In the first, it denotes a communication skill: a leader selects an incident, frames it with context, and relays it so that listeners grasp why it matters. In the second, which is the more useful for operations, it denotes a system. One practitioner analysis, published in 2026 by GoodSeeker, frames storytelling as infrastructure: a systematic way to capture, organize, and deploy proof narratives that support operational decisions.
The distinction has practical consequences. A skill depends on the individual who possesses it, whereas a system persists through staff turnover and can be audited. Moreover, the systemic view clarifies what operational storytelling is not. It is not embellishment of facts, it is not an internal marketing exercise, and it is not a substitute for measurement. A widely read 2025 commentary on the topic describes it instead as connective tissue among existing disciplines, an evolution of them rather than a replacement, and argues that vague storytelling collapses quickly under pressure, a point that becomes particularly relevant in incident response and other high-stakes settings.
The empirical case for narrative in organizations
The academic literature on organizational storytelling is extensive, though uneven in quality and scope. Three findings are worth distinguishing, because they support different claims.
Narrative as a vehicle for change
A 2022 study in the Journal of Knowledge Management notes that organizations frequently rely on stories to overcome change management challenges, and that storytelling has emerged as a leading tool for influencing people and encouraging knowledge sharing. A Harvard Business Review article from November 2023 makes a related argument from the leader’s side: after a plan is mapped, a further step remains, which is to tell a story that explains why the change is needed and how it will unfold. The same article is commonly summarized as recommending a narrative that honors the past, states a mandate for change, and describes a rigorous but optimistic path forward.
Narrative in a leadership role
A 2025 phenomenological study of exemplary chief nurse executives, drawing on Denning’s model, examined how senior healthcare leaders use stories to lead. It reports that storytelling drives transformation through numerous themes, among them sharing personal vulnerabilities, building purposeful collaboration, and recognizing community integration as essential to organizational values. The sample is small (ten participants), and a dissertation of this kind describes experience rather than establishing causal effects. It nonetheless indicates that narrative competence is a recognizable feature of leaders in a field where operational stakes are high.
Underuse in practice
A 2025 conceptual model published in Management Science Advances concludes that organizational storytelling is highly effective for strategic management yet underutilized. In its case study of an industrial group, only 9 of 20 potential storytelling applications were in use. The finding is a single case and should not be generalized as a rate, but it is consistent with the practitioner observation that stories are told informally and rarely captured.
Where narrative is weaker than data
An honest account of the practice must include its limits. Research by Michael Carriger, reported in a Sacred Heart University working paper comparing narrative with PowerPoint, indicates that narrative is not a universal remedy. The evidence suggests that it energizes audiences and can limit negative behavioral consequences in difficult periods, whereas clear analytical data is more effective when the aim is to convey complex reasoning or to establish belief in a leader’s integrity regarding a specific technical decision.
A companion paper on delivering bad news about layoffs through narrative examines the same tension empirically. The practical implication is a rule of division. Where the audience must evaluate a technical claim (an architecture choice, a risk acceptance, a security finding), the analysis and figures lead and the story illustrates. Where the audience must be oriented, motivated, or kept steady, the story may lead and the figures support. Using narrative to obscure unwelcome facts is the failure mode, because it converts a trust-building instrument into a source of distrust once the omission is discovered.
Narrative evidence: the operational use case
The most defensible form of operational storytelling in mission-critical environments treats the story as evidence attached to a metric. The common misconception is that stories compete with data. The GoodSeeker analysis offers an illustrative case: a reported uptime of 99.7% may appear satisfactory while concealing unsustainable manual workarounds that keep the figure high. The number is accurate, yet it conveys nothing about fragility. A short narrative describing who performs the workaround, how often, and what would happen if that person were unavailable supplies the missing context, and it moves leadership from passive reporting toward active risk management.
A worked example in the same spirit (illustrative, not a documented case) shows the structure:
| Element | Metric alone | Metric with narrative evidence |
|---|---|---|
| Statement | Backup success rate is 99.7%. | Backup success rate is 99.7%, but two failed nightly jobs are re-run by hand each week by one administrator. |
| Implied risk | Low | Single point of failure in staffing, undocumented procedure |
| Decision prompted | None | Automate the re-run, document the procedure, assign a second operator |
The narrative adds no embellishment. It contains a person, an action, a frequency, and a consequence, each of which can be verified.
Structure: the character as a causal engine
Screenwriting theory offers a useful discipline here. According to the Elliot Grove analysis, describing a person with a trait (“she is ambitious”) is less effective than treating the person as a causal engine, in which a trait leads to a decision, and the decision produces a change in the scene. Applied to operations, the same rule excludes adjectives and requires sequence. “The on-call engineer is diligent” conveys little. “The on-call engineer saw the disk alert, judged it to be recurring noise, delayed action for forty minutes, and the database stalled” conveys a decision, its rationale, and its effect, which is what a review or a risk register requires.
A workable template for a short operational story follows.
- Context: the system, team, or constraint, in one or two sentences.
- Decision: what a named role chose to do, and the reasoning available at the time.
- Consequence: the observable effect, with a figure where one exists.
- Implication: what the organization should keep, change, or investigate.
The fourth element prevents the story from remaining anecdote. It ties the narrative to an action that can be assigned and tracked.
Four modes of persuasion and the shared story
A leadership communication article in the FBI Law Enforcement Bulletin describes effective organizational stories as relying on four pillars of persuasion: logos (logical appeal), ethos (trust), pathos (emotional appeal), and mythos, the overarching shared story that members recognize as an account of who they are. The framework is useful because it places operational stories in a hierarchy. Individual incident narratives draw on logos and ethos, since they supply sequence and credibility. The mythos is the standing account into which those incidents are filed: whether the organization understands itself as one that reports near misses promptly, or as one that conceals them.
Narrative infrastructure and the risk of constraint
Practitioners at the Embedding Project use the term narrative infrastructure for the collection of ideas, stories, and metaphors that define what is legitimate within an organization. This infrastructure accelerates routine decisions by setting implicit norms. It also presents a hazard: stories that once explained success can harden into constraints that prevent adaptation. Leaders therefore do not merely tell stories; they shape the set of stories that circulate, and they must intentionally influence the dominant ones so that change remains possible.
For change programs, this suggests an audit before a campaign. The relevant questions are which stories new employees hear in their first month, which failures are retold and which are omitted, and whether the dominant account of past success is compatible with the change being proposed. Where it is not, the change narrative must address the older story directly, an approach consistent with the HBR recommendation to honor the past before articulating a mandate for change.
Embedding the practice in existing workflows
The GoodSeeker analysis reports that operational storytelling functions as an embedded capability rather than an initiative to be launched. Programs run as separate projects, with dedicated meetings and elaborate reporting, tend to lose participation once the initial novelty fades. The more durable pattern places five-minute story submissions in forums that already meet, such as project retrospectives and all-hands sessions. The claim is a practitioner observation, not a controlled finding, but it agrees with ordinary experience of administrative overhead.
A minimal implementation has five steps.
- Select one existing forum, for example the end-of-sprint retrospective or the after-action review that follows an incident.
- Add a single prompt, such as “describe one decision this period that the metrics do not explain.”
- Store submissions in the system already used for operational records, tagged by system, risk, and decision type, so that they are retrievable. Teams that manage production records can keep them alongside the records they explain; version discipline matters here, as discussed in this guide to document version control for teams.
- Review a sample monthly against the associated metrics, and record where a story contradicted a favorable figure.
- Report to leadership with the figure and the story together, and mark the action taken.
The after-action pattern deserves emphasis. Structured reviews already require participants to reconstruct events in sequence, so the narrative is partly produced as a by-product. A related treatment of restoring clarity under pressure with after-action reviews describes how this reconstruction can be kept brief and factual.
Applying the method to change management and executive briefings
In change management, operational stories serve two functions. First, they provide evidence of the problem in the words and experiences of the people affected, which is more concrete than a statement of strategic intent. Second, they supply early evidence of progress: a story of the first team that completed a migration without an outage is more portable than a dashboard. The caveat from the research stands, however: where the audience must judge technical merit, the data is presented in full, and the narrative accompanies it.
For senior audiences, the same logic supports a structured briefing in which the conclusion and the decision requested appear first, and the story appears as the supporting case. A template and tests for executive briefings elaborates on that structure. For security leaders, a board-ready set of zero trust KPIs offers an example of metrics that benefit from a short narrative explaining what each figure conceals or reveals.
Crisis settings impose a further requirement: the story must already exist before the incident. Organizations that have rehearsed a concise account of what is known, unknown, and being done communicate more consistently than those that improvise. This is the reasoning behind a crisis communications plan prepared in advance, and behind short rehearsal routines of the kind described in a 60-second rehearsal for communication under pressure.
Storytelling beyond operations
Brand-facing storytelling follows different conventions, since its audience is external and its goal is engagement. Readers interested in that adjacent field may consult an overview of storytelling and brand engagement, which treats strategic applications across organizations. The operational variant described here is narrower and more conservative: it is bound to verifiable events and to the decisions that follow from them.
Our perspective
We work where technical systems and human communication meet, and the pattern we see most often is not a shortage of data but a shortage of context attached to it. Dashboards report that a system is healthy, and the people who keep it healthy know at what cost. Our position is that the context belongs in the record, in plain sequence, written by the person who made the decision, and reviewed alongside the metric it explains.
We also hold to a constraint that the research supports: a story never replaces the analysis, and it is never used to soften a finding. When a technical decision is being evaluated, the evidence comes first. When a team must stay oriented through a stressful change, the story carries the weight. Distinguishing the two situations is itself a leadership skill, and it is one we build into our workshops and advisory work, where clarity under pressure is the common objective.
— Jesse Hart
Where PROJECT-JTH can help
For organizations that want to build this capability, PROJECT-JTH offers keynotes and workshops on calm leadership and communication under pressure, along with technical advisory work for risk assessment and infrastructure. Details of the speaking and workshop offerings are on the PROJECT-JTH home page, and technical engagements are described on the technical consulting page. Teams that need a structured place to keep production records and contracts can look at Project Relay, listed at $49 per month. Consultants who produce assessments and reports can see Project Praxis, listed at $99 per month.
FAQ
What is the difference between operational storytelling and business storytelling?
Business storytelling is the broader practice of using narrative, data, and context to communicate clearly, often to customers or prospects. Operational storytelling is narrower: it captures internal accounts of decisions, risks, and results so that leadership can act on them. Its audience is the organization itself, and its test is verifiability.
Can a story replace data in a leadership presentation?
The research reviewed here suggests not. Narrative is effective for energizing and orienting people, but clear analytical data performs better when the goal is to convey complex reasoning or to establish confidence in a technical decision. The most defensible approach pairs a metric with a short story that explains it.
How should storytelling be used in change management?
A change narrative honors what came before, states why change is needed, and describes a realistic path forward, as recommended in the 2023 Harvard Business Review article cited above. It should be supplemented by an audit of the stories already circulating, since an entrenched account of past success can obstruct adaptation. Bad news should be stated plainly, not wrapped in narrative.
How can a team start without creating another initiative?
Attach a single prompt and a five-minute slot to a meeting that already exists, such as a retrospective or after-action review. Store the submissions with the operational records and review them against the relevant metrics each month. Keeping the overhead low is the main safeguard against declining participation.
Sources
- GoodSeeker: Operational Storytelling for COO
- Elliot Grove: Operational Storytelling
- Story-making to nurture change (Journal of Knowledge Management, 2022)
- Exemplary Chief Nurse Executives Leading Through Storytelling
- Conceptual Model of the Effectiveness of Storytelling in Strategic Management (Management Science Advances, 2025)
- Narrative vs. PowerPoint: For Leaders, It May Not Be a Matter of Fact
- A Narrative Approach to Delivering Bad News in Organizations
- FBI Law Enforcement Bulletin: Leadership Storytelling
- Embedding Project: Shaping Your Organisation’s Narrative Infrastructure
