The org chart shows you reporting relationships. It tells you almost nothing about what is actually happening.
Who influences whom without formal authority. Where trust has broken down between teams. What conflicts have been papered over but not resolved. Where people are afraid to raise problems. What information is being hoarded because sharing it has been punished before.
These dynamics are real. They drive outcomes. And they don't show up in any document you'll be sent.
---
What to Look For
Who talks to whom before meetings. Before a decision surfaces in the formal forum, two teams have usually already worked it out in a side channel. When that's happened, the meeting is a confirmation. When it hasn't — when every decision re-litigates the same fault lines — that's a signal about where the real coordination structure lives.
Whose judgment prevails in practice. Not on paper. When there's genuine disagreement in the room, whose view actually wins? If a VP consistently defers to another VP even on questions that should be in their domain, that gap between formal authority and real influence is worth understanding. It might be appropriate. It might be a trust problem wearing the costume of a hierarchy problem.
What doesn't get raised. A meeting where the stated agenda is X and no one mentions Y. Y is usually the real issue. Organizations develop patterns of silence around uncomfortable topics: a struggling customer, a technical risk, interpersonal tension that never gets named. Silence is data.
Where the energy goes. In healthy organizations, people argue about ideas without it becoming personal — the room gets more alive when something matters. In unhealthy ones, the room goes dead when certain topics come up. Not because people don't care. Because they've learned that caring leads nowhere good.
---
Common Patterns
False consensus. People agree in the room and disagree in the hallway. Signals: decisions that get revisited repeatedly, implementation problems that weren't visible during planning, people who say yes and don't execute. Usually means either fear of conflict or a politeness norm that has calcified into dishonesty.
The blame reflex. When something goes wrong, the first question is "whose fault?" rather than "what happened and what do we do?" Blame cultures create information hoarding, risk aversion, and late escalation. The executive's first response to a mistake sets the tone for whether problems surface early or get buried.
Hero concentration. One person or one team consistently carries load that should be distributed. Signals: burnout risk, succession vulnerability, a single point of failure in the system. The hero is often also the person making it hard for others to step up — sometimes intentionally, usually not.
The informal veto. Someone without formal authority who consistently blocks decisions. The org chart says they don't own this — but they can kill anything they don't like. The question is why. Is it a legitimate concern not being heard through formal channels? Or is it a power problem wearing the costume of due process?
---
Beware Single-Source Weather Reports
Do not confuse one loud source with truth. Skip-levels are useful and dangerous. So are trusted lieutenants, informal confidants, and the person who always has a crisp diagnosis of everyone else. Organizational weather is triangulated, not consumed.
Look for patterns across sources: what you hear in 1:1s, what metrics imply, what customers say, where decisions stall, what changes after meetings. Reacting to gossip is amateur hour. Ignoring repeated weak signals is also amateur hour.
---
What to Do When You See It
Reading dynamics is not enough. You have to navigate them.
Name the pattern, not the person. If you see a blame reflex, don't call out individuals for blaming. Talk about the pattern in a staff meeting or a 1:1 — make it a structural observation, not a personal accusation. This gives people permission to see it too.
Create a channel for what's not being raised. If silence around a topic is the signal, find a way to surface it without making it personal. Specific questions in regular forums, skip-level conversations, input mechanisms that don't require attribution. The goal is to give the silence a place to become speech.
Force the real disagreement into the room. False consensus requires a counter-ritual: before commitment, require dissent. Ask each leader what would make the plan fail, what they disagree with, and whether they can commit anyway. Agreement without surfaced objection is often just theater.
Clarify informal vetoes. If someone can block work without owning it, either give them formal decision rights or require the objection to be made in the decision forum. Hidden veto power is poison because it lets authority operate without accountability.
Redistribute authority, not just workload. Hero concentration is not solved by telling the hero to rest. Move decision rights, context, and customer relationships to other people before burnout or departure forces the issue.
Work the relationship, not just the structure. Informal influence networks persist because relationships are strong. You cannot restructure around a strong informal relationship — you have to change the relationship or work with it. That means direct conversation, trust-building, and time.
Heifetz's distinction is useful if you keep it grounded: many organizational dynamics are not solved by a new process alone. They require changed norms, new learning, and shifted relationships. That takes longer and doesn't have a clean solution. But seeing it clearly is the prerequisite.
