The Invisible Cost of Misunderstanding
The Real Problem Wasn't Better Ideas
Like many people, I initially believed the answer was better ideas. If we could define a stronger vision, generate better concepts, or solve difficult creative problems more frequently, the project would naturally improve. Certainly, good ideas mattered. But over time, I began noticing that most struggling teams weren't suffering from a lack of good ideas.
They were suffering from something far less obvious: they didn't share the same understanding of what they were trying to accomplish.
Misunderstanding Is Invisible
That misunderstanding was rarely visible. People attended the same meetings. They listened to the same presentations. They reviewed the same documents. Everyone left believing they understood the plan. Then the work began.
Weeks later, subtle differences started appearing even amidst regular check-ins. Months later, those differences had become significant. Not because people ignored the vision, but because each person had unknowingly interpreted it through a different set of assumptions.
Communication Isn't Understanding
That was the first important lesson. Communication and understanding are not the same thing.
Communication is something we do. Understanding is something we build. One does not guarantee the other. Shared understanding is not a byproduct of collaboration; it is the product of deliberate, structured maintenance.
Goals Must Be Inclusive
But even deliberate communication fails if the goals themselves aren't inclusive.
For years, the games industry has suffered from a kind of hierarchical inertia—a hangover from systems and processes built 25 years ago. In that era, games were much simpler, and success was defined almost entirely by the core mechanic. The design team defined the vision, and the rest of the team executed it.
Today, that structure is largely obsolete. Games are massive, complex experiences. Consumers care deeply about visual fidelity, engine performance, and the emotional resonance of the world. Yet, many teams still operate under the ancient construct that "gameplay" is dictated by the designer alone.
The truth is, gameplay is a collection of all disciplines. An art discipline—like animation—is fundamentally responsible for fulfilling the mechanic. The mechanic is only as good as the animation supporting it, and vice versa. VFX is a massive UI component crucial to the experience. And if none of it runs because the engine can't handle the assets, the entire experience fails.
When leadership prioritizes a narrow definition of "gameplay," they orphan and demoralize the rest of the team. This feeds into outdated power dynamics rather than acknowledging a modern reality: teams need to understand it takes all disciplines to create a great experience. If goals aren't inclusive to everyone, they can't be understood by everyone.
Alignment Naturally Degrades
As I continued observing teams, another pattern emerged. Most organizations treated alignment as something that happened heavily at the beginning of a project or milestone. Goals were established. Roles were assigned. Responsibilities were discussed. The vision was presented. Everyone nodded, and then everyone went to work.
The assumption was that alignment had been achieved. In reality, alignment had only begun.
Because understanding doesn't remain fixed. It changes. Priorities shift. New information appears. People join the team, and others leave. Departments learn new things, assumptions evolve, and memory fades. Without anyone intending it, a team's shared understanding slowly begins to drift.
I eventually stopped thinking about alignment as something you create, and began thinking about it as something you maintain.
Leadership Restores Understanding
That distinction changed the way I approached leadership. If understanding naturally degrades over time, then leadership cannot simply establish alignment.
Leadership must continually restore it.
Participation Isn't Alignment
This also explained why so many meetings accomplished less than everyone expected. Leadership often confused participation with understanding. Everyone had been invited, everyone had heard the discussion, and everyone had an opportunity to speak. Therefore, everyone must be aligned.
But participation isn't evidence of understanding. Neither is agreement.
I've sat in countless meetings where everyone agreed upon the goal, the process, and the success criteria. The meeting ended, and everyone believed they had clarity. Months later, it became obvious that each discipline had built toward an entirely different definition of the goal and success criteria. As an example, the engineers had built for flawless, invisible efficiency, while the designers had built for disruptive, high-friction visual novelty.
The team agreed on the language. It never agreed on the meaning.
Maintenance Prevents Drift
The solution wasn't more meetings. It was better maintenance and more precise success criteria that captured all of the disciplines involved.
But where teams truly fail is in the mechanical application of this maintenance. They go to the effort of creating rules, goals, and processes, but rarely reassert them. People are busy, and they forget. They forget what happened at the last meeting. A human being generally needs to hear something seven times before they truly remember and understand it.
To create a repeatable system that is constantly nurtured, every meaningful discussion must become an opportunity to rebuild or reinforce understanding. This requires opening every formal discussion and review with a recap of what was agreed upon, who is involved, and by asking:
What are we trying to accomplish?
Has that goal changed?
Does the work we've produced actually reflect that goal?
What assumptions have changed since our last discussion?
What are we committing to before we meet again?
This sounds incredibly obvious, but it is critical that a team sticks to opening meetings with this recap without fail. Teams often do this once or twice and then stop. Soon after, the team is trapped in huge meetings where no one knows why they are even there or how they should contribute.
These opening conversations aren't repetitive. They are preventative. They prevent small misunderstandings from becoming expensive ones.
Clarity Enables Creativity
Roles and responsibilities turned out to be just as important. Many teams resisted defining them clearly because they worried structure would limit creativity and put people in a box. My experience was exactly the opposite.
Clear roles reduced confusion. When people understood who was responsible for making decisions, who owned the work, how every discipline contributed to the larger objective, and where the hand-offs were, meetings became more productive. Creative energy shifted away from negotiating ownership and toward solving problems.
Clarity didn't reduce creativity. It created the conditions that allowed creativity to flourish.
Meetings Have Different Jobs
The same principle applied to process. Not every meeting should serve the same purpose. Large meetings are excellent for communicating information, reviewing progress, and reinforcing shared objectives. They are far less effective at solving complex problems.
Problem-solving requires discussion. Discussion requires participation. Participation becomes increasingly difficult as groups become larger. Understanding isn't improved simply because more people are in the room. Often, the opposite is true.
Misunderstanding Is an Entropy Problem
Looking back, I no longer believe misunderstanding is primarily a communication problem. I believe it's a maintenance problem.
Human beings naturally drift. Our assumptions drift. Our priorities drift. Our understanding drifts. Creative people often drift even faster because they are naturally drawn toward novelty, exploration, and new possibilities. This isn't a flaw to be managed; it is the very engine of the creative process. It's simply part of being human.
The mistake is assuming shared understanding will remain intact without deliberate effort and consistent reinforcement.
Shared Understanding Is a Living System
Today, I think about leadership differently than I once did. Its purpose isn't simply to inspire people or help make smart, informed decisions. Its purpose is to continually maintain the conditions under which shared understanding can exist: clear goals, clear success criteria, clear roles, clear decision-making, clear process, continual reinforcement, and continual verification that the work still reflects the original intent.
Without those things, misunderstanding isn't surprising. It's inevitable.
Shared understanding is not a milestone. It's a living system. Left unattended, it naturally degrades. The responsibility of leadership isn't simply to create it once. It's to continually restore it before misunderstanding quietly takes its place.
Because the cost of misunderstanding is rarely small. Sometimes it's measured in missed opportunities, broken relationships, or failed products. Sometimes, it's catastrophic.
We can no longer afford to assume that understanding simply happens. We need to take a hard look at how we work together, constantly asking where unnecessary friction can be removed, and where clarity can be restored. Shared understanding may never happen by accident, but it can happen by design. And if we learn to maintain it intentionally, exceptional teams will finally become as consistent as their talent always suggested they could be.
