The ability to interpret complex, ambiguous, or conflicting information and construct an understanding that a team can act on with confidence. It means noticing weak or contradictory signals before they resolve into an obvious story, forming a working interpretation without waiting for complete information, and testing that interpretation against evidence and other perspectives rather than defending it once it is formed. It also means communicating the interpretation clearly enough that others can align around it, question it, and help revise it as the situation develops.

“How can I know what I think until I see what I say?” E.M. Forster

Why sensemaking matters

Sensemaking is the process leaders use to convert ambiguous, incomplete, or contradictory signals into an interpretation the organization can act on. Unlike simple analysis, it does not wait for complete information, because complete information rarely exists in the situations that matter most. In fast moving markets, crises, cultural shifts, or emerging risks, leaders must construct a working understanding before all the facts are in, then revise it as reality clarifies.

The interpretation a leader settles on becomes the organization’s shared reality, whether or not it is accurate. Teams do not act on raw events, they act on the story leaders tell about those events, so a confident but wrong reading of a situation does not just misinform one person, it redirects the effort of everyone who trusts that reading. This is what makes premature closure so costly. The danger is rarely being uncertain, it is resolving uncertainty too quickly and then organizing collective action around a flawed conclusion.

Because sensemaking is inherently retrospective and social, meaning is constructed after the fact through conversation, narrative, and the frameworks a leader brings to bear, not discovered as a hidden fact waiting to be found. This means the skill is not just cognitive but communicative. A leader who reads a situation correctly but narrates it poorly can still leave a team confused, while a leader who builds structured reflection, diverse input, and open uncertainty into how they process events will consistently construct sharper, more testable interpretations than one relying on instinct alone.

“The single story creates stereotypes, and the problem with stereotypes is not that they are untrue, but that they are incomplete.” Chimamanda Ngozi Adichie

What good and bad sensemaking looks like

Bad Good
Reaches for the nearest familiar explanation and treats it as settled, which forecloses the situation before enough signals have been gathered. Holds several possible explanations at once and treats the leading one as provisional, which keeps attention open to disconfirming evidence.
Announces a confident interpretation within minutes of an ambiguous event, which pressures the team to fall in line before the picture is clear. States what is known, what is uncertain, and what is being tested separately, which lets the team calibrate confidence rather than mistake speed for insight.
Gathers more data indefinitely without ever converting it into a working story, which leaves the team waiting for direction that never arrives. Sets a point at which the current best interpretation is acted on, then updates it as new information arrives, which keeps momentum without pretending certainty exists.
Interprets the situation alone and presents the conclusion as fact, which removes the checks that would catch a flawed reading. Tests interpretations out loud with people who see the situation differently, which surfaces blind spots before they harden into decisions.
Hides confusion behind confident language, which denies the team early warning that the situation needs collective attention. Names uncertainty openly as it appears, which signals that questioning the current read is expected rather than risky.
Applies the same explanation that worked in a past situation without checking whether the underlying conditions still match, which imports old assumptions into a genuinely new problem. Actively checks what is different about this situation before reusing a past explanation, which prevents pattern matching from overriding fresh evidence.
Treats the account given of events as neutral reporting rather than as an active shaping of what people believe happened, which lets an inaccurate account calcify into organizational memory. Recognises that the account given of events becomes what people act on, which makes deliberate, careful narration part of the job rather than an afterthought.
Skips reflection once the immediate pressure passes, which lets the next ambiguous event get met with the same untested assumptions. Builds a habit of reviewing what actually happened against what was assumed at the time, which corrects the interpretive habits that produced the last misread.

“The single biggest failure of leadership is to treat adaptive challenges like technical problems.” Ronald Heifetz

