What You See Is Not All There is

I was coaching an agile team at a Fortune 500—mostly based in India, employed by a vendor company—and we kept hitting the same wall during estimation sessions. When I asked team members to estimate independently and reveal their answers simultaneously (a technique designed to surface different perspectives), two people would consistently submit a single shared estimate instead.

It kept happening. I kept constructing stories to explain it. At first I thought maybe they didn't understand the exercise. “Oh, we understand,” they assured me. Then, I thought maybe there was a cultural dynamic around disagreement that I wasn't reading correctly. “Not a problem, we all share our opinions,” they said. Out of explanations, I concluded that they must’ve been resistant to the whole agile approach. Getting through to them was going to be a big challenge.

Then, in a one-on-one conversation with one of the team members, I found out the actual reason: they shared a phone between two desks. One device, two people, one vote. 

How embarrassingly simple! A resource problem. Something I could potentially fix with an email. Now, this was a surprise. I had been so confident in my diagnosis, and the real reason hadn’t even occurred to me as a possibility.

Recently I’ve been reading Daniel Kahneman's Thinking, Fast and Slow, and there’s a concept in the book that sheds light on this experience and other common frustrations in leading change. Kahneman, who won the Nobel Prize in economics for his work with Amos Tversky on decision-making, calls it WYSIATI: What You See Is All There Is.

WYSIATI is a cognitive bias. When we make judgments, we work with the information in front of us. We don't pause to ask what's missing. We don't hold space for what we haven't yet learned. Instead, we construct the most coherent story we can from available evidence, and then we believe it.

That's exactly what I was doing with the team in India. I had data: one vote for two people, repeatedly. I had a story: something is wrong with the way these team members are engaging. The story was coherent. It just wasn't true.

The Problem Compounds When the "You" is Singular

WYSIATI is a bias we all carry. But here's what makes it especially dangerous in organizational change: most leaders are working with a narrow slice of the full picture and don't know it.

When the "you" in "what you see" is a single person, you get one limited vantage point, one set of assumptions, one interpretation of silence or resistance or slow uptake. The stories feel solid because they're internally consistent, but internal consistency isn't the same as accuracy.

Now imagine expanding the "you" to include multiple people with genuinely different viewpoints: people closer to the work, people who've been in the organization longer, people who hold information you'd never think to ask for. Suddenly "what we see" becomes a much richer dataset. The stories you construct have more to work with. The blind spots shrink.

This is what I mean when I talk about building a shared context for change. It's not a soft, collaborative nicety. It's a cognitive upgrade. You're deliberately expanding what you see to include what others see too. 

By the way, there's an irony worth naming here. The estimation exercise I was running—asking everyone to reveal their answers simultaneously rather than sequentially—was itself designed to counteract WYSIATI. The whole point is to prevent any one person's answer from anchoring everyone else's. I was so focused on applying the technique to the team that I completely missed that I needed to apply it to myself. 

What This Looks Like When It Goes Wrong

WYSIATI shows up in predictable patterns in change work:

A new leader joins to champion a change initiative. They've led similar efforts before, so they conduct an assessment, compare what they see to what they've seen elsewhere, and build a plan. What they don't have is the history—the previous attempts, the failed pilots, the decisions that seem baffling until you understand what they were responding to. The plan meets resistance almost immediately, and the leader is surprised.

A bold vision is proposed. The people asked to implement it have never seen anything like it succeed here. Their whole frame of reference—everything they've experienced in this organization—says it won't work. So they hedge, comply minimally, or quietly wait it out. Not because they're obstructionist, but because what they see is genuinely all there is for them, and what they see isn't encouraging.

A change leader shares a plan and asks for input. Silence. The leader reads silence as agreement and moves forward. Months later, they're frustrated and confused about why the rollout is struggling—unaware that the silence meant something entirely different to the people in the room.

In each case, someone made a confident judgment from incomplete evidence. In each case, the story felt true. In each case, it wasn't the whole story.

Getting Under the Surface

The iceberg is the right image here. What's visible is real, but it's a fraction of what's actually there, and it may not be the most meaningful fraction. The same is true in the data you collect, the conversations you have, and especially the stories you tell yourself about why people are or aren't on board with change.

Getting under the surface isn't just about slowing down (though that helps). It's about actively going to get what you're missing. Ask the question you haven't thought to ask yet. Have the one-on-one you've been putting off. Stay curious longer than feels necessary, especially when you think you already know the answer.

In my case, one conversation changed my perspective on the problem and provided a dramatically simpler solution. Not because the team member volunteered the information, but because I finally stopped explaining the pattern and started asking about it.

What you see is all there is…until you go looking for what you’re missing.