5 Ways Strategy Deployment Fails
Updated: Oct 13
39→60% selling time · 100+ sellers · 0 new headcount
That is the selling capacity of more than 50 sellers at the old rate, and nobody was hired to get it.
It came from strategy deployment: Hoshin-style, with an X-matrix, priorities, targets and a monthly review. Nothing exotic. The frameworks are decades old and the templates are free.
When strategy deployment fails, it isn't generally related to effort. Teams work hard on plans that were built in an order that guarantees they break. Here are the five failures I see most, what each one looks like from the inside, and the fix that held.
Why strategy deployment fails (it isn't effort)
A strategy deployment plan is a chain: breakthrough goal, annual priorities, metrics, targets, owners, action plans, review. Each link depends on the one before it.
When the plan breaks, it almost always breaks at a link somebody skipped because it felt like paperwork. The skipped links are boring or misunderstood. That is exactly why they get skipped.
1. Targets before definitions
What it looks like
The leadership team agrees to improve selling time, or pipeline coverage, and sets a target in the same meeting. Three teams go build the metric. Three formulas come back.
Everyone is green on their own math, and the first review is spent reconciling spreadsheets instead of making decisions.
The fix
Define every metric before anyone sets a target against it. Write down the formula, the source system, the refresh cadence and what counts. For selling time, that meant agreeing on what counts as selling before measuring how much of it happened. Then set the target.
It feels slow for two weeks. It saves months.
2. Data owners who never signed off
What it looks like
The metric is defined, but the person who owns the underlying data wasn't on the call. At the first review they point out that the field isn't populated the way everyone assumed. Now the number is in dispute, and a disputed number can't drive a decision.
The fix
The data owner signs off on every target to improve. Not a courtesy email. A named sign-off that says the source is right, the definition is right, and they will stand behind the number in the review. Once that was in place, reviews argued about the work instead of the data.
3. Action plans bigger than the team that owns them
What it looks like
Every priority gets an action plan, and every action plan is reasonable on its own. Add them up and the same handful of people are committed well past their calendar.
Nothing gets cut, so everything slips a little, and the plan dies of a thousand yellow and red statuses.
The fix
Size the plan to the team. Total the load by person before the plan is final. Anything that can't be staffed gets trimmed, paused or merged into something that can. A shorter plan that finishes beats a complete plan that stalls. Saying no in Q4 during planning is cheaper than explaining red in June.
4. A different dashboard for every priority
What it looks like
Each priority owner builds their own view. Different layouts, different date ranges, different rules for red. The monthly review becomes a tour of six formats, and nobody can compare one priority to another.
The fix
One dashboard design across every priority: same layout, same plan against actual, same red and green rules. Then one Kaizen roadmap that holds the improvement work for all of them. When everything looks the same, the exceptions jump out.
5. The review turns into a status meeting
What it looks like
The review has good attendance and good slides. Each owner reads their status. Red items get a promise to do better next month. Owners walk out with no actions and no accountability: no countermeasure, no owner for the change, no date. Nothing in the plan changes, which means the review did nothing.
The fix
Every yellow and red gets a countermeasure: what caused the miss, what changes, who owns the change, and when it shows up in the numbers. If the plan leaving the review is identical to the plan that walked in, it was a status meeting. Cancel it and send an email.
The fix that held
The five fixes share one idea: do the boring link before the exciting one.
Selling time moved from 39% to 60% because 100+ sellers and the teams behind them did the work, and a GTM technology roadmap put help where sellers already were.
Strategy deployment didn't do any of that. It made sure every one of those efforts pulled the same way, and that when one stalled, somebody noticed in weeks instead of quarters.
If your strategy review has become a reading of slides, don't start with a new template. Start with definitions.
Where this fits: Pattern, Proof, Temper
This Forge Note maps to the six stages of The Rustin Forge Cycle ©.
Pattern (Plan). Build the mold before you pour. Failures 1 to 3 live here: definitions, sign-off and capacity are all part of building the X-matrix.
Proof (Measure). Plan against actual, every month, red or green. Failure 4 lives here.
Temper (Improve). A countermeasure on every red, then reset the plan for the next cycle. Failure 5 lives here.
If this sounds like your plan, book a Spark Test. Thirty minutes, free, and you leave knowing where the leak is and what it's worth.
Dustin J. Richardson is the Founder & Fractional Operator of Rustin Forge Consulting LLC, based in Minneapolis and working worldwide.