Barriers to sensemaking

  1. Relying on past patterns to interpret new situations. The reliance compounds itself, since each time an old pattern happens to fit, it strengthens the leader’s confidence in reusing it, which means the very situations where the pattern quietly stops applying are the ones least likely to be questioned.
  2. Discomfort with ambiguity that pushes toward premature closure. The relief of resolving uncertainty feels identical whether the resulting explanation is right or wrong, so leaders learn to chase the feeling of clarity rather than the accuracy of the interpretation, and the discomfort returns faster each time a rushed explanation later proves wrong.
  3. Overconfidence in your first interpretation. Because the first plausible explanation also arrives with the most emotional relief, it gets treated as tested even though it has only been generated, so the leader stops looking exactly when looking would matter most.
  4. Siloed information that hides the full picture. Each function makes local sense of its own slice of the situation and assumes that sense is complete, so the organization ends up with several confident, mutually contradicting interpretations instead of one uncertain, accurate one.
  5. Avoiding vulnerability by pretending to understand. Once a leader has publicly claimed clarity, admitting confusion later reads as a reversal rather than an update, so the incentive to keep performing certainty grows even as the evidence against it accumulates.
  6. Neglecting reflection after events. Without a deliberate pause, the interpretation that happened to be convenient in the moment gets encoded as the lesson learned, so the organization’s stock of assumptions quietly fills with untested shortcuts rather than examined conclusions.
  7. Underestimating context and the specifics of the situation. Generic frameworks feel efficient because they require no fresh thinking, so leaders default to them under time pressure precisely when the situation is most likely to be the exception the framework was never built for.
  8. Poor narrative skills that block sensemaking from transferring to others. A leader can read a situation correctly and still lose the organization if the explanation is delivered as a list of facts rather than a coherent account, since people act on stories they can follow and repeat, not on data they cannot retain.
  9. Emotion under pressure narrowing perception. Stress shrinks attention to the most threatening or salient details, so the interpretation formed under pressure is built from a systematically incomplete set of signals, and the leader rarely notices the narrowing has happened until well afterward.
  10. Endless information gathering without ever committing to an interpretation. Collecting more data can feel like progress while actually functioning as avoidance, since every new data point postpones the harder task of forming a testable view, which leaves the organization exposed to the cost of indecision while looking busy rather than stalled.

“Cause and effect can only be perceived in retrospect.” David Snowden and Mary Boone

Enablers of sensemaking

  1. Take time before acting. A short deliberate pause interrupts the automatic reach for the first available explanation, which gives slower, more accurate interpretive processes the chance to catch details the fast reaction would have missed.
  2. Actively invite diverse viewpoints through open, inclusive conversation. People who see the situation differently are the only source of feedback that can reveal what your own frame is missing, since anyone who already shares your read will confirm it rather than test it.
  3. Use storytelling to share meaning. A well constructed narrative gives people something they can hold onto and repeat accurately, which matters because an interpretation that cannot be retold correctly effectively stops existing the moment it leaves the room.
  4. Foster psychological safety. When naming confusion carries no social cost, uncertainty surfaces while it is still cheap to address, rather than staying hidden until it has already shaped decisions that are expensive to unwind.
  5. Diagnose the type of situation you are in. Correctly identifying whether a problem is familiar, complicated, or genuinely novel determines which tools are even relevant, since applying a method built for a known problem to a genuinely new one produces confident answers to the wrong question.
  6. Strengthen your comfort with ambiguity. Tolerating an unresolved question long enough to gather real evidence breaks the cycle where discomfort gets relieved by premature closure, since the leader who can sit with not knowing is the one who eventually knows something accurate.
  7. Build regular reflection into your routine. Reviewing outcomes against the assumptions that produced them is what converts experience into calibrated judgment, since without that comparison, success and failure teach identical, uncorrected lessons about how good the original interpretation actually was.
  8. Practise reframing challenges. Deliberately generating a second or third plausible explanation for the same situation weakens the grip of the first one, which matters because the first explanation is rarely wrong for lack of evidence, it is wrong because no alternative was ever seriously considered.
  9. Ask probing reflective questions. Questions that target assumptions rather than facts expose the interpretive leaps a person has made without realizing it, since most flawed sensemaking fails not at the evidence stage but at the invisible step where evidence gets turned into meaning.
  10. Set a decision point, commit to your best current interpretation, and revise as new evidence arrives. Naming the moment you will act on incomplete information in advance prevents both premature closure and paralysis, since the commitment is explicitly provisional, which makes revising it later a sign of good sensemaking rather than an admission of earlier failure.

