Hoshin Planning: Best Practices

Most Hoshin implementations get the planning right and the alignment wrong. Here’s what the discipline of Hoshin Kanri actually requires, from breakthrough objectives to the catchball process.

Ask a plant manager to name their company’s top strategic priorities, and most can answer without hesitating. Ask a frontline team lead the same question, and you’ll often get a blank stare, or an answer that has nothing to do with what the plant manager said.

That gap between strategy and daily action is exactly what Hoshin planning (also called Hoshin Kanri or policy deployment) was designed to close. The framework connects an organization’s long-term vision to the specific actions happening on the plant floor every shift, but most organizations only implement the planning half.

At The Luminous Group, what we’ve found is that the alignment half is what makes or breaks success with Hoshin planning.

With that in mind, let’s look at how Hoshin Kanri is structured, how its key elements function in practice, and what separates organizations that get real results from those that are just spinning their wheels.

Learn how to improve follow-through on the plant floor in our free eBook, 5 Ways Quality Leaders Can Break the Accountability Trap

What Is Hoshin Planning?

Hoshin planning is a strategic management methodology that connects an organization’s long-term goals to the daily work happening at every level. The name comes from two Japanese words: hoshin, meaning direction or compass, and kanri, meaning management or control.

Hoshin kanri is often translated as “policy deployment,” a practice that goes beyond setting direction to continuously managing how it is executed.

The distinction matters. Most organizations that try Hoshin treat it as a planning tool. They build the vision, set the objectives, produce the X-matrix, and file the document away. A year later, they come back and wonder why their KPIs didn’t move.

To get it right, Hoshin Kanri must align action to your plan. Leaders and the second level of managers at a plant have to use the tool on a daily and weekly basis. If it doesn’t drive action, it’s just a planning exercise where you’re not getting any value, because actions are still scattershot and don’t contribute to strategic goals.

Key Components of Hoshin Planning

Hoshin planning is built on five interconnected elements, each tied to a specific level of the organization and a specific time horizon:

Organizational vision sets the long-term direction for the company’s purpose and aspirations over the next 10 to 20 years. It doesn’t change much year to year, but it anchors everything beneath it.
Breakthrough objectives (sometimes called strategic goals) are 3-to-5-year targets that move the organization meaningfully toward the vision. These are big, specific, and relatable goals. One clarification worth making: breakthrough objectives and strategic goals are the same thing. They’re not two separate levels, though they’re sometimes described that way.
Annual goals (or annual objectives) are the year’s progress markers toward the breakthrough goals. Each annual goal should trace directly up to a strategic goal.
Action plans are the specific initiatives and tasks that teams own to achieve the annual objectives. This is where daily work lives.
The Hoshin Kanri X-matrix displays all four levels in a single diagram, showing how each action connects up through annual objectives to breakthrough objectives. It’s a visibility tool, not the plan itself. Organizations that treat producing a polished X-matrix as the deliverable have done the planning half and left the execution half untouched.

The 7 Steps of Hoshin Planning

Hoshin planning follows a seven-step cycle. On paper, it would appear sequential. In practice, it’s a living loop, where information and results from one annual cycle feeds into the next.

Step 1: Establish organizational vision, mission, and values
Step 2: Develop breakthrough objectives
Step 3: Develop annual goals
Step 4: Deploy objectives via catchball, the iterative process by which goals cascade down and execution plans come back up
Step 5: Implement annual objectives through team action plans
Step 6: Conduct monthly reviews to track progress, adjust actions, and keep Plan-Do-Check-Act (PDCA) cycling
Step 7: Conduct annual review to assess overall performance and adjust breakthrough objectives if needed

Steps 1 through 3 tend to get the most attention. Steps 4 through 6 are where Hoshin programs succeed or fail.

Why Hoshin Kanri Takes Years, Not Months

One of the reasons why most organizations don’t succeed with Hoshin Kanri is that they give up before they ever see results. It’s a difficult, intensive tool to use compared with traditional quality tools like 8D problem-solving or failure mode and effects analysis (FMEA), requiring commitment and discipline over the long term.

For context, it took roughly three years of working Hoshin Kanri as a plant manager at a Toyota-partnered plant before we started to get it right:

Year one: I treated the annual review as the primary accountability mechanism, essentially running it like a budget. I set annual goals myself and planned to evaluate progress twelve months later. At year’s end, we had done some things, but they weren’t what we’d planned, because there was no process keeping actions connected to the goals between January and December.
Year two: We went the other direction and had just one strategic goal—reduce waste from 4% to 1%. Directing this to the engineering team, I held monthly reviews with managers, who had decided to focus on getting tools on time, among other annual goals. We had some successes, but people largely weren’t connecting anything to Hoshin Kanri because there was no weekly engagement.
Year three: Managers added weekly team meetings, which I attended on a rotating basis. We had PDCA discipline built into the action cycle to make adjustments on a weekly basis. This was deployed beyond engineering to include groups handling purchasing and on-floor supply to work cells.
Year four: This is when it started feeling like a success. We finally had what looked like a network tree with one strategic goal at the top, multiple annual goals beneath it, and a constantly churning layer of actions at the base. Furthermore, people had ownership of the system and could link every task back to our strategic goals.

An illustration: At the time, the plant was deploying a layered process audit (LPA) program to reduce process variation in five specific areas by 30% within a year (the annual goal). Because the entire team could trace the LPA program back to that goal, it became something they owned.

The Catchball Process: The #1 Element of Hoshin Planning

Of all the elements in Hoshin planning, catchball is the most critical and the most frequently misunderstood.

