BEFORE THE STORY FINISHES HAPPENING, SOMEONE HAS ALREADY DECIDED WHAT IT MEANS

Have you ever noticed what happens in a room one second after someone says, “I think I know what happened here”?

Every shoulder in the room drops. Someone exhales, quietly, air they’d been holding since the meeting started. Nobody has checked anything yet. No data has been cross-referenced, no witness asked twice, no counter-hypothesis put on the table. And still, relief settles over the room, because the unbearable gap — that silent stretch between what happened and what it means — has just been filled. By anything. By anyone.

I call this the rush to decide meaning. And I disagree with most of what gets said about it, because the usual framing treats understanding complex situations as a matter of competence: whoever has more data, more intelligence, more experience, understands better. That’s not quite it. Understanding fast, most of the time, has nothing to do with competence. It has to do with discomfort.

Nobody can stand the blank.

That’s all it is.

Watch traffic sometime. The car ahead brakes hard. Before your foot even reaches the pedal, a whole story has already formed in your head: a driver on their phone, someone crossing where they shouldn’t, a dog loose on the road. You’ll never know which one is true, and here’s the strange part — you don’t actually want to know. You just wanted the second of not-knowing to end. The story you invented doesn’t need to be right. It only needs to arrive fast enough to silence the question.

Now take that same reflex and drop it inside a company. It stops being trivial. It becomes structural.

In a risk committee, someone reports an incident. Before any formal review, before a single fact has been verified, a version is already circulating through the hallways — and that version, the first one, the one delivered with the steadiest voice and the least hesitation in the eyes, becomes the filter every subsequent question passes through. The questions that follow don’t test the story. They confirm it. And here’s the worst part: nobody notices they’ve switched from investigating to confirming, because the feeling of doing one is identical to the feeling of doing the other. Only the outcome changes.

I’ve sat in rooms where I watched this happen with an almost cruel clarity. The person who speaks first, with the most conviction, isn’t necessarily informing the room. They’re deciding what the room will remember as truth a month from now. And the tragic part is they don’t know they’re doing it. They genuinely believe they’re just describing the facts.

Here’s the part nobody says out loud: understanding a situation too quickly is, almost always, cowardice wearing the costume of efficiency.

Let me explain.

Sitting in not-knowing is uncomfortable in a physical, almost bodily way. It tests patience, tests the ego — because as long as you haven’t decided what something means, you also don’t know who’s at fault, who’s right, who’s about to get blamed, and that ambiguity bothers people more than any real damage ever could. Entire companies trade months of serious investigation for one rushed morning of conclusion, just to hand back a feeling of control to whoever can’t stand not knowing any longer.

I’ll tell you something I learned watching leadership teams up close, compliance committees, negotiation tables: the cost of deciding meaning too fast never shows up right away. It shows up months later, dressed as a different problem. It becomes “a communication issue.” It becomes “misalignment.” It becomes “resistance to change.” Nobody goes back to ask whether, at the root, it was never a communication problem at all — whether someone simply decided the plot before the facts had finished revealing themselves, and everyone else, for comfort’s sake, bought that plot without arguing.

A newer version of this became common once so much of work started happening behind a screen. A message lands too dry. A voice note goes unanswered for twenty minutes. A camera stays off during an important call. And right there, with no data beyond the silence, a whole person has already rewritten someone else’s intentions: “she’s upset with me,” “he’s lost interest in the project,” “they’re deliberately leaving me out.” Nobody asked anything. A screen gives you no face, no tone, no visibility into someone’s exhaustion at the end of a long day. It’s exactly that absence of information that makes the imagination move faster — the less real data there is, the more room the story has to grow on its own.

I’ll bring this home too, because it isn’t only a workplace problem. It’s human, and that’s why it lives everywhere.

Someone walks in quiet after a long day. Their partner looks over, feels the silence, and in a single second has already decided: he’s mad at me. Nobody asked. They’ve already started reacting to the story they invented, not to the person who just walked through the door. They spend the whole evening arguing with a fictional plot, while the real exhaustion of the day — which was just that, exhaustion, nothing more — waits, with no room to exist, outside the conversation.

It would be funny if it didn’t hurt so much.

We spend so much of our lives fighting with stories we made up about other people, and so little time fighting with the people themselves.

I think — and this is an opinion I’m claiming, not a truth I’m announcing — that the rarest, most underrated skill inside any organization isn’t deciding fast. It’s tolerating the stretch where nothing is decided yet. That tolerance doesn’t show up on any performance review. It has no polished name in a competency framework. And yet it’s what separates people who lead with real depth from people who simply manage collective anxiety while looking efficient.

Because here’s the thing: saying “I don’t know yet” in a decision-making room is, in most corporate cultures, treated almost like weakness. Whoever says it gets read as slow, insecure, not assertive enough. And what the culture ends up doing, without ever meaning to, is reward whoever invents a fast version instead of whoever investigates with patience. It rewards the speed of the narrative, not the quality of it.

There’s a name for this that you’ve probably run into somewhere — sensemaking — though the name matters far less than the lived experience of it. In practice, it isn’t a tidy, organized process laid out in stages inside a leadership workshop. It’s messy. It’s instinctive. It’s a tired person in a hallway, desperately trying to turn a mess of incomplete information into something that feels manageable before the four o’clock meeting starts.

And here’s the turn I wanted to make: giving something meaning isn’t about having more information. It’s about having enough courage to stay without it longer than everyone else can bear.

