Strategy deployment is usually explained in the vocabulary of one method: hoshin, OKRs, the scorecard. Strip that away and it’s a simple idea with three moving parts, and most organizations are doing only one of them.
In this guide
- A plain definition
- Three moving parts
- What it isn’t
- Where the term comes from
- A worked example: the same strategy, deployed two ways
- Signs you need it
- Strategy deployment across a year
- Who is involved
- Common misconceptions
- Key terms
- Strategy deployment at different scales
- What the software side costs
- What software adds
- Questions this article answers
Key Takeaways
- →Deployment is what happens between the choices a small group makes and the work everyone else does.
- →Three directions: targets agreed down, evidence reported up, dependencies agreed across.
- →Most organizations run one direction well and the other two barely at all.
- →It isn’t planning, isn’t a cascade, isn’t portfolio management and isn’t one method.
- →Hoshin kanri is the best-known method; OKRs and the Balanced Scorecard deploy strategy too.
- →The symptom to watch for: roll-ups look healthy while the board’s key results don’t move.
A plain definition
A strategy is a set of choices: where to compete, what to change, what to stop. Those choices are made by a small group. The work that makes them real is done by everyone else. Strategy deployment is everything that happens in between.
More precisely, it is the process of turning strategic choices into targets and work at every level, and bringing back evidence of whether that work is moving the results the strategy depends on. The second half of that sentence is the part most definitions leave out, and the part most organizations struggle with.
Three moving parts
Down, up and across. Each one does a job the other two can’t, and each fails in a way of its own.
| Part | What it does | What failure looks like |
|---|---|---|
| Down | Turns choices into targets each level agrees to own | Targets handed down, disputed for months, quietly ignored |
| Up | Brings back progress and evidence of effect | Roll-ups show 80% progress while the key results don’t move |
| Across | Agrees the dependencies between functions | A division commits to a number another team controls |
Most organizations run strategy deployment in one direction. The other two are where strategies quietly fail.
What it isn’t
- It isn’t strategic planning. Planning decides the choices. Deployment makes them operational and tests them. See Strategy Deployment vs Strategy Execution vs Strategic Planning.
- It isn’t a cascade. A cascade copies goals downward. Deployment negotiates them and listens to what comes back. See Cascading Goals vs Negotiating Them: Why Top-Down Cascades Fail.
- It isn’t portfolio management. Funding and delivering projects matters, but finished projects don’t prove the strategy is working. See Purpose-Built Hoshin Kanri Tools vs Strategy Execution Platforms.
- It isn’t one method. Hoshin kanri is the best-known, but OKRs, the Balanced Scorecard and other frameworks can all deploy strategy. See Hoshin Kanri and OKRs on One Platform: Where Each Belongs.
Where the term comes from
“Strategy deployment” is the common English rendering of ideas developed in Japanese quality management under the name hoshin kanri, sometimes translated as policy deployment. Western organizations adopted the idea, often without the Japanese vocabulary, which is why many strategy offices practice strategy deployment without ever using the word hoshin. The history is in Policy Deployment: Where Strategy Deployment Came From.
A worked example: the same strategy, deployed two ways
An illustrative industrial group commits to growing services from 31% to 40% of sales over three years.
| Deployed as a cascade | Deployed in three directions | |
|---|---|---|
| Down | Each division receives a services growth goal | Each division negotiates its share; commitments are checked to add up to the group target |
| Up | Divisions report percent complete on their services initiatives | Divisions report initiative progress beside services share and contract attach rate |
| Across | Sales and service set goals separately | Service’s target is agreed with sales, whose contract model it depends on |
| Mid-year result | Initiatives 85% complete; services share flat; noticed at year end | Same initiatives flagged in month four: centers open, attach rate flat; routing fixed by July |
The strategy, the people and the initiatives are the same in both columns. The difference is whether the organization could see, in time, that its work wasn’t moving the result.
Signs you need it
| You notice | What it suggests |
|---|---|
| Roll-ups look healthy while the board’s key results don’t move | Progress is reported; effect isn’t |
| Targets are disputed months after they were set | Targets were assigned, not negotiated |
| A function misses because another function didn’t deliver | Dependencies were never agreed |
| The strategy office spends weeks building the monthly pack | Data is collected by hand across systems |
| Each planning cycle starts from a blank page | Nothing was learned from last year’s bets |
Strategy deployment across a year
| When | What happens | Direction |
|---|---|---|
| Planning season | Strategic choices translated into objectives; targets negotiated by level | Down, across |
| Every month | Owners check in; progress shown beside results; exceptions flagged | Up |
| When a gap persists | Corrective action agreed by everyone it commits | Across |
| Every quarter | Bets kept, changed or retired; targets reopened on evidence | All three |
| Year end | Each major bet judged; lessons feed the next plan | Up, into planning |
Deployment isn’t an event after planning. It’s the rhythm that runs through the whole year and connects one planning cycle to the next.
The planning half of that rhythm, stage by stage, is in The Hoshin Kanri Planning Cycle, Stage by Stage.
Who is involved
| Role | Part in deployment |
|---|---|
| Executive team | Makes the choices; decides at quarterly reviews |
| Strategy or transformation office | Runs the process; brings exceptions and decisions forward |
| Objective owners | Negotiate targets; report progress and evidence |
| Functional leads | Agree dependencies their colleagues’ targets rely on |
| Teams | Do the work; check in on their key results |
The strategy office’s role is often misunderstood as reporting. In practice its job is to keep all three directions moving.
Who belongs in the room when the choices are made is a related question, answered in Who Belongs in the Hoshin Planning Room.
Common misconceptions
- “It’s goal-setting.” Goal-setting is the downward third. Without evidence coming back and dependencies agreed, goals are set and the strategy still drifts.
- “It’s top-down.” The downward direction is negotiated, and the upward direction is where much of the learning happens.
- “You need hoshin kanri.” Hoshin is one method. OKRs, scorecards and combinations all deploy strategy.
- “It’s a project.” Deployment has no end date. It’s how the organization runs between strategy cycles.
- “Software does it.” Software keeps the directions connected. The negotiation, diagnosis and decisions are still people’s work.
Key terms
| Term | Meaning |
|---|---|
| Breakthrough objective | A multi-year change the strategy commits to |
| Cascade | Copying goals down the organization, often without negotiation |
| Catchball | Negotiating targets between levels until both sides agree |
| Contribution | A lower-level result that adds to a higher-level objective, with a weight |
| Correlation | A stated link between a piece of work and the result it should move |
| Expected lag | How long a result should take to respond to the work |
| Exception | Work that isn’t moving its result, or a delivery problem, flagged for review |
| Outcome lag | Work progressing while the result it should move doesn’t |
The hoshin-specific vocabulary is covered in more depth on the hoshin kanri software and hoshin kanri tools pages.
Two of these terms have articles of their own: The Hoshin Kanri Toolkit: Every Tool and How They Connect covers the artifacts, and Outcome Lag: When Priorities Are Green and KPIs Don’t Move covers the one that costs the most to miss.
Strategy deployment at different scales
| Organization | What deployment mostly involves | Typical gap |
|---|---|---|
| Single business, one site | Connecting leadership objectives to a few teams; monthly review | Evidence: finished work with no effect |
| Multi-division company | Negotiating divisional targets; dependencies between functions | Across: divisions committing to results they don’t control |
| Group of companies | Group objectives, entity contributions, shared KPI definitions | Down: contributions that don’t add up |
| Public entity | Outcome objectives, central unit negotiation, cross-agency work | Up: outputs reported, outcomes unchanged |
The three directions are the same everywhere; which one breaks first depends on the shape of the organization. See Deploying Hoshin Kanri Across Multiple Sites.
How long it takes to start
Weeks, not months, if you start with the strategy you already have: load current objectives and targets, link major initiatives to the results they should move, and run the next monthly review from that. Full negotiation of targets usually waits for the next planning cycle. Where you stand today can be checked against a strategy deployment maturity model.
What the software side costs
Deployment itself is free; keeping the three directions connected by hand is not. The cost shows up as someone’s week every month, and as decisions taken later than they could have been.
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 test for either is the same one this article sets: does the tool carry evidence back up, or only progress?
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Strategy deployment sits in Essentials alongside OKRs and Goals, Balanced Scorecard, Hoshin Kanri and Strategy Roadmap, so an organization can run all three directions without buying three products. What Drives the Cost of Hoshin Kanri Software lists the rest to total, and the 30-day free trial covers one monthly cycle, which is long enough to see whether evidence actually comes back up.
What software adds
Strategy deployment can be run on spreadsheets and slides in a small organization. As the number of levels, owners and methods grows, keeping the three directions connected by hand becomes a job in itself. Software should carry targets down with the agreements behind them, bring evidence up alongside progress, and hold the dependencies across. The tests are in How to Choose Hoshin Kanri Software: Seven Pass/Fail Tests.
Profit.co handles the three directions with catchball sessions for negotiated targets, an exception queue and four-quadrant view for evidence, and agreement from every function a target or corrective action commits. See the Hoshin Kanri software page.
In practice that comes down to three things:
- Down: a catchball session carries the proposed target, each level’s response and the agreement, with a balance check so the commitments below add up to the target above.
- Up: check-ins show initiative progress beside the result it should move, and an exception queue flags the cases where work advanced and the result didn’t.
- Across: a target or corrective action that depends on another function needs that function’s agreement before it closes.
If OKRs are the vocabulary your teams already use, the same three directions are available through OKRs and Goals on the same data model.
Free Product Demo
See your strategy’s three directions
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
The process of turning strategic choices into targets and work at every level, and bringing back evidence of whether that work is moving the results the strategy depends on.
Three directions: targets agreed down the organization, evidence of progress and effect reported up, and dependencies agreed across functions.
Hoshin kanri is the best-known strategy deployment method. Strategy deployment is the broader idea, also practiced with OKRs, the Balanced Scorecard and other frameworks.
Goal-setting is the downward direction only. Without evidence coming back up and dependencies agreed across, goals are set and the strategy still drifts.
Weeks, if you start with the strategy you already have: load current objectives and targets, link initiatives to the results they should move, and run the next monthly review from that. Full target negotiation usually waits for the next planning cycle.
Published alternatives include OnStrategy at $200 per month for unlimited users, and i-nexus with a free Starter tier for five users and $28 per user per month at Standard. Profit.co publishes two plans, Essentials and Enterprise, quoted against modules and scale rather than a public seat rate, with a 30-day free trial.
