Plan Intelligence
Your plan is in the deck.
Is it in the room where decisions get made?
Most plans are communicated. Few are understood. Fewer still are understood well enough to guide judgment when the leader isn't in the room. Plan Intelligence maps the gap between what you wrote and what your team actually carries.
Book a Meeting
The gap in every strategic plan
Communication is not the same as comprehension.
You ran the all-hands. You sent the deck. You had the leadership team present the priorities in every department meeting. The plan was communicated.
What you don't know is which sections dissolved before they reached the people doing the work. Which priorities made it into how decisions get made on Tuesdays. Which capabilities your team thinks they have and which they're quietly uncertain about.
Plan Intelligence surfaces that. Not as a judgment on your team. As a diagnostic that tells you where to focus the next conversation.
What plan intelligence surfaces
Section by section, role by role.
Which parts of the plan have strong clarity and which don't.
Not the plan as a single entity. Specific sections. The Q3 priority that was in every meeting. The capability shift that was in the deck but not in the conversation.
Where teams understand the plan but lack the capacity to execute it.
These are different problems. A team that doesn't understand the plan needs clarity. A team that understands but lacks capacity needs resources. Plan Intelligence separates them.
How well the plan traveled from leadership to front-line roles.
Leadership alignment and staff alignment are different things. The plan may be crystal clear at the director level and murky by the time it reaches the people executing it daily.
What to clarify or reinforce before the next planning cycle.
Plan Intelligence doesn't just describe the gap. It gives you a specific list of what needs to be addressed before you build on it. That's the input your next planning session actually needs.
In practice
Connecting your plan to what your team actually knows.
Describe your plan in your own language.
Not a template. Your actual strategic priorities, capability goals, and direction for the year. Pulse works with your plan as it exists, not a rewritten version of it.
Define what understanding looks like by role.
What does a program director need to know to make good judgment calls on this plan? What does a senior IC need to understand? The questions are derived from those definitions, not from a generic survey bank.
See the gap by section and by team.
After deployment, you see a map. Which sections have strong understanding and capacity. Which have understanding but not capacity. Which are genuinely unclear. The output is specific enough to act on before the next planning cycle.
Track how understanding builds over time.
As you clarify, reinforce, and act, the map changes. Quarterly deployments let you see what moved. You build an organizational record of how your plan takes root.
Why this is different from what you already have
Task completion is not the same as plan comprehension.
OKR tools tell you whether work is getting done. They don't tell you whether the people doing that work understand the plan well enough to make the right calls when something unexpected happens.
Plan Intelligence sits upstream of execution. It surfaces the understanding and capacity gaps before they become the results you can't explain. That's a different kind of intelligence, and it changes how you lead into each quarter.
See alignment dashboards
Map your plan against what your team knows.
We'll show you what Plan Intelligence looks like against your actual strategic priorities. 30 minutes.
Book a Meeting