When we deliver a score report to an HR director or an L&D team, the first reaction is usually to look at the aggregate number — the composite score that rolls all 12 dimensions into a single overall rating. We understand why. An aggregate is easy to compare. It tells you where someone ranks relative to the cohort. It gives you a one-number headline for a succession conversation.
But the aggregate score is nearly useless for development. A 6.4 overall tells you nothing actionable. It doesn't tell you whether the leader is strong on strategic dimensions and weak on relational ones, or vice versa. It doesn't tell you which specific behaviors are driving the low scores. It doesn't tell you whether two leaders with the same 6.4 have similar or completely different profiles. For development purposes, two leaders with identical aggregate scores can have completely opposite dimension patterns, and they need completely different development work.
This post is a plain-language guide to reading a dimension-level profile and using it to structure a development plan that's actually tied to the data.
The structure of the 12 dimensions
The 12 dimensions we score fall into four clusters. Understanding the clusters matters for interpreting individual scores because the clusters tend to correlate within a person — someone who is strong on Strategic Thinking often also scores well on Narrative Construction and Systems Awareness, because these skills share a cognitive foundation. When you see a very high score in one dimension of a cluster paired with a very low score in another, that's a signal worth examining closely because it's less common.
The strategic cluster covers how a leader reasons about context, time horizon, and causality: Strategic Thinking, Systems Awareness, and Narrative Construction. These dimensions assess whether the leader can hold complexity without oversimplifying, connect near-term decisions to longer-term implications, and build a coherent story from ambiguous data.
The relational cluster covers how a leader manages human dynamics in pressure situations: Conflict Navigation, Influence Without Authority, and Stakeholder Alignment. These dimensions assess whether the leader can manage disagreement without either capitulating or escalating unnecessarily, can build the buy-in needed to move cross-functional work forward, and can read the room accurately enough to adjust their approach when the dynamics shift.
The execution cluster covers the operational dimension of leadership: Accountability Framing, Decision Velocity, and Priority Clarity. These assess whether the leader owns outcomes when things go wrong, makes decisions fast enough under uncertainty, and is able to make and communicate clear choices about what matters most when there's more to do than resources to do it.
The presence cluster covers how a leader projects under pressure: Executive Presence, Emotional Regulation, and Communication Precision. These assess composure, the absence of defensive patterns, and the ability to be understood clearly and efficiently when stakes are high.
Reading the dimension profile: what to look for first
When reviewing a score report, start with the lowest-scoring dimensions, not the highest. This sounds obvious but in practice people often spend time discussing the high scores first, which is validating but not where development work should focus.
The lowest-scoring dimension in a profile is not automatically the highest priority for development, however. You need to cross-reference two additional factors: context sensitivity (did the low score occur in a situation that specifically elicited that dimension, or was it a context that didn't require it?) and criticality for the target role (is this dimension genuinely required for VP performance in the specific role this person is developing toward?).
Consider a director being developed for a VP of Engineering role. Her score report shows Narrative Construction at 4.8, which is low, and Influence Without Authority at 4.2, which is also low. Both scores matter, but Influence Without Authority is more critical for VP of Engineering than Narrative Construction — VP Engineering requires constant cross-functional alignment with Product, Design, and Data, and positional authority is limited in those contexts. Narrative Construction is more critical for VP roles with external-facing responsibilities. So the development priority order should be Influence Without Authority first, with Narrative Construction as secondary work, even though the raw scores are similar.
This role-specificity is why a generic "develop the lowest scores" approach to a dimension profile produces suboptimal development plans. The profile needs to be interpreted against the specific VP role the leader is targeting, not against a generic VP benchmark.
What a consistent gap pattern tells you versus a situational gap
A single session score is a starting point, not a conclusion. Session-to-session variance in dimension scores is real — a leader who scores 5.1 on Emotional Regulation in one session might score 6.4 in the next if the scenario context is different. Emotional regulation gaps are often situational: they show up reliably under specific conditions (financial pressure, peer conflict, board-level scrutiny) and not under others.
The difference between a consistent gap and a situational gap is important because they have different development implications. A consistent gap — one that shows up at similar levels across three or more sessions in different scenario contexts — suggests a behavioral default that is not context-dependent. That's the kind of gap that responds to deliberate practice because the behavior is wired enough that it fires across contexts. The leader needs reps in which the old default gets interrupted and a new behavior gets practiced in its place.
A situational gap — one that shows up sharply in specific scenario types but not others — suggests a skill that exists in the leader's repertoire but breaks down under specific pressure conditions. The development approach is different: rather than general practice, you want focused exposure to the high-pressure context that elicits the gap, so the leader can build resilience and automaticity specifically in that context.
In the score report, we flag whether a dimension score pattern is consistent across scenarios or concentrated in specific scenario types. That distinction should drive which type of development activity you assign. Consistent gaps get micro-drill work. Situational gaps get scenario repetition in the specific context that elicits the gap.
The interaction effects worth paying attention to
Certain dimension combinations interact in ways that matter for development planning. Two patterns we see frequently that aren't obvious from the individual scores:
High Decision Velocity paired with low Accountability Framing is a profile that shows up in leaders who move fast and rarely stop to own what went wrong. They make decisions quickly, which is valuable, but they also move on quickly from failures without processing what they own in the miss. This combination tends to produce a leadership style that peers describe as "fast but deflecting." The development priority is Accountability Framing, not Decision Velocity — the speed is an asset, but it needs to be paired with the willingness to stop and own outcomes when they're off.
High Narrative Construction paired with low Conflict Navigation is a different kind of problem. These leaders can tell compelling stories and build cases well, but they struggle when their narrative is directly contested. They often respond to pushback on their framing by either doubling down or backing down entirely, neither of which is appropriate. The development work here involves practicing what to do when the narrative breaks — when a board member challenges the framing, or a peer stakeholder pushes back hard on the logic. The storytelling skill doesn't go away; it needs to be combined with a toolkit for navigating the moment when the story gets contested.
Turning a dimension profile into a week-by-week plan
A development plan built from a dimension profile should have three tiers of work running simultaneously, not sequentially:
Tier 1 (most intensive) is the primary gap — the single dimension that is both lowest relative to VP threshold and highest priority for the target role. This gets micro-drill work two to three times per week for four to six weeks. The goal is measurable score improvement of 1.5+ points over that period.
Tier 2 (moderate intensity) is the secondary gap — typically the second-lowest dimension that is also role-critical. This gets one micro-drill session per week during the same period. It's background work while the primary gap gets the focused attention.
Tier 3 (maintenance) is the strength reinforcement — identify the one or two highest-scoring dimensions and design situations in real work that require those skills. This isn't development work in the traditional sense; it's calibrated exposure that keeps strong dimensions sharp while the development resources focus on the gaps.
After four to six weeks on this structure, run a verification scenario to see whether the primary gap has moved and whether the secondary gap has held. Then reassess and reset the tier assignments for the next development period. The plan isn't fixed — it adjusts based on what the data shows.
What a dimension profile can't tell you
Dimension scores tell you how a leader performs in simulated scenarios under specific conditions. There are several things they don't capture well: leadership effectiveness in very long-horizon strategic work (most scenarios run 30–50 minutes), the quality of relationships built over time rather than managed in a single high-stakes interaction, and performance in situations that are genuinely novel in ways that can't be simulated.
We're not saying a dimension profile is a complete picture of leadership readiness. It's a specific type of evidence — behavioral evidence from observable performance under pressure — that complements but doesn't replace other evidence sources like work product quality, team engagement data, and manager observation over time. The dimension profile is most useful when treated as one input in a portfolio of evidence, not as the single source of truth for VP readiness decisions.
Used that way, it's among the most specific and actionable inputs available. The 12-dimension structure gives you a place to look and a direction to develop toward that a single composite score, or a holistic manager impression, simply can't provide.