Catchball in Hoshin Kanri: How It Works and Why It Matters

Most organizations have a strategy. Far fewer have a reliable way to turn that strategy into aligned action at every level of the business.

Leadership sets ambitious goals. Middle managers translate them — imperfectly — into department targets. Frontline teams receive plans they had no input in shaping, that may not reflect operational reality, and that they feel little ownership over. The strategy stalls.

Catchball is the process designed to break that pattern.

It is the structured, two-way dialogue at the heart of Hoshin Kanri — the Japanese strategic planning methodology used by Toyota, Xerox, and thousands of other organizations globally. Catchball replaces one-directional, top-down mandates with an iterative exchange between levels of an organization until a plan is both strategically sound and operationally realistic.

This article explains what catchball is, where it came from, how the process works step by step, the two directions it operates in, and what makes the difference between catchball done well and catchball that wastes everyone’s time.

What Is Catchball?

Catchball is a structured communication process in which strategic objectives, proposals, or plans are passed between organizational levels — like throwing and catching a ball — with each level adding feedback, raising concerns, or refining the plan before throwing it back.

The name captures the mechanics well. A ball thrown in only one direction is not catch. Strategy deployed without feedback — sent down and never questioned — is not catchball. The defining feature is the return throw: the receiving party does not just accept the plan, they engage with it and send something meaningful back.

The process is a core component of Hoshin Kanri (also called Policy Deployment or Hoshin Planning), a strategic management system originating in post-war Japan and documented extensively in the quality management literature. The term “Hoshin Kanri” translates from Japanese as “compass management” — the idea being that the whole organization should be oriented and moving in the same direction.

Catchball is the mechanism that makes that alignment real rather than theoretical.

Where Catchball Came From

Hoshin Kanri was developed in Japan during the 1960s and 1970s, building on Total Quality Management principles introduced by W. Edwards Deming and Joseph Juran. Toyota adopted and refined the methodology extensively, making catchball a cornerstone of how it links executive strategy to daily operations on the production floor.

The process spread to Western companies in the 1980s and 1990s. A widely cited case study from 2001, published in the journal Long Range Planning, documented how Rover Group — a UK-based automotive manufacturer — adapted catchball as part of its Strategic Policy Deployment initiative to connect annual planning to quality strategy.

The research, conducted by Charles Tennant and Paul Roberts of the University of Warwick, noted that organizations attempting to deploy strategy without employee input consistently underperformed compared to those that used structured catchball dialogue.

Pierre Masai, a Toyota executive, has described catchball as essential to making Hoshin targets practical: without a structured way for employees at different levels to share their perspective and have it heard, ideas from people closest to the work simply do not reach the plan.

How Catchball Works: The Core Process

Catchball operates through a repeating cycle of throw, catch, and return until consensus is reached. Here is what each stage involves.

The Throw

A leader — typically at the executive or senior management level — presents an initial objective, strategic direction, or proposed target. The throw includes:

• The strategic priority this objective supports
• The expected outcome or result
• Any constraints, timelines, or resources attached to it
• The reasoning behind why this direction is being proposed

The goal of the throw is not to deliver a finished plan. It is to share a direction and invite engagement. A well-formed throw gives the receiving team enough context to respond meaningfully without leaving so little room that feedback feels pointless.

The Catch

The receiving team — mid-level managers, team leaders, or frontline staff, depending on where in the hierarchy the ball has been thrown — evaluates the proposal against what they know from the work itself:

• Is this objective achievable with current resources and processes?
• What constraints, risks, or dependencies are not visible from the level above?
• What would need to change for this to be realistic?
• Are there better ways to achieve the stated outcome?

This review is where ground-truth enters the plan. The people closest to the actual work know what the process is capable of, where the bottlenecks are, and what assumptions in the proposed target may not hold in practice.

The Return Throw

The receiving team throws the ball back, typically with:

• Proposed adjustments to the target, timeline, or approach
• Identified risks or dependencies that need resolution
• Specific tactics they believe will work at their level
• Questions that need to be answered before they can commit

The return throw is not a rejection of leadership’s direction. It is a contribution to shaping it into something that will actually work.

Iteration Until Consensus

The ball continues moving back and forth until both parties reach a shared commitment: a plan that is strategically aligned from the top and operationally grounded from the bottom. The number of iterations varies. Some objectives require one exchange. Others, involving significant resource trade-offs or cross-functional dependencies, require several rounds before the plan is solid.

The process ends when both sides can genuinely commit to the outcome — not when one side runs out of objections or simply complies.

Vertical vs. Horizontal Catchball

Catchball operates in two directions, and many organizations focus only on one.

Vertical Catchball

This is the most commonly described version. It moves objectives up and down the organizational hierarchy:

• Executive leadership defines breakthrough objectives for the year
• These are thrown to senior managers, who catch, evaluate, and throw back their department-level responses
• Senior managers then throw to team leaders, who engage the same way
• Team leaders work the same process with frontline teams

By the time the plan reaches the people doing the work, it has been reviewed and pressure-tested at every level. Each level has contributed to shaping how the objective will be achieved within their scope. The result is alignment — not just compliance.

Horizontal Catchball

Less discussed but equally important, horizontal catchball occurs between functions or departments at the same organizational level.

