Strategic Alignment and Value Visibility: The $1B Goal That Never Reached a Ticket
Behind this page is an organisational change programme we ran inside a global research and advisory group, in one of the biggest business units it runs. Nine product and technology teams; revenue measured in hundreds of millions of dollars a year; a publicly stated goal of doubling it. To steer with evidence rather than opinion, we assessed the organisation across twenty-five scored dimensions, plus a qualitative pass for what scores can’t carry.
The analysis started with the map.
Start with the map
Correlation, not causation: every edge is a measured statistical association (p<0.05) from this engagement, not an asserted cause. Edges below |r|=0.35 are omitted for legibility; the rest are drawn thicker and more opaque the stronger they are. The map stays focused on Portfolio vision: hover any dimension to preview its own connections against it, and use the strength slider to keep only its strongest links.
The map opens centred on portfolio vision and strategy: whether people can see where the organisation is going. Its neighbourhood is the interesting part. Vision’s strongest pulls are how features and their benefits get defined, how testable the requirements are, and the shared planning cadence: the mechanics of turning direction into work. Strategy here doesn’t correlate with communication artifacts. It correlates with the machinery that carries it downhill, and this page walks what happens when that machinery drops the load.
What the numbers said
By the scores, the vision looks in decent shape: a median of 7 out of 10 across sixty-one respondents, with eight scoring it at 4 or below. Comfortable, with a visible tail of people it isn’t reaching.
What the words said
The two dark blobs not lining up is the chart.
Coded units number eight here, five negative to two positive. On the shared scale the words land at 3 and the scores land at 7. But the split is stranger than the average, because both of these were written inside the same organisation, in the same survey window:
“We have big vision.”
“I am not familiar with my organization’s Portfolio Vision and Strategy.”
Both are true. The vision existed at the top and evaporated on the way down, and the people it never reached felt the missing piece directly:
“Feels like there are always so many things going on instead of just a few clear wins that would set us up for success.”
Where it lived
Nine teams, anonymised, best to worst. Thin rows render wider and flatter; less data looks uncertain, not falsely precise.
Team by team, the medians fall from 9 to 5. Which makes sense if visibility of strategy depends on where you sit: the teams closest to the planning rooms scored it comfortably, the teams furthest away scored what actually reached them.
What the vision turned out to be entangled with
The map’s numbers, written out:
- Defining features and their benefits (r = .72), the strongest pull
- Testable requirements (r = .67)
- Cross-team planning cadence (r = .65)
And the edge that closes the triangle: defining features and business-value clarity move together at r = .72. Vision, feature definition, value clarity and the planning cadence form one tight structure in this data. The leaders’ retrospectives, run separately from the survey, walk the same break altitude by altitude:
“There is no direct connection between the work the teams are doing and the $1b goal.”
“Leadership must decompose the KPIs into something that makes sense. KPIs are not connected from individual/team/org levels.”
“We do not have a good measure of the customer value. The only measure is surveys.”
Goal, then KPIs, then measurement: each altitude below the top lost one link of the chain, so by the time work reached an engineer it was denominated in tickets, not value. The people at the bottom of that chain said so in almost exactly those words:
“The engineers get frustrated because the measure of success is missing. We shouldn’t be focused on how many tickets we’ve done rather than how much value they’re bringing.”
“When an engineer opens their laptop, they should feel their alignment to the overarching goal.”
Which is one coherent reading of why cadence sits inside the value triangle: the chain from goal to ticket is rebuilt, or not, in the shared planning rooms. A vision that only exists above the planning cadence is indistinguishable, from a team’s chair, from no vision at all. Interpretation of correlations, offered as such.
What happened next
Money that followed the assessment paid for training across the product and portfolio teams, whose people own the chain from strategy to feature to story. The organisation stayed engaged with the teams as things developed from there. Whatever those later numbers show isn’t something I can claim, that result belongs to them. What is transferable is the approach: before fixing how strategy is communicated, check whether each altitude below it can restate the goal in its own working unit. Where one can’t, that is the broken link.
A note on the data
A real engagement; an unnamed client, and it stays that way. Team names and identifying details are removed, and quotes are lightly edited for anonymity. Every chart and figure here is generated straight from the underlying assessment data, not typed in from memory, out of a pool of nearly 2,000 data points across both survey streams. One organisation’s measurement, correlations not causes: treat it as a pattern to watch for, never as a rule to follow.
Read Next
- Strategic themes: the cascade mechanism
The broken chain this client measured (goal to KPI to team objective to ticket) is exactly the cascade strategic themes exist to carry.
- Portfolio vision: traceability and freshness
“We have big vision” and “I am not familiar with the vision” in the same dataset is a traceability failure, not a communication one.
- Scoring Cost of Delay components
Business value can only be scored against visible strategy; without the chain, prioritization is denominated in tickets.