Alignment
The Divergence Map
How to map where stated intent and real behavior diverge.
Ask a single executive to rate how quickly their organization makes decisions and you get one perspective - informed, sincere, and incomplete. Ask five members of the same leadership team the same question, independently, and something far more valuable appears: the shape of their disagreement.
Key Takeaways
- When a leadership team discusses its own performance in a room, the conversation converges toward the most senior and most confident voices. Independent responses remove that gravity and reveal what people actually experience.
- A large gap on a single metric is itself an alignment problem and a diagnostic priority, regardless of which leader is right. The disagreement, not the average, is the finding.
- The divergence map is the fastest path from a diagnostic to a productive facilitated session, because the data does the confronting so the people do not have to.
Agreement hides. Divergence reveals.
When a leadership team discusses its own performance in a room together, the conversation converges. The most senior voice anchors it. The most confident voice amplifies it. People round toward consensus because consensus is comfortable and because no one wants to be the outlier who thinks the organization is in worse shape than everyone else seems to believe.
Independent responses remove that gravity. Each leader answers alone, with no visibility into anyone else's answers, describing the organization as they actually experience it. And what surfaces, again and again, is that the people running the same company are living in measurably different versions of it. The CEO rates Decision Velocity a 4.2 - decisions move. The COO, who sits closer to where decisions actually stall, rates the same dimension a 2.1. That is not a rounding error.
Why the gap is the diagnosis
A divergence of that size on a single metric is itself an alignment problem - and a diagnostic priority - regardless of which leader is right. If the CEO is right, the person operating the execution engine has lost confidence in it, and that belief will shape every decision they make. If the COO is right, the person setting strategy is doing so on a false read of what the organization can actually deliver. Either way, the gap is expensive, and you cannot see it at all until you measure each perspective separately and lay them side by side.
A team average hides the disagreement that produced it. The divergence map puts the disagreement in the center of the table, where it belongs.
What divergence maps predict
Leadership teams that diverge sharply on how they see the organization tend to share a set of downstream symptoms. Priorities fragment, because each leader is optimizing for the version of the organization they believe they're in. Initiatives stall at the seams between functions, because the people at those seams don't share a picture of what's wrong. And strategy fails at execution - not because the strategy was bad, but because the leaders carrying it out never agreed on the conditions they were carrying it into.
A tight divergence map, where the team's responses cluster, is a genuine asset. It means the leadership layer shares a picture of reality, which is the foundation every coordinated move is built on. A wide one is not a failure. It is the clearest possible signal of where the real work is.
The conversation that sells itself
There is a particular kind of leadership conversation that does not need to be sold. When a team sees, in front of them, that they rate their own Decision Velocity anywhere from 1.8 to 4.3, the room changes. The question stops being whether there's a problem and becomes why do we see this so differently - which is exactly the question that produces alignment. That is why the divergence map is the fastest path from a diagnostic to a productive facilitated session. The data does the confronting, so the people don't have to.
How to use it
If you lead a team, resist the temptation to run the diagnostic yourself and present the result. Have each leader complete it independently first. Then bring the divergence map to the table and start with the widest gap. Do not litigate who is correct. Ask what each person is seeing that produces their number. The answer to that question is usually the constraint.
About the Author
Dan Flynn
Creator of The Four A's of Organizational Readiness™ · Enterprise Transformation Executive · Author, Builders Build
Dan Flynn has spent thirty years inside federal, defense, and commercial organizations: diagnosing the invisible conditions that determine whether capable people produce extraordinary results. He is the creator of The Four A's of Organizational Readiness™ framework, has reached more than 11,000 professionals across corporate, civic, and national security contexts, and produced a documented 1,033% improvement in delivery velocity by changing organizational conditions: not people.
His book, Builders Build: The Four A’s of Organizational Readiness™, is forthcoming.
Related Articles
Map your team's divergence
The divergence map is generated by the Team Evaluation in the Executive Organizational Diagnostic, powered by Builder Intelligence™ and the Four A's of Organizational Readiness™. Set up a team evaluation to see where your leaders agree, and where they don't.