When Everyone Agrees, but No One Shares the Same Understanding

For much of my career, I believed that most challenges in architecture came down to technology. The wrong technology, the wrong solutions, the wrong priorities. Over time, I started noticing a different pattern. Often the problem wasn't that people disagreed. The problem was that they believed they agreed.

When the Words Are the Same

I have sat through many meetings where the conversation flows smoothly. Everyone nods, no one objects, the discussion wraps up, and we move on. It looks like we have reached consensus. Yet something interesting happens once people leave the room: they walk away with completely different understandings of what was actually said, decided, or expected. Not because anyone is trying to create confusion, but because the words we use rarely mean exactly the same thing to everyone.

A Single Word Can Hold Many Realities

Take a word like "product". Over the past few years, I have heard it used to mean an application, a team, a business area, a value stream, a budget responsibility, and a customer experience. Everyone uses the same word, yet they are looking at different things. When that happens, a discussion can drag on for a long time without anyone realizing they are actually talking about different problems. The same applies to words like platform, ownership, accountability, autonomy, and architecture. The more central the word, the greater the risk, because we tend to assume the understanding is shared.

Language Creates the Illusion of Shared Understanding

Communication feels simple because we have language. We have words, we have concepts, we can explain, describe, and discuss. But the difficulty is that we don't communicate through language alone, we also communicate from context, and the context differs from person to person. A developer, a product owner, an architect, a manager, and a business stakeholder can hear the exact same sentence and interpret it in five different ways, not because anyone is misunderstanding on purpose, but because they filter the information through different experiences, responsibilities, goals, and concerns. We assume we are seeing the same thing. Often, we are not.

Something AI Often Does Better Than People

One of the more interesting things I have discovered in recent years actually comes from working with AI tools. When I explain a problem to Copilot, something fairly simple happens. The tool tries to reflect back what it believes I mean. I read the response, correct what's wrong, add missing context, clarify what's unclear, and gradually we converge on a shared understanding.

What's interesting isn't that AI always gets it right, because it doesn't. What's interesting is the mechanism itself. It reflects understanding back. It tests comprehension. It makes misunderstandings visible. It made me start wondering how rarely people actually do the same thing for each other.

We Often Move On Too Quickly

In most meetings, we jump straight from what was said to our own interpretation. We rarely pause to ask: have I understood you correctly if I summarize it like this? Or: when you say "product", do you mean the team, the solution, or the value stream? Or: are we actually agreeing on the decision, or just on the wording?

These kinds of questions can seem minor, but they often reveal significant gaps in understanding. More often than not, the real conflict isn't in the proposed solution. It's in how the problem was framed, in who owns what, or in what people actually believe was decided.

Information Isn't Transferred Just Because It Was Said

Over time, I have arrived at a fairly simple view of communication. The sender is responsible for making sure the message is understood. The receiver is responsible for making sure that understanding is correct. Both sides carry responsibility. It isn't enough to say "I informed them", and it isn't enough to say "that's not how I understood it." Communication isn't finished the moment information is sent. It's only finished once the understanding is actually shared.

Decisions Need Shared Understanding

This has also changed how I think about decision-making. Many decisions get discussed endlessly, not because the choices themselves are difficult, but because the people involved are building their arguments on different understandings of the situation. On the surface, the discussion is about solutions. In reality, it's about understanding: what is the actual problem, what are we trying to achieve, who owns the consequences, what constraints apply, and what do the words we're using actually mean.

When these questions haven't been settled, the decision is weaker than it appears. It might be formulated. It might be documented. It might even be formally accepted. But that doesn't mean it's understood.

When a Decision Was Never Really Made

I've come to believe that many decision-making problems start right here. Not with bad intentions, not with a lack of competence, not even with genuine disagreement, but with everyone assuming the conversation was clearer than it actually was. Everyone believes the decision has been made. Everyone believes accountability is clear. Everyone believes the direction is shared.

Time passes, and only later does it become apparent that people have been acting on entirely different mental models. At that point, it can look like execution failed. But often, understanding failed much earlier.

Architecture Often Starts Before the Architecture Does

I have increasingly come to believe that many of the problems we frame as architecture problems, organizational problems, or governance problems actually start somewhere else entirely: with people seeing different things while using the exact same words. That makes communication more than a supporting activity. It makes communication part of decision architecture itself. When understanding differs, decisions become arbitrary. When understanding is shared, many decisions turn out to be surprisingly simple.

A Simple Rule

I have therefore become less concerned with whether people say they agree. I care much more about whether they can explain what they agree on, in their own words, from their own perspective, in a way others actually recognize. That is where shared understanding begins to take shape. Without it, agreement is often just a polite form of ambiguity. Because when everyone agrees, but no one shares the same understanding, it's usually only a matter of time before the problems resurface.