When one team’s objective depends on another department delivering something — data, components, approvals, shared resources — catchball between those departments surfaces the dependency early. Cross-functional objectives that skip horizontal catchball often fail not because the goal was wrong, but because a handoff between teams was never properly negotiated.

An effective Hoshin Kanri deployment uses both. Vertical catchball aligns the hierarchy. Horizontal catchball aligns the handoffs.

Also Read: How to Use Six Sigma to Optimize Public Transit Routing and Reduce Wait Times

What Catchball Is Not

Understanding catchball also means knowing what it should not become.

Catchball is not a veto process. The feedback cycle is meant to refine and pressure-test plans, not to block leadership direction or delay decision-making indefinitely. Teams that use catchball to endlessly resist change — or leaders who use it as a rubber stamp, ignoring every piece of feedback — are both missing the point.

Catchball is not a substitute for leadership clarity. For catchball to work, the initial throw has to be clear enough for the receiving team to engage with it meaningfully. Vague objectives — “improve customer satisfaction” without a metric or context — produce vague feedback. Garbage in, garbage out.

Catchball is not only for annual planning. Many organizations run catchball intensively during the annual planning cycle and then stop. The same structured dialogue is valuable during quarterly reviews, when significant changes arise mid-year, and when a cross-functional project needs alignment across teams.

Catchball is not a one-meeting event. The process takes time. In organizations new to Hoshin Kanri, the first year of proper catchball often takes longer than leaders expect. That investment pays back through faster execution — teams that helped shape the plan move faster and with less friction than teams receiving mandates.

Why Catchball Matters for Six Sigma and Lean Deployments

For organizations running Lean or Six Sigma improvement programs, catchball solves a specific and common problem: improvement projects that are technically excellent but organizationally disconnected.

A Black Belt team can produce a DMAIC project with significant calculated savings. But if that project was selected without input from the teams who will implement the changes — or if the solution requires actions that are not feasible with current staffing or equipment — the implementation stalls. The project goes on the books as complete. The savings never materialize.

Catchball applied to the project selection and scoping process changes this. When potential improvement projects are thrown to the operations teams who will execute them, their feedback shapes which projects get prioritized and how they are scoped. The result is projects that are both strategically aligned and operationally executable.

This connection between catchball and Six Sigma project selection is why Hoshin Kanri is taught alongside Lean Six Sigma in Black Belt programs. Strategy deployment and process improvement are not separate activities. Catchball is the bridge between them.

Also Read: How Six Sigma to Prevent Insurance Fraud Saves Billions?

Common Reasons Catchball Fails

Organizations that adopt catchball and then abandon it usually point to one of a few recurring problems.

Leaders who throw but do not genuinely catch. If leadership presents objectives but dismisses every piece of feedback as resistance or lack of understanding, teams learn quickly that the return throw is pointless. Participation drops. The process becomes a formality.

Teams that catch but do not throw back substantively. If the culture punishes disagreement or pushback, teams will send back nominal adjustments without raising the real concerns. Plans get approved that should have been revised.

No time dedicated to the process. Catchball requires structured conversations, not just email threads. Without dedicated meetings, review sessions, and documented exchanges, the back-and-forth collapses under the weight of day-to-day work.

Objectives that are too vague to pressure-test. Catchball works when the initial throw is specific enough for the receiving team to evaluate feasibility. High-level vision statements (“become the industry leader in quality”) cannot be caught — there is nothing concrete enough to respond to.

Too many objectives in play at once. Hoshin Kanri works best when organizations focus on a small number of breakthrough objectives — typically three to five at any given time. Organizations that try to deploy catchball across 15 or 20 concurrent priorities find that the process becomes unwieldy and nothing gets the attention it deserves.

Catchball and the Hoshin Kanri X-Matrix

In most Hoshin Kanri implementations, catchball is visualized and tracked using the X-Matrix — a single-page tool that maps the relationships between long-term objectives, annual priorities, improvement initiatives, and the performance metrics used to track progress.

The X-Matrix does not run catchball, but it provides the shared reference point that makes catchball conversations productive. When both parties in a catchball exchange are looking at the same X-Matrix, the conversation stays grounded in the strategic priorities and how each proposed plan connects to them.

If your organization is implementing Hoshin Kanri, building comfort with the X-Matrix alongside catchball is worth the investment.

Learn Hoshin Kanri and Strategy Deployment in Our Training Programs

Catchball, used well, is one of the most effective tools for closing the gap between what an organization intends and what it actually achieves. Understanding the process is a starting point. Applying it — running effective catchball conversations, designing an X-Matrix, connecting improvement projects to strategic objectives — requires structured learning and practice.

At Six Sigma Development Solutions, strategy deployment and Hoshin Kanri principles are covered in our Lean Six Sigma Black Belt program. We offer training in formats designed to fit the way your team works:

• Onsite training at your facility, applied to your organization’s actual strategy and improvement programs
• Live virtual classroom with a live instructor, structured exercises, and real-time discussion
• Online self-paced certification you can complete on your own schedule

Our Black Belt program covers the full connection between strategic planning, Lean deployment, and DMAIC project execution — so your improvement work is always aligned to what the business actually needs to achieve.

Lean Six Sigma Green Belt Training Brochure

Related Articles