The honest answer is that most leaders do not know. They communicate the strategy, they watch people nod, they get no objections, and they assume that means the message landed. MIT Sloan research found that only 28% of executives responsible for executing strategy can name three of their company's strategic priorities.
The gap between communicating and being understood
There is a version of this you have probably lived. You built the plan. You brought the team together. You walked through the priorities clearly, made space for questions, watched people engage. It felt like it landed.
Six weeks later, something happens that shouldn't. A decision gets made that contradicts the stated direction. A program drifts toward whatever funding is available rather than what the strategy calls for. A senior person, when you happen to ask them what they are working on, describes work that has no visible connection to the priorities you outlined.
The meeting worked. The transfer did not.
MIT Sloan Management Review published research showing that 97% of senior leaders said they had a clear understanding of their organization's priorities. When asked to describe those priorities in detail, just over half of those same leaders could do it accurately. If the comprehension gap is that wide at the senior level, the gap further down the org chart is not hard to imagine.
A separate study put the number at 95% of employees unable to articulate their company's strategy. The research framing varies, but the finding is consistent: communication does not equal comprehension. Hearing the strategy in a meeting and carrying it into daily decisions are two different things, and most organizations have no way to measure the difference.
If your team's strategic alignment feels invisible to you, that is the right instinct. For most organizations, it is. See also: what the alignment gap actually is and why it persists.
Why nobody raises their hand when they are confused
Before getting to what you can do about this, there is something worth naming directly: if you have been running all-hands meetings and asking "does anyone have questions?" and getting silence, that silence is not a clean signal.
Nobody raises their hand for a few predictable reasons. In a group setting, confusion about the strategic direction can feel like a personal failure. If the leader just presented the plan with visible investment, saying "I don't understand what this means for my work" carries social risk that most people choose not to take. They nod. They write things down. They wait for the meeting to end.
There is also a deeper problem. In many teams, confusion about strategy is not recognized as confusion. People have a sense of the plan, a rough mental model that feels sufficient. They assume the things they do not quite understand will become clear once execution starts. What they actually have is an approximation of the strategy, and approximations perform fine until they hit a situation the approximation does not cover.
This is where the nod becomes genuinely misleading. The person nodding is not being dishonest. They believe, in that moment, that they understand. The real gap is not between what they said and what they meant. It is between what they think they understood and what they will actually do when the strategy is tested.
What asking directly in a meeting tells you (and what it cannot)
Asking "does everyone understand the strategy?" in a group setting tells you one thing reliably: whether anyone is willing to publicly signal confusion in front of their peers and their leader. That is not the same as whether they understand.
Even one-on-ones have a ceiling. Leaders who have done listening tours describe learning genuine things, real information about alignment gaps that would not have surfaced in a group. But the people in a one-on-one with the executive director or the principal or the VP of strategy have strong reasons to communicate competence. The setting introduces pressure even when the leader works hard to reduce it.
One ED described running structured individual conversations with every employee using four specific questions. The insight was real and valuable. It also took months, could not realistically be repeated quarterly, and still filtered through the social dynamics of a direct conversation with leadership.
Direct asking is not useless. It is incomplete. What you get is a filtered, socially curated version of your team's relationship to the strategy. What you need to know is what happens when you are not in the room.
This is directly connected to why engagement scores can look fine while execution is struggling. If you are seeing that pattern, there is a specific reason engagement and alignment diverge.
Three ways to find out without putting people on the spot
There is no zero-effort way to understand whether your team has genuinely internalized the strategy. But there are approaches that reduce social distortion and get you closer to an honest reading.
Watch decisions at the edge
The clearest signal of strategic comprehension is not what your team says about the strategy. It is what they do when they face a decision the plan did not explicitly anticipate. When someone makes a judgment call without escalating it, look at whether the call reflects the underlying strategic logic. Teams that have genuinely internalized a direction make those calls well, often without being able to articulate why. Teams that have heard the strategy but not internalized it get lost when they leave the path the plan explicitly mapped.
Create a written channel where confusion is low-stakes
A simple mechanism: a periodic written prompt asking team members to describe, in their own words, what the organization's top priority is right now and what they are doing that connects to it. The prompt is not a test. It does not go to a manager. The leader reads the responses directly. What you get is a distribution of how the strategy is actually being understood across the team, without the distortion of a live social setting.
The variation in those responses is the data. If ten people describe ten different top priorities, you have an alignment problem. If eight of ten descriptions reflect the same strategic logic, you have signal that the message penetrated. This is what measuring team alignment looks like in practice.
Ask about recent decisions, not about the strategy
Instead of "do you understand our strategic priorities," ask "tell me about a decision you made in the last two weeks." Then listen for whether the reasoning connects to the strategic direction without prompting. If people can describe their work and the rationale without you needing to draw the line back to the strategy, the alignment is real. If the connection only appears after you make it explicit, the comprehension is shallower than the nodding suggested.
Alignment Intelligence
Pulse surfaces comprehension and belief gaps at the team level without putting individual team members on the spot. Rather than asking how people feel about the organization, Pulse measures whether they can describe where the organization is going and whether they believe the direction is right, in a way that produces honest signal rather than socially curated responses.
What it actually looks like when your team genuinely understands the strategy
There is a texture to a team that has internalized the direction, and it is different from a team that is compliant but not aligned. The compliant team executes the tasks. The aligned team executes the logic.
When alignment is genuine, you see it in a few specific places. Decisions do not get escalated unnecessarily, because people have a working model of what leadership would decide and they can apply it themselves. New priorities get taken up quickly, because the team understands the underlying reasoning well enough to connect new directives to existing understanding. When the plan does not cover a situation explicitly, people make the right call without waiting to be told.
You also see it in what does not happen. Scope creep toward available funding instead of strategic priorities. Competing internal narratives about what the organization is actually trying to do. Programs that drift because nobody is sure whether they still fit the direction.
The fear many leaders carry, that finding out the team does not understand the strategy reflects badly on their leadership, is worth naming directly. The finding does not reflect poorly on the communication effort. Research confirms that frequency and quality of communication do not reliably produce comprehension. The organizations where this gets fixed are the ones where leadership creates a mechanism to find out the real state of alignment rather than inferring it from meeting behavior.
If you are seeing signs that your team is not moving in the same direction, the early indicators of misalignment are often visible before execution breaks down.
Find out where the comprehension actually breaks down in your org
30 minutes. We will walk through how Pulse surfaces alignment signal without putting team members on the spot, and what the data looks like in your specific context.
Frequently Asked Questions
How do I know if my team understands the strategy without putting them on the spot?
The most reliable approaches avoid direct questioning in group settings, where social pressure produces performative alignment rather than honest signal. Watch decision-making at the team level when leadership is not in the room. Ask people to describe their current top priorities and listen for whether those priorities connect to the strategic direction. Create low-stakes written channels where team members can flag confusion without attaching their name to it.
Why does my team nod in meetings but not execute on the strategy?
Nodding in a meeting is a social behavior, not a comprehension signal. MIT Sloan research found that only 28% of executives responsible for executing strategy could name three of their company's strategic priorities, even though those same leaders consistently said they understood the strategy when asked directly. The meeting creates pressure to perform agreement. Execution is where real understanding shows up, and the gap between the two is often larger than leaders expect.
Is it my fault as a leader if my team doesn't understand the strategy?
Not entirely, and that framing is less useful than understanding what actually broke down. Research consistently shows that communication volume does not equal comprehension. Leaders who communicated strategy frequently still found their teams couldn't articulate the priorities. The issue is usually not effort or intent. It is the absence of a mechanism that can tell the difference between a team that has heard the strategy and a team that has genuinely internalized it.
What does it actually look like when a team genuinely understands the strategy?
The clearest signal is judgment at the edges. Team members make good calls in situations the plan did not explicitly cover, and those calls reflect the underlying strategic logic. Decisions do not get escalated unnecessarily. When asked why they made a particular choice, people can connect it back to the direction without prompting. New staff reach functional alignment faster because the existing team can translate the strategy into practice, not just quote the document.