The name comes from the literal back-and-forth of throwing and catching a ball. In practice, it describes the iterative dialogue through which strategic goals are translated into execution plans.

The most important thing to note is that leadership only sets the strategic goals (the what). Teams are the ones responsible for defining their own annual goals (the how). Leadership responds, refines, and confirms. The process continues until there’s genuine alignment at every level.

The point is to refine the strategy through dialogue. Without it, Hoshin planning becomes exactly what it’s not supposed to be: a top-down list of assignments.

The Catchball Process: Real-Life Examples

When I was an engineering manager in the nineties, Toyota created a set of strategic objectives as part of Hoshin Kanri that they called 20-20-20:

20% fewer component count
20% cost reduction
20% fewer supplier rejections

Toyota set the direction from the top, but how each part of the supply base got there was theirs to define.

The seating group, for instance, determined it would reduce 18 stampings to 6 castings. The air intake group set different annual goals, as did the center console group. Each had to determine what they would do to reduce their piece count, costs, and quality concerns.

Same breakthrough objectives. Different annual goals. That’s catchball working as designed.

When I later managed three separate plants, this same dynamic played out across different sites:

One plant ran injection molding, another blow molding, and one had heavy assembly operations
Each plant manager set different annual goals toward the same strategic goals
The annual goals looked different because the plants were different. But they all traced back to the same breakthrough objectives.

So, what does bad catchball look like? If you tell your team, “Here are your three annual goals,” that’s not catchball. That’s an assignment. Your team hasn’t defined how those projects connect to the company’s strategic goals, whether they’re feasible, or generated their own ideas to get there. Without their participation on the how, the plan remains leadership priorities only, and you won’t see any genuine buy-in.

Building ownership into how goals get executed, rather than enforcing compliance with a top-down mandate, is what determines success with Hoshin planning.

Setting Breakthrough Objectives the Entire Team Understands

Another of the most common Hoshin mistakes has nothing to do with process. It’s starting with too many goals, stated in language nobody on the floor relates to.

The rule on breakthrough objectives: start with three. Maybe even one if you’re just getting started. Every strategic goal must pass a simple test:

Can a frontline operator understand it without explanation?
Does it describe a condition that’s visible and felt on the plant floor?
Is it memorable enough that someone could recite it six months from now?

If the answer to any of these is no, the objective won’t drive action.

“Improve OEE from 72 to 77” doesn’t pass that test. Most operators can’t relate to OEE, because it’s a composite metric that abstracts away the specific operational reality behind it. Reducing waste from 4% to 1%, on the other hand, does pass the test. Everybody on the floor knows you’re making too much scrap. It’s visible, felt, and relatable.

The first year I started with Hoshin Kanri, I set 10 to 12 strategic goals, most stated in KPI language my team couldn’t connect to their daily work. It didn’t work. Trimming that down to one goal was how we ultimately implemented Hoshin successfully.

The Review Cadence: Where Most Hoshin Programs Fail

Hoshin planning programs go off-track quickly as soon as daily firefighting starts crowding out weekly and monthly review meetings. That’s because without these check-ins, the connection between daily work and strategic goals dissolves very quickly over the course of the first year.

The leading indicator for your Hoshin Kanri program is whether the meetings are happening. Did the weekly meeting occur where the team discussed Hoshin actions? For example, was there a conversation where the team addressed reducing variation on a given machine? Engagement with the process is the leading metric, while the results are the lagging metrics.

Here’s what the cadence progression should look like in practice:

Plant manager holds monthly reviews with direct reports
Direct report teams meet weekly to discuss actions and progress
Plant manager rotates into team meetings held by direct reports to ask, “What are you working on, and how does it connect to our goal?”

Management commitment is paramount, and Hoshin Kanri won’t work if you’re doing it just because directors are requiring the plant to do it. Leadership engagement is what reveals when teams are working on things that have nothing to do with Hoshin objectives.

Technology’s Role in Hoshin Planning

Toyota worked the Hoshin Kanri methodology on chalkboards for decades before software existed. What digital tools now add to the process is acceleration of the PDCA cycle.

The strategic goal at the top of the network stays fixed. At the base, where teams are running actions and adjusting based on data, the speed at which information flows determines how many PDCA cycles a team can run between monthly reviews.

Consider what that looks like in the context of an LPA program:

In a manual audit system, a finding from Tuesday shows up in the Monday morning meeting, six days later. By then, conditions have changed and the opportunity to act quickly has passed.
A digital LPA system, on the other hand, flags findings immediately, as soon as the plant floor check is complete. The supervisor can assign a corrective action within two minutes, so the team can close the loop on the issue that day.
Faster data leads to faster action, which ultimately enables more PDCA cycles over a given period of time. Weekly and monthly meetings show more progress, and continuous improvement accelerates overall.

The People, Process, Tools framework is a critical concept here. People must buy in and you must have a disciplined process before technology can accelerate it. Tools layered onto a spotty review cadence or a catchball process driven largely from the top won’t get you far. But when people own the program and the process discipline is there, software becomes a genuine accelerant.

Making Hoshin Planning Work on the Plant Floor

Done right, Hoshin planning is one of the most powerful alignment tools available to manufacturing leaders.

Three things tend to separate organizations that get real results with Hoshin from those that stall out:

Leaders hold monthly and weekly reviews consistently
They use catchball as true two-way dialogue to build ownership of how teams achieve strategic goals
They state strategic goals in terms every team member can connect to their day-to-day work

The framework supplies the structure, but leadership has to supply the discipline: showing up to meetings, asking hard questions, and trusting teams with how to achieve the goals you set.

Hoshin Planning: Best Practices, Pitfalls, and the Role of Leadership