Whoever manages that, whoever trains the body and mind not to close the story too early, starts seeing things nobody else sees. Not because they have different data. Because they didn’t shut their eyes too soon.

This isn’t a gift reserved for the more enlightened among us. It’s practice, and nobody outgrows the temptation, not even after years at it. I fall for it myself, most Friday evenings, exhausted, closing off any explanation that lets me stop thinking about something for one more minute. The difference isn’t immunity. It’s remembering to resist one more time, even tired.

There’s a risk I see often in compliance and audit teams that rarely gets called by its real name: the risk isn’t missing information. It’s the rush to fill the gap with the first available explanation, especially when that explanation spares someone a difficult conversation, or spares the company from admitting the problem is structural, not isolated. An audit that starts out already committed to a rushed conclusion isn’t investigating anything anymore. It’s gathering evidence to confirm what someone, in a hallway, already decided before any proof existed.

There’s also a side effect that rarely makes it into any report: when the whole room buys the first version, accountability dissolves right along with it. Nobody needs to doubt, question, or double-check anymore, because doubting the accepted story starts to sound like doubting the people who told it — and socially, that costs too much for most people to risk. So the meaning that should have been investigated becomes consensus, the consensus becomes politics, and the politics becomes the reason why, six months later, nobody can explain how an obvious problem went unnoticed for so long. It didn’t go unnoticed. It was agreed upon, quietly, by people who preferred the peace of a closed story to the discomfort of an open question.

There’s a subtler version of this, and it usually wears the costume of good leadership. A team finishes a project that didn’t work out. The leader, before even hearing the team out, walks in with the explanation already packaged, almost gently: “the market shifted,” “we ran out of time,” “nobody could have seen it coming.” The intention is good — sparing the team the discomfort of rebuilding what happened on their own. But by handing over a finished meaning before people have had room to build their own understanding, that leader isn’t taking care of anyone. They’re kindly silencing the one thing that would have made the team actually learn something. The team leaves the room relieved, and somehow emptier than when they walked in, because they’ve just received an answer to a question they never got to ask for real.

We’re also living through a moment where data has never been more abundant, and, strangely enough, conclusions have never been reached faster. Dashboards, automated reports, real-time alerts — all of it promises more clarity and, in practice, delivers more haste. The more information arrives, the greater the temptation to close a quick verdict, just to prove you’re in control of all that volume. But information isn’t meaning. Meaning is what’s left after someone has been patient enough to look at the data long enough for it to stop lying.

You might be thinking this is inevitable, that the world moves too fast to sustain that kind of interpretive patience. I agree the world moves fast. I don’t agree that this justifies the rush to decide what things mean. Acting fast is one thing. Deciding meaning fast and mistaking that for acting fast is something else entirely. These are two different processes, and confusing them is where some of the worst strategic mistakes I’ve ever watched companies make were born.

A team can move with speed — test, adjust, correct course — without needing to prematurely close what an event represents. The most agile teams I’ve ever worked alongside weren’t the ones deciding meaning the fastest. They were the ones acting fast precisely because they weren’t wasting time arguing with invented stories. They tested hypotheses instead of defending them.

That changes everything.

The moment you defend an interpretation instead of testing it, you stop seeing what’s actually in front of you and start seeing only what confirms what you’d already decided to see. And that, inside any governance, risk, or leadership structure, is the quiet beginning of nearly every collapse that later gets announced as a surprise.

It wasn’t a surprise. It was a story told too fast, by someone who couldn’t stand the silence in the room any longer.

I think about small children, who haven’t yet learned to fake knowing. A child hears a strange noise in their room and asks, with no shame at all, “what is that?” — and actually waits to find out. They haven’t yet learned there’s a social reward for answering quickly. We learn that reward later, at school, at work, in meetings where hesitation looks like weakness. Growing up, in a lot of ways, is trading a genuine question for a rushed answer — and calling that maturity.

There’s a small, almost bureaucratic detail that tends to seal this rush forever: the record. The moment the first version of an event enters an official document — meeting minutes, an incident report, a compliance memo — it stops being a provisional interpretation and becomes fact. And a written record, inside any corporate structure, carries the weight of something already settled. Nobody tends to reopen minutes to ask whether that first reading still holds up. The written word locks the story in place long before the story has finished forming, which is why so many companies carry conclusions for years that were never actually verified — only documented too soon.

I’d like to leave you with an invitation, not a formula. Next time you feel the relief of someone saying, “I already know what’s going on,” pay attention to your own body before you accept that as truth. Notice whether that relief came from real investigation or just from wanting to stop feeling the discomfort of not knowing. The two feelings look almost identical. Only one of them is honest.

Next time a meeting ends with that familiar “so, are we all aligned?”, try a quiet experiment: keep, just for yourself, the questions that never made it into that agreement. No need to raise your hand, no need to break the mood. Just keep them. And notice, the next day, whether that consensus still feels as solid as it did in the closed room. Sometimes the question nobody asked was the only piece of data that actually mattered.

And if, for one moment, you can stay a little longer in not-knowing — without filling the gap, without deciding, without giving anyone relief, not even yourself — maybe that’s where the first question worth asking begins.

I still don’t know what that question is for you. And maybe that’s exactly where the conversation should start.

If this kind of reflection resonates with you, the Coaching & Você blog holds hundreds of pieces that walk this same line between human behavior, leadership, and relationships — worth getting lost in.

#sensemaking #consciousleadership #organizationalculture #marcellodesouza #marcellodesouzaoficial #coachingevoce