Sensemaking

Why it matters

People don’t first understand a situation and then act — they act, watch what happens, and then build a story that explains it. Understanding is constructed after the fact, out of cues their own actions generate. When a situation turns strange enough that the shared story stops holding — when roles, routines, and the very picture of “what’s going on here” dissolve — the ability to make sense of events dissolves with it, and a group can freeze at exactly the moment it most needs to move.

For example: an airline crew hits a warning light no checklist quite fits. The captain who keeps the crew talking — narrating what each instrument shows, what they’re trying, what they’re seeing — holds the cockpit together: the running story is a shared framework everyone can correct and add to, and small actions keep producing fresh cues. The captain who goes silent and stares at the panel offers the crew nothing to interpret; the shared picture frays, the others stop knowing their part, and confusion compounds. Same emergency, same training — what differs is whether a workable interpretation got built, out loud, while the situation was still moving.

What it reveals. That interpretation is an achievement, not a given — a story actively constructed from the cues action throws off, held together by intact roles and a shared narrative, and only ever as good as its last update.
How it changes the read. You stop asking “did they understand the situation?” and start asking “were they able to build and keep updating a workable story — and was the structure that lets a group interpret events still standing?”
When to foreground it. A genuinely ambiguous or novel situation where routines don’t fully apply; a crisis the team is improvising through under time pressure; a post-incident review trying to recover why people acted as they did; a reorganization that has scrambled who does what.
What you’d miss without it. That a competent team can fail not from bad decisions but from interpretive collapse — frozen, role-stripped, unable to assemble any coherent read — and that staying in action is often what keeps understanding alive, because action is where the cues come from.
Where it misleads. Treating the after-the-fact story as if it were known all along is its own trap — a tidy reconstruction can make a chaotic response sound deliberate, and clinging to an early story while cues pile up against it is how a plausible interpretation becomes a wrong one.

How it works

In August 1949, fifteen smokejumpers parachuted into Mann Gulch in Montana to fight what looked like a routine wildfire. Within an hour, thirteen of them were dead. The organizational theorist Karl Weick spent years studying the disaster, and the reading he produced is one of the most piercing accounts ever written of how understanding falls apart.

The fire, it turned out, was not routine. It jumped the gulch and “blew up” — exploding into a wall of flame that raced uphill straight at the crew faster than a person can run. The foreman, Wagner Dodge, did something that looked, in the moment, insane. He stopped running, struck a match, and deliberately lit a new fire in the tall grass ahead of him. As that small fire burned a patch clear, he stepped into the still-hot ashes, lay down, and let the main fire roar over and around the burned-out ground. He survived. This maneuver — the “escape fire” — is now standard wildland-firefighting technique. But in 1949 no one had seen it, and that is the heart of the tragedy: Dodge shouted for his crew to join him in the ashes, and they could not understand him. To men fleeing a fire, a man lighting another fire in their escape path made no sense at all. They ran past him for the ridge. Many never dropped their heavy tools — their saws and shovels — even as the weight cost them the seconds that meant their lives.

That last detail is what Weick could not stop turning over. Why would running men, in a footrace with death, keep carrying forty pounds of equipment? His answer reaches past the fire. Under enough stress, he argued, the thing that quietly collapses first is not courage or strength but the structure that lets a group interpret events at all — its chain of command, its routines, its shared sense of the situation, and even the tools that anchor who each person is. A firefighter carries tools because firefighters carry tools; the saw is part of the identity. When the situation became incomprehensible and the crew’s shared framework dissolved — orders stopped making sense, the group scattered, each man alone — the ability to make sense of anything went with it. Dropping the tools would have meant, at some level, ceasing to be a firefighter, at the very moment that role was the last solid thing left to hold.

Pull back and the mechanism is general. We don’t, as we like to imagine, first work out what’s happening and then decide what to do. We act, see what our action produces, and then assemble a plausible story that explains the result — and that story is what we call understanding. Weick gave the process four properties. It is retrospective: we make sense of what we’ve already done, reading meaning backward from outcomes. It is social: shared narratives, built out loud between people, bootstrap a common picture no individual could hold alone. It is anchored in identity: who we take ourselves to be decides what even counts as a relevant cue. And it is ongoing: the story is never finished, only continuously updated as new cues arrive — or wrongly defended as the cues turn against it.

Which yields Weick’s hard, practical lesson, the one that turns a tragedy into a tool: if people can stay in action, they can make sense of things; if they stop, confusion may overwhelm them. Action is not the reward for understanding — it is the source of it, because action is what generates the cues a story gets built from, and movement is what keeps a role, and an identity, intact. The modern echo is everywhere a team improvises through an ambiguous crisis and stays oriented not by pausing to figure it all out, but by keeping the work going and narrating it as they go: naming what they see, holding their roles, updating the shared story out loud, never letting the silence in. The name for all of this is right in the title — it is sensemaking.

