Strategy: HR Strategy as a Decision-Support Substrate (And Why the Twelve-Initiative People Strategy Will Never Land)
The fourth banner piece under the four-S synthesis argues the S that organizations spend the most money articulating — and the one that fails most quietly when the other three are missing.
The deck was forty-eight pages.
It had been built by a respected boutique. Six weeks of executive interviews, three internal workshops, a culture diagnostic that involved focus groups in seven countries. The deliverable was a People Strategy with twelve named initiatives organized under four pillars under one north-star statement. The pillars had names like Talent Ecosystem of the Future and Inclusive Performance Culture. The initiatives had crisp titles, owners, milestones, and what the consultant had labeled guiding metrics.
The CHRO presented it to the executive team on a Tuesday. The CEO asked good questions. Two of the executives nodded approvingly. One executive — the new head of revenue — asked a sharper question: which of these twelve initiatives, if we executed them perfectly, would have the largest effect on which business outcome, and how do we know?
The CHRO did not have an answer.
The deck had answered what to do. It had not answered what decision the doing was supposed to inform, what alternative we were choosing it over, what information would change our choice, and how we would know whether the choice was working when the year ended. The strategy was a list of priorities. It was not a decision-support apparatus. When the CFO came back six weeks later asking for a $14M budget commitment against the twelve initiatives, the people-analytics function had nothing to offer except the consultant's projected ROI tables — which had been built without access to the company's actual data, and which the function had not been involved in producing.
The CFO funded six of the twelve. By Q3, two had quietly stopped reporting metrics. By Q4, the deck had been retired with the same ceremony as last year's People Strategy and the year before's.
That story is a parable about strategy-shaped absence — what happens when the function has the science, the statistics, and the systems, but the strategy layer is built as a deliverable rather than a substrate. The output looked strategic. The output was not, in the operational sense the other three S's require, decision-bearing.
I have been in enough versions of that room to say this plainly: most HR strategy in 2026 is the wrong shape. Not because the strategists are bad — they're usually competent professionals doing the best work the format permits — but because the format is built for a deliverable that explains itself in a slide deck, and the work that actually compounds is built for a substrate that informs the next decision the company has to make.
This piece is the long argument for the Strategy S in the four-S synthesis — strategy, science, statistics, systems. The S that should be the easiest, and the one that fails most often in the same way for the same reason.
What "Strategy" means here (and what it doesn't)
When I say strategy in this context, I do not mean the document. Twelve-initiative slide decks are documents. Pillars-and-priorities frameworks are documents. Strategy in the corporate-communication sense is one of the most-produced and least-acted-on artifacts in modern enterprise life.
The work is decision-support substrate. It has three layers that interact:
Decision-shape clarity. Every strategic initiative is a choice over alternatives under uncertainty. If the strategy doesn't name the alternatives, doesn't characterize the uncertainty, and doesn't specify what would distinguish a good choice from a bad one, it isn't a strategy. It is a list of priorities. The distinction matters because lists of priorities can survive any outcome ("we made progress on initiative seven") while decisions can be evaluated against what they were chosen over.
Lifecycle measurement. Every business of any size is, in workforce terms, three interlocking processes: attraction (the pre-employment relationship — sourcing, candidate quality, employer brand), activation (the employed-and-producing-value relationship — capability, alignment, motivation, support), and attrition (the exit relationship — voluntary, regrettable, retention dynamics). The Three A's framework names the load-bearing measurement set for HR. Strategy at the substrate layer is the discipline of which Three-A decisions matter most for the business this year, what data would change which decisions, and what is the value of acquiring that data before acting.
Decision-grade financialization. Strategy without a financial-translation layer dies in committee. Net Activated Value — the framework that ties workforce activation to dollar outcomes through CAMS index × ELV per segment — is one operationalization of the principle. The principle itself is broader: executive decisions in 2026 are made in financial language, and analytical work that doesn't translate into financial language doesn't reach executive decisions. The function's strategic posture is determined by whether it has built the translation layer or has chosen to operate in HR-vocabulary-only and complain about not being heard.
If that sounds technocratic, the technocratic discipline is what makes the difference between strategy that survives the next budget cycle and strategy that gets retired. The strategy-deck-as-deliverable pattern routinely produces brilliant artifacts that don't survive contact with the CFO. The strategy-as-substrate pattern produces work that informs the CFO's questions and gets funded.
Why the conflations matter
Three conflations bedevil HR strategy. Each kills a different kind of strategic work.
Priorities are not decisions. A list of priorities tells the team where to focus. A decision tells the team what to choose. Priorities can coexist; decisions require choosing among alternatives. A People Strategy with twelve initiatives, no named alternatives, no decision criteria, and no falsification conditions is twelve priorities — which is to say, twelve things the function might or might not do, none of which is structurally evaluable. The corrective is to shape every strategic initiative as a decision: we are choosing X over Y because the evidence on Z suggests A; we will know we chose wrong if B happens by month six.
Initiatives are not outcomes. Launching a new performance management system is an initiative. Performance management is now improving the percentage of employees who can articulate their team's goals is an outcome. Strategy decks routinely conflate the two — measuring did we launch and reporting that as strategic progress — when the strategic question is always did the launching produce the change the strategy was built around. The corrective is to measure outcomes at the lifecycle layer the strategy intends to move (Attraction / Activation / Attrition), with the financial translation that makes the outcome legible to executives.
Strategic ambition is not strategic capacity. The deck names twelve initiatives. The function has the operational capacity to execute three. The remaining nine are either deferred indefinitely, executed badly, or executed by groups outside HR. The CHRO is then accountable for outcomes the function never had the capacity to produce. The corrective is to size strategic ambition against operational capacity — to write strategies that the function can actually execute, with explicit acknowledgment of what is being deferred and why.
The failure modes — what breaks when Strategy is missing
Five patterns recur across the deployment record. None is fixable by hiring better strategists. All are fixable by treating strategy as decision-support substrate rather than as a deliverable.
1. The twelve-initiative dilution. The strategy lists twelve initiatives. None has the authority, budget, or attention to actually move. The function appears strategic; the function is structurally diluted. The corrective is the principal-issues discipline: name the three initiatives that matter most for the business this year, sequence the rest behind them with explicit deferral criteria, and decline to dilute the principal three with the rest.
2. The activity-measurement substitution. The strategy reports initiatives launched, programs deployed, training sessions delivered. These are activity metrics, not outcome metrics. The CFO recognizes the substitution; the strategy loses credibility one quarter at a time. The corrective is outcome measurement at the Three A's lifecycle layer: Attraction outcomes (offer-acceptance, employer-brand health, sourcing-funnel velocity), Activation outcomes (CAMS index, NAV translation, capability-build trajectory), Attrition outcomes (regrettable-rate, retention-of-target-cohorts, post-exit feedback).
3. The benchmark-as-strategy trap. Our target is industry-median engagement scores. This is a benchmark, not a strategy. It substitutes being normal for making a decision. When the benchmark says you're at target, the strategy is complete; when the benchmark moves, the strategy is suddenly behind without anyone having made an actual call. The corrective is to make the decision the benchmark is supposed to inform: given our position relative to the benchmark, and given our business priorities, what are we choosing to invest in over what alternative, and what would change the choice.
4. The strategy-disconnected-from-the-analytical-stack pattern. The strategy is built by one team (often with consultant help); the analytics function operates a different mandate (often a reporting-team configuration per the prior piece). The two functions don't intersect except at quarterly review. The strategy can't be evaluated because the function doesn't measure what the strategy named; the function can't drive strategic decisions because the strategy doesn't ask the function for input. The corrective is co-located authorship: the analytics function helps shape the strategy from the outset; the strategy is built around questions the function can actually answer; the measurement plan ships with the strategy, not as a follow-on.
5. The financial-translation gap. The strategy is articulated in HR vocabulary (engagement, capability, retention, culture). The executive team makes decisions in financial vocabulary (EBIT, NAV, productivity, headcount-to-revenue). The strategy reaches the boardroom and bounces. The function spends six months trying to translate after the fact. The corrective is financial translation at authorship: every strategic initiative carries its dollar-translation logic from day one, computed against the function's own canonical lifecycle measurements rather than retrofitted from someone else's projections.
What Strategy is for, in this field
The deepest misunderstanding is treating HR strategy as if its job were to articulate aspiration. It isn't. Its job is to make the decisions that have to be made anyway visible, evaluable, and informed by evidence the function is in a position to produce.
That reframing changes nearly everything about what a strategy looks like.
A strategy whose job is to articulate aspiration produces a deck. The deck explains the aspiration. The deck is celebrated at the off-site. The deck is filed.
A strategy whose job is to inform decisions produces an apparatus. The apparatus names the decisions the year will require (compensation increase budget, headcount allocation across business units, investment in capability-build vs hiring, response to attrition variance across teams). It specifies what evidence would distinguish a good choice from a bad one on each. It builds the measurement infrastructure that produces that evidence. It commits to the financial-translation layer that makes the evidence executive-legible. The apparatus survives the deck.
This is also why the People Analytics Toolbox's forecasting spoke matters strategically rather than only analytically. Forecasting under VOI reasoning is the engine that lets the strategic substrate ask the right next question. Given the decision in front of us, what is the expected value of perfect information, and the expected value of sample information? — translated to a strategic question: given the choice between Initiative A and Initiative B, would more data change our choice, by how much, and is the data worth acquiring? The function that operates with VOI substrate gives the executive team a fundamentally different kind of input than the function that operates with quarterly engagement reports.
The same logic threads through every other named artifact in the methodology spine. CAMS isn't a survey instrument; it's the operationalization of what activation means for any strategic decision that depends on workforce performance. NAV isn't a financial metric; it's the bridge that makes activation-strategy legible in CFO language. The Three A's framework isn't a taxonomy; it's the lifecycle structure that organizes which decisions need which kinds of analytical support at which time.
None of those artifacts replaces strategy. They are the substrate strategy depends on — the kind of strategy that survives the next budget cycle and the next CEO transition.
Why the other S's can't carry the missing weight
The temptation when Strategy is weak is to compensate by deepening the other three. The compensations don't work the way they appear to.
Without Science, strategy produces decisions about constructs nobody can defend. The strategic ambition is precise; the things being decided about are incoherent.
Without Statistics, strategy produces decisions on the strength of pattern-matching to charts that don't survive interrogation. The decisions sound rigorous; the underlying evidence is bluffing.
Without Systems, strategy produces decisions whose evaluation infrastructure doesn't exist. The function says we'll measure this next year; next year the function lacks the operational capacity to do so; the strategy degrades into anecdote.
Without Strategy, science produces honest constructs in service of questions nobody is acting on. Statistics produces honest estimates in service of analyses nobody is consuming. Systems produces beautiful infrastructure in service of capabilities nobody is calling. The other three S's collapse into function for its own sake — which is the longest-running pathology in people analytics and the easiest to defend until the next budget cycle, when it suddenly isn't.
The four-S synthesis exists because each S carries weight the others cannot substitute for. Strategy is the S that determines whether the function's work matters to the business — which determines, on any time horizon longer than a quarter, whether the function continues to exist.
A usable minimum (without asking you to be McKinsey)
The honest objection here is bandwidth. The CHRO has thirty meetings this week, a board deck due Tuesday, and a function whose existing strategy was articulated by a consultant the year before. We don't have time to rebuild the strategy as a decision-support substrate; we have a deck that worked last year.
Fine. McKinsey isn't the standard for seriousness; decision-grade discipline is. A usable minimum looks like this:
- Three decisions, not twelve initiatives. Every year, the function names the three load-bearing decisions the business will make that depend on workforce evidence — compensation increase, headcount allocation, capability investment, attrition response, leadership succession, structural change. Each of the three is shaped as a decision (what is being chosen over what), characterized for uncertainty (what would change the choice), and committed to financial translation (what is this worth in NAV-language).
- Outcome measurement, not activity measurement. Every initiative reports against the Three A's outcome layer (Attraction / Activation / Attrition) plus financial translation, not against did we launch or did we train.
- Co-author with the analytics function from day one. The strategy is built with the function in the room. The function names which questions it can answer, with what confidence, in what timeframe. The strategy is shaped around what the function can actually produce — and the function's investment plan is shaped around what the strategy will need next.
- Financial translation at authorship, not as retrofit. Every strategic initiative carries its NAV-translation logic the day it ships. The translation is computed against the function's canonical lifecycle measurements (Three A's outcomes), not against consultant-projected aspirational ROI.
- One annual decision-review. Not a strategy review — a decision review. What decisions did the year actually require? Which of the three named decisions did we inform with our analytical work? Which decisions were made without our input, and why? The answers are the function's leading indicators for strategic relevance.
None of that requires a Big Four engagement. It does require treating Strategy as decision-support substrate — not as the deliverable the function produces because the calendar demanded it.
If you're a CHRO reading this
Most CHROs operate in a strategic register the rest of the C-suite quietly tunes out. Not because the work is bad — usually the work is good — but because the register is wrong. The work is articulated in HR vocabulary and presented as program-and-initiative narrative; the rest of the C-suite operates in decision-vocabulary and financial-translation language. The translation gap is the structural reason HR strategy gets the budget it gets.
The leverage move isn't to articulate more strategic vision. It's to rebuild the strategy as decision-support substrate that the CFO and the CEO can actually consume. Three decisions per year, decision-shaped, NAV-translated, evidence-bearing. The function becomes the CFO's analytical counterparty rather than the executive committee's program-and-initiative reporter. The budget conversation gets fundamentally different.
If you're an analyst reading this
The strategic relevance of your work is determined upstream of the analysis. If the strategy doesn't name the decisions, you can produce brilliant analytical work that informs nothing. The career-leverage move isn't to deepen your statistical sophistication or build more dashboards — both are useful but neither moves the strategic relevance dial. The career-leverage move is to shape the strategy at authorship: get into the room where the strategy is being built, push for decision-shape clarity on every initiative, commit to financial translation at day one, and refuse to deliver analyses that don't connect to a named decision.
The first time you push back on a strategic initiative with what decision is this informing, what alternative is it chosen over, and what would change the choice, you will feel out of place. That is the feeling of the function leveling up. The discomfort is the discipline asserting itself.
The synthesis this piece belongs to
The four-S frame closes with Strategy because every prior S culminates here. Science gave you constructs that can defend a decision. Statistics gave you evidence that can inform one. Systems gave you the infrastructure to produce both at scale. Strategy is what determines whether the prior three accumulate into a function that the business uses — or remain a brilliant capability the business ignores.
This is the principal-issues thesis at the meta-level. Every domain has a load-bearing measurement set, and most domains are stuck because they haven't named theirs. People analytics is stuck for the same reason: the field has the science, the statistics, and the systems available to it — but most functions have not named the load-bearing decisions their work is supposed to inform, have not built the financial-translation layer that would make their work executive-legible, and have not committed to the decision-grade discipline that separates analytical functions that compound from analytical functions that evaporate.
The principal issue isn't whether to have a people strategy. Everyone has one. The principal issue is whether the strategy being operated is decision-support substrate — three decisions, named alternatives, characterized uncertainty, financial translation, outcome measurement — or merely aspiration-deck: twelve initiatives, four pillars, one north-star statement, retired at the end of the year.
The difference is what gets executed on Monday morning, what gets funded next quarter, and what the function looks like five years from now.
That's the sport. The ones who do it are playing a different one than the ones who don't.
Where this connects to the rest of the methodology spine
The four-S synthesis is the meta-framework. Inside it, the specific artifacts that operationalize each S have their own pieces:
- CAMS — the activation diagnostic (Capability · Alignment · Motivation · Support) — is treated in Why CAMS
- NAV — the financial-translation layer — is treated in Net Activated Value
- Three A's — the lifecycle measurement spine — runs throughout the methodology writing; a deeper drill-down piece is queued under the Strategy banner
- Principal-issues thesis — the meta-framework that names what's load-bearing across domains — is the spine the magazine itself is named after
- Rapid Collaborative Impact (RCI) — the methodology applied to HR-specific principal-issues sets — is treated in Why People Analytics Is Stuck and How to Unstick It
The four-S frame doesn't replace those artifacts. It names why they are the artifacts that compound — the structural reason they are decision-support substrate rather than deliverable, and the reason imitations of them tend to evaporate while the originals continue to land.