Strategy Deployment: Hoshin Kanri Simplified for Small Businesses

Many small businesses have a plan and a busy team, but no reliable link between the two. The owner knows the year's priorities; the people doing the work know their daily tasks; and nobody is quite sure how one connects to the other.

Strategy deployment, known in lean management by the Japanese term hoshin kanri, is a method for building that link. It is widely used in lean management, including at Toyota, and its full form can look bureaucratic. The underlying ideas, though, are simple enough for a team of ten.

This guide explains what the method is, the few ideas that matter most, and a stripped-down version you can try this year.

What hoshin kanri is

The Lean Enterprise Institute (LEI) defines hoshin kanri, also called policy deployment, as "a strategic framework for building sustained high performance and producing results through structured plan-do-check-act (PDCA) thinking." It helps an organization align its functions and activities with strategic objectives "vertically and horizontally — from the CEO to the front line and across departments."

LEI's entry on strategy deployment adds the practical shape: a plan, typically annual, developed "with precise goals, actions, timelines, responsibilities, and measures."

In plain terms, hoshin kanri asks you to pick a few important goals, agree with the people involved on how each part of the business will contribute, and then check progress on a regular rhythm and adjust.

You do not need the full apparatus to get most of the value. Four ideas carry the method.

1. A few goals, chosen deliberately. The point is focus. A deployment plan with fifteen goals deploys nothing.
2. Connection from top to bottom. Every team-level priority should visibly support one of the business's goals, and every business goal should have someone working on it.
3. Dialogue instead of decree. Goals are tested against real capacity before they are final.
4. A regular check-and-adjust cycle. Progress is reviewed on a schedule, and plans change based on what the reviews show.

Catchball: testing goals against capacity

LEI explains that strategy deployment may start top-down, but once the major goals are set it "should become a top-down and bottom-up process involving a dialogue between senior managers and project teams about the resources and time both available and needed to achieve the targets." That dialogue is called catchball, because ideas are tossed back and forth like a ball.

The purpose is specific: to match available resources with desirable projects "so that only projects that are desirable, important, and achievable are authorized." LEI notes this is meant to avoid a common pattern of launching many improvement initiatives that are never completed for lack of agreement and resources.

A related term, nemawashi, describes gaining acceptance for a proposal by reviewing the idea and then the plan with stakeholders to get input and anticipate resistance before formal approval. LEI notes the word literally means "preparing the ground for planting."

In a small business, catchball might be one meeting and a few follow-up conversations. The owner proposes the year's goals; each person or team says what they could contribute, what they would need and what would have to give; the owner revises. The final plan is smaller than the first draft, and everyone has had a hand in it.

The A3 as a planning sheet

Lean organizations often capture a deployment plan on an A3, the single large sheet of paper LEI describes as a Toyota-pioneered way to summarize a problem, analysis, actions and action plan. LEI's strategy deployment entry shows an example A3 from a finance department director with boxes for performance, reflection on last year, analysis, an action plan covering who, what, when, where and how, and follow-up.

That layout is a ready-made template. If you already have a one-page strategic plan, a team-level A3 is its natural companion: one sheet per goal or per team, showing how that part of the business will contribute.

PDCA: the engine underneath

Hoshin kanri runs on the plan-do-check-act cycle. LEI describes PDCA as an improvement cycle based on the scientific method: plan the goals and needed changes, do the changes, check the results against performance, and act by standardizing the change or beginning the cycle again. It is also known as the Deming cycle, after W. Edwards Deming, who introduced the concept in Japan in the 1950s.

For strategy deployment, the "check" is your regular review, and the "act" is the decision that follows: keep going, change the approach, add resources or drop the goal.

A lightweight version for a small business

Here is one way to run it, using a hypothetical twelve-person machine shop as an example.

1. Choose two or three annual goals. The shop picks: reduce late deliveries, and win repeat work from two new industries.
2. Run catchball. The owner shares the goals with the shop lead, the sales person and the office manager. The shop lead says late deliveries come mostly from scheduling changes; sales says new-industry work needs certifications the shop lacks.
3. Write a sheet per goal. Each sheet shows the current situation, the main causes, three or four actions with owners and dates, and the measure that will show progress.
4. Link team work to the sheets. Each person can point to which sheet their improvement work supports. Work that supports neither goal is fine as daily business but is not called strategic.
5. Review monthly. Each owner reports status against the measure. The team decides whether to continue, adjust or stop each action.
6. Reflect at year end. Last year's sheets become the "reflection" box on next year's.

How it compares with OKRs

Objectives and key results are another popular way to connect goals to work. Google's re:Work guide describes OKRs as ambitious objectives with measurable key results, made public inside the organization and graded on a 0 to 1.0 scale, with a grade of about 0.6 to 0.7 considered the "sweet spot" for stretch goals.

The two methods share a lot: few goals, visible connection, regular review. In broad terms, hoshin kanri puts more weight on the capacity dialogue and the PDCA cycle, while Google's OKR guidance puts more weight on ambitious stretch goals and transparent grading. A small business can borrow from both. Just avoid running two parallel systems.

Pitfalls to avoid

• Deploying too many goals, so every team gets a long list and nothing gets finished.
• Skipping catchball, which produces plans that look aligned on paper but have no time behind them.
• Turning the A3 into a form-filling exercise. LEI stresses that the A3 is "a management process learned through dialogue," not just a sheet of facts and figures.
• Reviewing only at year end, which removes the "check" and "act" from the cycle.

Key takeaways

• Hoshin kanri, or strategy deployment, connects a few strategic goals to the work of every team through structured PDCA.
• Catchball tests goals against real capacity so only desirable, important and achievable projects go ahead.
• A one-sheet A3 per goal or team is a practical way to write the plan down.
• Monthly reviews supply the "check" and "act" that keep the plan honest.
• It can coexist with OKRs, but pick one system to run, not two.

Sources

• Lean Enterprise Institute, Lexicon: Hoshin Kanri
• Lean Enterprise Institute, Lexicon: Strategy Deployment
• Lean Enterprise Institute, Lexicon: Nemawashi
• Lean Enterprise Institute, Lexicon: A3 Report
• Lean Enterprise Institute, Lexicon: Plan, Do, Check, Act (PDCA)
• Google re:Work, Set goals with OKRs (originally published 2016)