In a recent engagement with a large enterprise organization, an engineer on the leadership team had a moment of real clarity about himself.
He realized that every time a colleague brought something into the conversation that wasn’t a hard fact, a hunch, a wider view, a sense of where things might be headed, he pulled the conversation back to facts. Every time.
From where he sat, it had always looked like his colleague kept drifting off track. What he saw for the first time was his own part in it: the more he pulled toward facts, the more his colleague reached for possibility, each one certain the other was losing the thread.
Neither one was wrong. They were working from two different starting points, and until that moment, neither of them had a way to see it.
By Design
That moment didn’t happen by accident. We’d given the team a structured way to see how they each approach decisions: not a label, a clear picture of the actual gap in how they’re wired to work.
Most teams never get that. The differences stay invisible, showing up as friction and the same argument on repeat, never named for what it is.
Why It Stays Hidden
A fact-first thinker assumes everyone works from facts first, because that’s the only way they’ve ever operated. A possibility-first thinker assumes the same about their own approach. Neither one experiences their own lens as a lens. It just feels like how things are.
That’s why teams think they’re aligned when they aren’t. Nobody sets out to misjudge how differently their colleagues see the world. They just never have a reason to question their own default.
The Pattern Most Teams Miss
Most leaders don’t lose sleep over disagreement. It’s visible, so you can manage it.
What stalls execution is a team that talks in circles, lands on something that sounds like agreement, and never realizes it’s covering two different pictures of the same decision. The conversation loops, someone restates the plan, everyone nods, and it sounds resolved. But “we’re aligned” is doing a lot of work in that sentence.
Because it ends in something that sounds like agreement, nobody stops to ask why the conversation had to loop twice (or more) to get there. Work starts, then stalls, decisions get revisited, and the leader gets pulled back in to referee something that was supposedly already settled. The conversation happened. Alignment didn’t.
The Real Cost
Left alone, this pushes a team toward one of two outcomes: they stay stuck in the same loop, or they stop having the conversation at all. People don’t usually get excluded because they’re incapable. They get excluded because the team has come to expect a certain kind of friction from them, and over time decides it isn’t worth the effort. That decision can look efficient, since meetings get shorter and decisions move faster, but it comes at a real cost: innovation slows, perspective narrows, and trust erodes long before anyone names why. Execution suffers either way.
What’s Actually Happening
It’s tempting to treat this as a personality clash, but it isn’t. The engineer wasn’t wrong to trust facts, and his colleague wasn’t wrong to bring in context. Both were doing exactly what they were wired to do. Left unnamed, it turns into “they’re missing the point,” and that’s when it becomes personal, not because it is, but because the real difference was never named.
Most leaders know their people are different, but few have built that difference into how the team actually works. Naming that a gap exists is the easy part. Seeing exactly where you diverge, and designing a way to close it, is the part that usually gets skipped.
What Shifts It
For the engineer, the shift was simple once he could see it: pulling every conversation back to facts wasn’t keeping the team on track, it was cutting off exactly the input they needed. His colleague wasn’t off course. He was covering ground facts alone couldn’t reach.
That recognition, not a personality reset, is what breaks the cycle, and it’s rarely limited to one person on one team. If your team feels aligned but execution keeps slowing down, the problem probably isn’t disagreement. It’s the assumption that everyone in the room already sees it the way you do, an assumption that’s easy to miss, because your own view never feels like an assumption. It just feels like how things are.
Where are you assuming your team sees things the way you do?
