The Story in Your Head: Why Leaders Mistake Narratives for Facts

You didn't observe that your best director has checked out. You observed three things: she declined the offsite, her update ran four minutes long and two slides short, and she didn't push back when you reallocated her budget. Somewhere between the third observation and the end of the drive home, you wrote a story. It has a genre — the slow exit of someone who has already decided to leave. It has a cause — the comp conversation in June. It has a cast, and in your version of it, she's the one who got comfortable. You have never said any of this out loud. But you have started routing her best work to someone else, and you have decided, without deciding, that the bench conversation can wait.

This is not a failure of character. It is the ordinary operation of a mind doing the job you're paid for. A leader's core function is to make sense of incomplete information quickly, and the instrument for that is narrative: you take sparse, ambiguous signals and assemble them into a structure with causes, intentions, and a direction. Done well, that's judgment. Done unexamined, it's fiction with authority — and the authority matters, because your story doesn't stay in your head. It sets what you ask about, who you develop, what you decide, and how hard your team tries to tell you anything that contradicts it.

How the story gets built

The construction happens in three moves, and none of them feel like bias while they're happening. The first is selection. You don't experience the world as a stream of ambiguous events; you arrive at a meeting already knowing what kind of meeting it is, and that frame chooses which moments register. Two executives sit through the same all-hands and file different meetings, because the frame decides what was memorable. You are not observing your organization and then forming a view. You are forming a view and then observing.

The second move is gap-filling. Real information is always thinner than the decisions you're required to make on top of it, and the mind refuses to leave holes. It fills them with the most available explanation, which is rarely the most accurate one — it's the one that was nearest, most recent, or most emotionally loaded. Someone's comment from Tuesday colors how you read a whole quarter of their work, not because it was informative but because it was vivid. This is the part that should worry a leader most: the confidence you feel about a person is usually a measure of how smoothly the story fits together, not how much evidence supports it. A fluent narrative feels true. Coherence is not verification.

The third move is the one that locks it in. Once the story exists, it becomes a filter: confirmations are noticed and filed as common sense, contradictions are explained away as exceptions, and the whole thing gets rehearsed — with your spouse, your peer, your board — and each retelling adds a detail and removes a doubt. By the time the story is a year old, you can't find the raw observations it was built from. All you have is the story, and the story has the texture of something you witnessed.

Why the story feels like a fact

There's a physiological reason the narrative lands as truth. Unresolved ambiguity is not a neutral state for a nervous system — the brain treats an open loop as a low-grade threat, and it will accept a mediocre explanation over none. That's why the first plausible theory of a person's behavior is so hard to dislodge: it wasn't adopted because it was good, it was adopted because it closed the loop. The relief you feel when a story clicks is real, and it is not evidence. It is the threat response resolving.

Once the story is loaded, it runs your physiology in the room. You walk into the one-on-one already holding the conclusion, and your body gives it away — shorter openings, less eye contact, a slightly flatter tone, questions that are actually confirmations. The other person reads all of it within ninety seconds and adjusts. They become careful. They report upward in a shape that survives your frame. And you walk away thinking, see, there's nothing going on — which is precisely the wrong reading of a person who has learned that honesty is expensive in your presence.

What a wrong story costs

The cost is rarely a single bad decision. It's a slow reallocation of your attention and your people's futures. You stop investing in someone the story has already written off, which reliably produces the outcome you predicted — a person given nothing interesting will eventually stop producing anything interesting. That's the trap: some narratives are self-fulfilling, and the leader who acts on them gets to keep the narrative as confirmation. Your retention numbers then validate a story your own behavior authored.

The second cost is upstream, in the quality of information you receive. Once a story is legible to your team, they write to it. People stop volunteering the messy, ambiguous, half-formed thing that would actually have taught you something, because they can predict which file it goes into. This is how <a href="/insights/youre-the-last-to-know-receiving-feedback-as-a-leader">being the last to know</a> happens: not because anyone lied, but because your interpretations had a shape and everyone learned it.

And the third cost is the one you can't see. Certainty about people closes off the version of them that was still becoming. The executive you've quietly filed as unreliable is often the one two years from being your best option — if anyone is still telling them so. The same reflex, at a larger scale, is what keeps a leader from <a href="/insights/how-to-build-a-bench-develop-the-leaders-beneath-you">building a bench</a>: you can't develop a person your story has already finished with.

How to hold a story as a story

The discipline isn't to stop building narratives — you can't, and you shouldn't want to. It's to keep them in the right slot: hypothesis, not evidence. Five practices do that reliably.

• Separate the observation from the inference, in writing, before you act. Three columns: what I actually saw, what I concluded, what I'd have to believe for my conclusion to be wrong. Most leader narratives collapse when the middle column is forced to stand alone.
• Ask what else fits the same facts. Not as a fairness exercise — as a diagnostic. If you can't produce a second story that explains the same three observations, you're not reasoning, you're recalling a preference.
• Test it with the person, early, and with the story named as a story. "Here's what I've noticed, here's the theory I built from it, tell me where it's wrong" is uncomfortable for about twenty seconds and then produces information no amount of observing would have.
• Run the reverse test: would I accept this reasoning about someone I trusted? The double standard is the tell. You give your own behavior context and other people's behavior character.
• Track your predictions. Write down what the story says will happen and check it in ninety days. Most leaders who do this discover they're wrong far more often than they thought, and the ones who don't discover it are the ones not writing it down.

There is a version of leadership that is simply being right more often, and a version that is being wrong faster and out loud. The first feels better and degrades your information supply. The second is how you stay capable of surprise — which is the practical definition of a leader who still knows what's actually happening in their organization.

"The most expensive thing in your head isn't a wrong conclusion. It's a story that has stopped feeling like a story."

If you notice you've been quietly finished with someone for months — a director, a co-founder, the person you stopped giving the interesting work to — that's worth a conversation before it becomes a resignation letter or a decision you'll have to explain to a board. If you're the one carrying the story, the same test cuts both ways: what has your leader decided about you, and when did they last check?