When the Senior Team Agrees on the Words but Not on What They Mean

There is a category of alignment failure that is particularly difficult to detect and particularly damaging once it takes hold. It is not the failure that looks like disagreement: the senior team that argues in strategy meetings, that produces visible tension in reviews, that cannot reach consensus on a direction and knows it cannot. That failure is at least honest in its form. The failure I am describing here is the one that looks like alignment. The team agrees on the words. The strategy document is approved. The values statement is signed off. The transformation programme has a sponsor. And yet, in the weeks and months that follow, the programme stalls, the strategy produces inconsistent outcomes across the organisation, and the leaders who were in the room when the words were agreed find themselves acting in ways that appear to reflect fundamentally different understandings of what was decided.

THE PROBLEM IS NOT DISAGREEMENT. THE PROBLEM IS THAT AGREEMENT WAS PERFORMED RATHER THAN ACHIEVED. The words were agreed because they were general enough to accommodate the different interpretations each leader brought to them. The strategy meeting ended with consensus because consensus, in this context, means the absence of visible objection rather than the presence of shared understanding. And the organisation, which was told that the leadership team was aligned, proceeded to act on that alignment, which did not exist, and experienced the consequences of that absence in every interaction where the different interpretations of the agreed words produced different decisions, different priorities, and different messages to the organisation.

The most common condition that produces this failure is language that is sufficiently abstract to be genuinely ambiguous. Strategic vocabulary has a particular susceptibility to this. Words like “customer-centricity,” “agility,” “innovation,” “performance culture,” and “accountability” are used frequently enough in organisational contexts that they carry the weight of shared meaning while in fact accommodating a wide range of specific interpretations. When a leadership team agrees that the organisation needs to become “more agile,” each leader in the room is agreeing with a version of agility that reflects their function, their experience, their team’s current pressures, and their personal theory of what the organisation needs. The word is the same. The meaning is not.

A second condition is the social pressure that operates in senior leadership conversations, particularly in the presence of a CEO or powerful sponsor, toward premature closure. The discomfort of sustained disagreement, especially on strategic questions that have been on the table for a long time, creates an incentive to reach agreement sooner than genuine shared understanding would allow. Leaders who have reservations about the direction being proposed, or who understand the proposal differently from the way it is being presented, may choose not to surface that difference because the cost of extending the conversation appears higher than the cost of accepting the apparent consensus. This calculus is almost always wrong, but it is made regularly and in good faith by people who believe they are being collegiate rather than evasive.

A third condition is the assumption that agreement on words implies agreement on priorities. Even when a leadership team has a reasonably shared understanding of what a strategic word means, they may have very different intuitions about what that word implies for resource allocation, decision-making trade-offs, and the order in which competing demands should be addressed when they come into conflict. The strategy document states that the organisation is committed to both “innovation” and “operational excellence.” The leadership team agreed to both. But when the innovation initiative requires resourcing that creates operational risk, or when the operational excellence drive produces a process rigidity that constrains innovation, the leadership team discovers that it never agreed on which principle takes precedence in the conflict. That conversation was never had, because the document implied that both were equally important, and no one challenged the implication.

The intervention for this failure mode has to happen before the words are agreed, or in a structured re-engagement with words that have already been agreed but whose implications are already producing inconsistent outcomes. It cannot happen in the normal operating rhythm of leadership meetings, because the social dynamics that produced the apparent agreement in the first place are present in every meeting that uses the same format and the same relational patterns. It requires a structured facilitation process in which the explicit task is to test the meaning of the words rather than to reach agreement on them.

The most direct method is the scenario test. For each strategic word or phrase that carries significant weight, the facilitation process asks: given this word, how would we respond to this specific situation? Not hypothetically but as concretely as the scenario can be made. The scenario is chosen to put the word under pressure, to require a real prioritisation between competing legitimate interests, and to expose the interpretive differences that the word itself has been accommodating. The quality of the discussion the scenario produces is a direct measure of the depth of alignment the team actually has. THE DEPTH OF DISAGREEMENT THAT EMERGES IN SCENARIO TESTING IS NOT A SIGN THAT THE TEAM HAS FAILED. It is a sign that the scenario has done its job.

A second method is the explicit prioritisation exercise: not asking the team to rank values or strategic priorities in the abstract, which is easy and uninformative, but asking each leader to describe, from their own recent experience, a moment when two of the agreed principles came into tension, and how they resolved the tension. The diversity of responses across the leadership team is the diagnostic output. If the responses suggest that different leaders are resolving similar tensions in consistently different ways, the organisation does not have strategic alignment. It has strategic vocabulary, which is a much thinner foundation for consistent execution.

I facilitated a leadership team realignment session approximately eighteen months after the organisation had completed a widely communicated values and strategy renewal process. The trigger for the session was not a visible failure: the organisation was performing adequately on its headline metrics, and the leadership team was not in open conflict. The trigger was a pattern of inconsistent messages reaching the middle management layer, a pattern that was producing confusion about priorities, frustration among high-performing managers who felt they were receiving contradictory guidance, and a quiet but growing sense that the organisation did not actually know where it was going.

The realignment session began with a diagnostic exercise in which each member of the leadership team, independently, described what they understood “transformation” to mean for the organisation, and what they believed the organisation’s most important priority was for the next eighteen months. The outputs were more divergent than any member of the team expected. Three meaningfully different understandings of what the transformation was for were visible in the responses. One framing understood transformation as a technology and process modernisation effort. A second understood it as a cultural shift toward greater accountability and performance orientation. A third understood it primarily as a growth and commercial repositioning effort. All three framings were legitimately derivable from the language in the strategy document. All three had been present in the senior team throughout the eighteen months of execution. None of them had been named as distinct, because the strategy document had been broad enough to contain all three without requiring the team to choose.

The work of the session was not to decide which framing was correct. It was to produce a shared understanding of how all three framings related to each other, which took precedence at this stage of the organisation’s development, and what that prioritisation implied for the decisions the leadership team had been making inconsistently. The conversation was one of the most productive I have facilitated, precisely because the team was genuinely surprised by the degree of divergence the diagnostic had revealed, and that surprise created an openness to doing the work of alignment that the team had believed, until that moment, it had already done.

RK

Founder & Principal Consultant, ProventusHR

RK holds the Master Certified Coach (MCC) credential from the ICF and is a Certified Practitioner of the Marshall Goldsmith Stakeholder Centred Coaching methodology. He has facilitated over 400 leadership, culture, and coaching programmes across India’s most complex organisations.

About the Author

Rama Krishna (RK)

Founder Director, ProventusHR  ·  MGSCC Master Coach  ·  NDA Alumnus

Founder of ProventusHR and principal architect of ExperienceLearning and REEL|Life. 25+ years across leadership advisory, executive coaching, and experiential design across 14 industries. 9x Brandon Hall HCM Excellence Award winner (2022 to 2025).

Full Profile ›