Black Friday & Cyber Monday Sale·50% off·ends in 0d 0h 0m 0s

Claim offer
9 min read ·

Measuring Whether Strategy Deployment Is Working

Bastin Bastin ·
Bastin Gerald, Founder and CEO at Profit.co

Bastin Gerald

Founder & CEO at Profit.co

Bastin Gerald is an entrepreneur, business strategist, and technology leader who pioneers AI-driven strategy execution at Profit.co. A published author, he has mentored over 250 leaders worldwide.

Organizations measure their strategy in detail and their strategy deployment not at all. Yet the process can be measured: whether targets are really negotiated, whether evidence arrives in time, whether decisions follow. A few process measures tell you where deployment is breaking.

How do you measure strategy deployment? Measure strategy deployment as a process across its three directions: the share of targets genuinely negotiated and changed, check-in timeliness, the share of initiatives linked to a result with an expected lag, the time from evidence to decision, dependencies agreed in writing, and how many of last year’s bets were judged. These show where deployment is breaking before results do.

Key Takeaways

  • →Strategic results are lagging indicators of deployment. Process measures are the leading ones.
  • →Down: targets negotiated, targets changed in negotiation, additive targets that add up.
  • →Up: check-ins on time, initiatives linked to a result with a lag, months from evidence to decision.
  • →Across: dependencies agreed by both sides. Learning: last year’s bets with a verdict.
  • →If no target changed during negotiation, it wasn’t a negotiation.
  • →There are no universal benchmarks. Track direction over time instead.

Why measure the process

Strategic results are lagging indicators of deployment. By the time a result misses, the deployment failure behind it, a target nobody owned, a dependency nobody agreed, an exception nobody saw, happened months earlier. Process measures are the leading indicators.

Each of the three directions leaves its own trace, which is what makes this measurable at all rather than a matter of opinion.

Eight measures

DirectionMeasureWhat it reveals
DownShare of targets negotiated, not just assignedWhether ownership exists
DownShare of targets changed during negotiationWhether negotiation is real: zero suggests announcement
DownAdditive targets that add up at agreementWhether gaps are found early
UpCheck-ins on timeWhether evidence is current
UpInitiatives linked to a result, with an expected lagWhether effect can be tested
UpMonths from evidence to decisionDecision latency
AcrossDependencies agreed by both sidesWhether shared results have shared commitments
LearningShare of last year’s bets with a recorded verdictWhether the organization learns

If no target changed during negotiation, it wasn’t a negotiation. If no bet was judged at year end, nothing was learned.

Score your deployment process.

Eight process measures, read off records you already have.

Book a demo →

What good looks like

There are no universal benchmarks, and inventing them would be misleading. Look for direction rather than a number: negotiated targets rising towards all of them; some, but not most, targets changing in negotiation; check-ins consistently on time; decision latency falling from quarters to a single month; and every major bet carrying a verdict at year end.

A different way to read the same evidence, as five stages rather than eight measures, is in A Strategy Deployment Maturity Model: Five Levels.

A worked example: a deployment scorecard

One organization’s deployment scorecard, two years apart. Read the direction column rather than the absolute numbers.

MeasureLast yearThis yearDirection
Targets negotiated30%85%Improving
Targets changed in negotiation0%25%Healthy
Check-ins on time55%88%Improving
Initiatives linked to a result with lag20%70%Improving
Months from evidence to decision51.5Improving
Dependencies agreed by both sidesNot tracked12 of 15New
Last year’s bets with a verdictNone9 of 11Improving

Row two is the one to dwell on. Going from no target changing to a quarter of them changing is the difference between announcing and negotiating.

What not measuring the process costs

An organization that measures only results finds out about a deployment failure two or three quarters after it happened, in the form of a number that missed. It then debates the number rather than the process that produced it, and the same failure repeats the following year because nothing about it was visible enough to fix.

Among published alternatives, OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. The question to put to either is whether the eight measures above can be read off the system’s own records, or whether someone has to reconstruct them.

Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Catchball records, check-in dates, correlation lags and strength histories sit in Essentials with OKRs and Goals, Balanced Scorecard, Hoshin Kanri and Strategy Roadmap, so the scorecard above is a report rather than a research project. Building the Business Case for Hoshin Kanri Software covers how to make that argument internally.

Where the numbers come from

Most of these come straight from the deployment system’s own records. In Profit.co, catchball sessions record proposals, changes and agreement; check-ins carry dates; correlations carry expected lags and strength histories; and countermeasure A3s close with verdicts. See the strategy deployment software page.

Which means each measure has an obvious source:

  • Targets negotiated and changed come from the catchball change table, where the proposal and every counter are kept.
  • Check-ins on time and decision latency come from dates the system already records, not from a survey.
  • Bets with a verdict come from closed A3s and correlation strength histories, which is also the input the next planning cycle needs.

That last one feeds the annual reflection described in Hansei: Reviewing Last Year’s X-Matrix Before Planning the Next.

Free Product Demo

Score your deployment process

A 30-minute walkthrough, tailored to your team.

Book a free demo
G2, Capterra and Gartner Rated 4.7/5 by 500+ Leaders

What happens in the call

01
Share how you work today

How your teams set goals, track progress and review results.

02
See Profit.co in action

Strategy, performance, projects and engagement on one platform, with AI.

03
Leave with a clear plan

A practical path to align teams, execute faster and drive results.

Questions this article answers

With process measures across its three directions, such as targets negotiated, check-in timeliness, initiatives linked to results, time from evidence to decision, dependencies agreed and bets judged at year end.

Results lag deployment failures by months. Process measures show where deployment is breaking while there is still time to act.

No reliable universal benchmarks exist. Track the direction of each measure over time instead.

That it was an announcement rather than a negotiation. Some movement, though not on most targets, is the healthy pattern.

The time between evidence arriving and a decision being taken on it. Falling from quarters to a single month is the direction to look for.

Related Articles

Strategy Deployment Software
9 min read · November 14, 2026

A Strategy Deployment Maturity Model: Five Levels

Last updated: Nov 14, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Strategy Deployment Software
9 min read · November 14, 2026

KPI Cascades: When a KPI Should Cascade, and When It Shouldn’t

Last updated: Nov 14, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Strategy Deployment Software
10 min read · November 14, 2026

Strategy Deployment in Government and Public Entities

Last updated: Nov 14, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Strategy Deployment Software
9 min read · November 14, 2026

Strategy Deployment Frameworks Compared: Hoshin, OKRs, Balanced Scorecard, 4DX

Last updated: Nov 14, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Strategy Deployment Software
9 min read · November 14, 2026

The Quarterly Strategy Review: Meetings That Change Decisions

Last updated: Nov 14, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Strategy Deployment Software
9 min read · November 14, 2026

The Roll-Up Problem: Why Averaged Progress Hides a Failing Strategy

Last updated: Nov 14, 2026 Bastin Gerald Founder & CEO at Profit.co Bastin Gerald is an entrepreneur, business strategist, and…

Bastin Bastin
Athena

Welcome to Profit.co 👋

How can I help you today?