Framework & implementation

Origin and evidence

The framework is Karl Weick’s, and its founding case is his 1993 paper in Administrative Science Quarterly, “The Collapse of Sensemaking in Organizations: The Mann Gulch Disaster” — the close reading of the 1949 wildfire that established how interpretive structure, and the identity anchored in it, can dissolve under extreme stress. Weick’s comprehensive theory followed in Sensemaking in Organizations (1995), which laid out the now-standard properties: sensemaking is retrospective, social, identity-grounded, and ongoing. The applied extension is Weick and Kathleen Sutcliffe’s Managing the Unexpected (2007), which built the ideas into the practice of high-reliability organizations — aircraft carriers, control rooms, emergency rooms — that operate continuously under conditions where a lapse in collective sensemaking is catastrophic. A close complement comes from Gary Klein’s Sources of Power (1998), whose naturalistic-decision-making research showed how experts under time pressure act through recognition and rapidly built mental simulation rather than deliberate comparison — the individual-cognition counterpart to Weick’s social account.

Applications and common uses

Sensemaking is a working tool wherever people must construct a workable interpretation faster than the situation will sit still.

Crisis and incident response. Its native ground: keeping a response team in action and narrating, preserving roles so the shared picture holds, and treating new information as cues that update the working theory rather than noise to be forced into the first one.
Post-incident review and investigation. Reconstructing what people believed at each moment — the in-the-moment story — instead of imposing the clarity that only hindsight allows, which is the discipline that separates real learning from blame.
High-reliability operations. Aviation, medicine, power, and industrial control, where Weick and Sutcliffe’s work made “collective sensemaking” an explicit safety practice: preoccupation with weak signals, reluctance to simplify, deference to expertise on the spot.
Organizational change. Reorganizations scramble roles, and scrambled roles degrade sensemaking; the lens flags the interpretive cost of disrupting who-does-what and argues for preserving enough structure that people can still read their situation.
Strategic foresight. The use a reader meets here: building scenarios as pre-rehearsed interpretive frames so that when an ambiguous future arrives, the organization recognizes it faster and isn’t constructing a story from scratch under pressure.

In every case the payoff is the same: interpretation is treated as something actively built and maintained — out of action, narration, and intact roles — rather than something that simply arrives, so the framework is still standing when it’s needed most.

Failure modes and when not to use it

The lens’s characteristic ways of going wrong are catalogued in its Common Failure Modes:

Narrative lock-in. An early interpretation persists despite contradictory cues. The tell: the investigation keeps heading in its original direction long after the evidence stopped supporting it. The correction is to build cue-audit checkpoints into the process — a scheduled “what supports our current theory, and what contradicts it?” — and, in scenario work, to keep every scenario at equal standing rather than promoting one.
Sensemaking collapse. Actors freeze because they can no longer interpret the situation. The tell: action stops and communication degrades. The correction is to enforce small, safe-to-fail actions that restart the cue-generating cycle, and to protect role structure, since identity is the scaffolding the whole process rests on.
Retrospective rationalization. The after-the-fact story makes the response sound more coherent than it was. The tell: a timeline reconstruction shows the tidy explanation could not actually have been known at the time. The correction is to separate “what we knew when” from “what we know now” as a standing discipline.

When not to reach for it. When the situation is genuinely not ambiguous — a well-understood problem with a procedure that fully applies — sensemaking adds little; the right move is to run the known procedure, and domain-typing (the Cynefin framework) is the tool that tells you which case you’re in. When the task calls for a probability-weighted read of the future rather than a set of interpretive narratives, the heavier forecasting analysis fits better. And the lens describes and protects the construction of interpretation; it does not, by itself, decide — choosing a course of action from a well-made interpretation is the job of a decision analysis, for which sensemaking supplies a sounder, less prematurely-narrowed input.

Scenario Planning — the analysis this lens informs; builds multiple causally-distinct narratives of an uncertain future, each held at equal standing, as pre-rehearsed interpretive frames.
Second-Order Thinking — the sibling lens in the same future-exploration territory: where sensemaking builds the interpretive frame, second-order thinking traces the chain of consequences an action sets in motion within it.
Cynefin Framework — the domain-typing companion that decides when sensemaking applies: it separates the ambiguous, probe-first situations where sense must be made from the ordered ones where a known procedure already fits.
OODA Loop — Boyd’s decision cycle whose “Orient” stage is where sensemaking lives: the moment a team turns raw observation into a workable read before it acts.