Strategy functions are among the most difficult parts of an organization to evaluate from a return-on-investment perspective. The investment side is reasonably clear: leadership time in planning cycles, external consulting fees, tooling, program management overhead, and the organizational disruption that comes with any significant strategic initiative. The return side is far more ambiguous. How do you know whether the strategy was responsible for the revenue growth, or whether the market was moving in that direction anyway? How do you account for the initiatives that were avoided because the strategy process identified them as low-value? How do you measure what did not happen?
Most organizations do not have a robust answer to these questions, and the absence of a measurement framework creates a recurring problem: when budget cycles arrive, strategy functions that cannot demonstrate their impact are vulnerable to cuts that prioritize areas with cleaner ROI narratives. This is not a hypothetical — it is a pattern that emerges consistently in organizations that have undergone significant cost restructuring.
The Two Categories of Strategy Investment Return
Before constructing a measurement framework, it is useful to be precise about the different kinds of value that strategy execution produces, because they require different measurement approaches.
The first category is initiative delivery value: the direct business outcomes that result from strategic initiatives being executed to plan. A market expansion initiative that delivers its revenue target generates measurable value. A cost transformation initiative that achieves its efficiency target generates measurable savings. These returns are attributable to the initiative, and the measurement challenge is ensuring that attribution is done rigorously rather than allowing the business line to claim credit for what the strategy function delivered.
The second category is execution quality premium: the additional value created by executing well versus executing poorly on the same initiative. This is harder to measure directly but is not unmeasurable. An initiative that delivers on time versus six months late has a compounding advantage in time-to-market, resource efficiency, and organizational momentum. An organization with a mature execution management capability consistently realizes more of its strategy portfolio than one without — meaning the same strategy plan produces more value when execution quality is higher.
Building an Initiative-Level Returns Framework
The most defensible approach to measuring strategy ROI is an initiative-level returns framework: tracking the committed outcomes for each initiative at the time it is approved, measuring actual delivery against those commitments, and aggregating both the financial and operational returns across the portfolio.
This framework requires three inputs that many organizations do not capture systematically. First, at initiative approval, the leadership team must document the specific outcomes the initiative is expected to deliver, with quantified targets and a timeline. "Expand into DACH market" is not a measurable commitment. "Generate €2.4M in first-year revenue from DACH market, achieving breakeven on market entry costs within 18 months" is a commitment that can be tracked.
Second, the initiative must have a defined cost basis: the fully-loaded cost of executing the initiative including leadership time, external spend, opportunity cost of internal resources, and tooling. Without a cost basis, you have a revenue or savings number but not a return ratio.
Third, outcomes must be tracked against the baseline: what the business would have achieved without the initiative. This is the hardest input to construct honestly, because it requires leadership to commit to a counterfactual assumption that may feel arbitrary. The right approach is not to achieve precision in the counterfactual but to be consistent in how it is estimated — using the same methodology across all initiatives so that relative comparisons are valid.
A Framework for Four Measurement Horizons
Different strategic initiatives have fundamentally different return timelines, and a single measurement cadence will either miss early value or undercount long-cycle returns. A practical measurement architecture uses four horizons.
The first horizon — twelve weeks — measures execution health indicators: milestone completion rate, workstream velocity, blocker resolution time, and owner engagement. These are leading indicators, not outcomes. Their value is predicting whether the initiative is likely to deliver the expected returns, not confirming that it already has. An initiative running at 60% of its planned milestone completion rate at week twelve is statistically more likely to underperform its return commitments than one running at 90%.
The second horizon — six months — measures early outcome signals: the early-stage metrics that precede the full financial return. For a market expansion initiative, this might be pipeline in the new market, first customer signed, team hired and onboarded. For an operational efficiency initiative, this might be process adoption rates, error reduction, and cycle time improvement. These signals are not the full return, but they are leading indicators of whether the full return is on track.
The third horizon — twelve months — measures direct financial returns: revenue contribution, cost savings, margin impact. This is where the ROI calculation becomes concrete. The fourth horizon — twenty-four to thirty-six months — measures strategic positioning value: market share change, capability uplift, competitive positioning improvements that take longer than a year to materialize. These are the hardest to measure but often represent the majority of value for significant strategic bets.
Where Most Organizations Under-Invest in Measurement
The most common measurement failure is not in the framework design — it is in the baseline capture. Organizations routinely approve strategic initiatives without documenting the pre-initiative baseline against which success will be assessed. When the initiative concludes, leadership cannot determine how much of the outcome was initiative-attributable versus the background trajectory of the business.
We are not saying that every strategic initiative must have a rigorous econometric baseline — the overhead would be disproportionate for smaller initiatives, and the methodology complexity would discourage rather than enable measurement discipline. The right standard is a documented estimate of the expected baseline, agreed at the time of initiative approval, with a clear methodology note. "Without this initiative, we project this business line to grow at its current three-year CAGR of X%" is a defensible baseline. "We didn't measure the baseline" is not.
Connecting Execution Health to Return Prediction
The practical value of pairing an execution management layer with a returns framework is the ability to update return predictions in real time rather than waiting for outcomes to materialize. If an initiative is running at 70% of its planned execution pace at the six-month mark, the expected return at twelve months should be revised downward — not as a punitive measure, but as accurate information for the leadership team making resource allocation decisions.
This connection between execution health signals and return forecasting is where the two disciplines — execution management and strategy measurement — become genuinely integrated. A COO who has both real-time initiative health data and a portfolio-level returns framework can answer two questions that are usually asked separately: "Are we executing well?" and "Is the execution producing the value we expected?" When those questions are answered together, the strategic portfolio management conversation moves from retrospective assessment to active management.
The Practical Starting Point
For leadership teams starting from a low-measurement baseline, the most effective entry point is not to retrofit a measurement framework onto the existing initiative portfolio. It is to begin with the next strategic planning cycle: require that every initiative approved in the next cycle enters with documented outcome commitments, a cost basis, and a defined measurement horizon. Build the muscle on new initiatives where the data infrastructure can be designed from the start, rather than trying to reconstruct it retrospectively for initiatives already mid-execution.
Within two to three planning cycles, the organization will have a portfolio of initiatives with consistent measurement architecture — and will begin to accumulate the longitudinal data needed to assess whether the strategy function is producing returns commensurate with its investment.