“The only true voyage of discovery would be not to visit strange lands but to possess other eyes.” Marcel Proust

Self-reflection questions for sensemaking

  1. When did you last mistake a familiar explanation for a correct one, and what would it have looked like to test it before acting?
  2. What is the current situation asking you to notice that a past pattern might be causing you to miss?
  3. Whose perspective have you not yet sought on this situation, and what might they see that you cannot?
  4. How comfortable are you naming what you do not yet understand out loud, in front of your team?
  5. What decision point have you set for converting your current interpretation into action, and what would change your mind?
  6. What story are you telling about recent events, and how is that story shaping what your team believes is true?
  7. When did emotion under pressure last narrow what you were willing to consider as an explanation?
  8. How often do you build in time to review what actually happened against what you assumed at the time?
  9. What information is currently siloed in your organization that, if surfaced, would change your read of the situation?
  10. What would it look like to hold two competing explanations for the same situation at once, rather than settling on one too quickly?

“A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.” Alfred Korzybski

Micro practices for sensemaking

  1. Write down your first explanation before seeking more information, then revisit it once the fuller picture emerges. This exposes how much of your initial read was pattern matching rather than evidence, since comparing the early guess to the later understanding reveals exactly where your assumptions filled gaps that data later contradicted.
  2. Before presenting a conclusion, state it as “my current best read is” rather than as settled fact. This small language shift keeps the door open for correction, since a claim framed as provisional invites challenge while a claim framed as certain invites compliance, and the difference determines whether your team catches your errors or inherits them.
  3. Schedule a short retrospective after significant events, even successful ones, to compare what was assumed against what actually happened. This matters because success without review teaches the wrong lesson just as often as failure does, since a good outcome can mask a flawed interpretation that only worked because of luck rather than accuracy.
  4. When you notice discomfort with an unresolved situation, name it rather than resolve it prematurely. This breaks the loop where anxiety about ambiguity gets relieved by any confident sounding explanation, since the relief of closure feels identical whether the explanation is right or wrong, so noticing the urge is the only reliable signal that you are about to trade accuracy for comfort.
  5. Deliberately seek out one person who reads the situation differently before finalizing your interpretation. This works because people who agree with you confirm your existing frame rather than test it, so disagreement is the only feedback that can actually reveal what your frame is missing.
  6. Practise narrating events to your team using an explicit “what we know, what we don’t know, what we’re testing” structure. This prevents the common failure where a leader’s confident tone gets absorbed as certainty regardless of the words used, since separating the categories forces the team to track uncertainty explicitly rather than infer false confidence from your delivery.
  7. Before applying a solution that worked in a previous situation, list what is different about the current one. This counters the compounding trap where each successful reuse of an old pattern makes the pattern feel more universally reliable, so the very evidence that should prompt scrutiny, repeated past success, is what erodes the scrutiny it needs.

“Leaders who refuse to listen will eventually be surrounded by people who have nothing significant to say.” Andy Stanley

Explore related leadership resources

To further develop this capability, examine how it intersects with other core leadership dimensions across the libraries:
Leadership library:

  • Insight Seeking: Explore patterns and deeper meaning within complex situations, enabling more informed interpretation and action.
  • Questions (Asking good): Use powerful questions to surface assumptions, challenge thinking, and open up new perspectives.
  • Self Awareness: Recognise how your own biases and interpretations shape meaning, allowing you to engage more objectively with complexity.

Supporting libraries

Continue exploring: Return to the Leadership Library to view the full directory of competencies and resources.