Catchball Process: How Hoshin Kanri Aligns Strategy Across Teams

Catchball is the structured, two-way dialogue in Hoshin Kanri where strategic objectives move down through an organization while feasibility, resourcing input, and operational insight move back up, refining the plan at every level before it is finalized. The name comes directly from the game: ideas are tossed between organizational levels the way a ball moves between players, with each exchange shaping the plan rather than simply relaying it.

Without a catchball, Hoshin Kanri collapses into conventional top-down goal-setting with an unusually detailed matrix attached. The X-matrix can be built flawlessly and the breakthrough objectives can be perfectly reasoned, but if the annual objectives and improvement priorities beneath them were never actually negotiated with the people executing them, the plan carries no more organizational buy-in than a memo. Catchball is the mechanism that prevents that outcome.

This guide covers what catchball is, how the exchange moves through organizational levels, what a genuine catchball session looks like in practice, and the common failure pattern that turns catchball into a rollout in disguise.

What Catchball Is and Why It Exists

Catchball exists to solve a specific weakness in conventional strategic planning: goals set at the top are frequently infeasible, poorly resourced, or disconnected from operational reality by the time they reach the people who must execute them. A senior leader setting an annual objective has visibility into strategic priorities but not into the daily constraints a specific production line faces. Catchball closes that gap by requiring genuine input from the level closer to the work before the objective is finalized.

Catchball is commonly associated with Hoshin Kanri, referring to the process of colleagues tossing ideas back and forth to improve them iteratively, so participants become informed of potential changes and have a chance to consider the implications for themselves and the broader organization. This distinguishes catchball from ordinary communication. A memo informs. Catchball negotiates, and the negotiation changes the plan.

Good to Know: Catchball is frequently confused with nemawashi, and the two work together but are not identical. Nemawashi is the informal, individual groundwork that happens before a proposal is presented. Catchball is the formal, structured, often group-based negotiation of specific objectives, targets, and resources between organizational levels.

Key Insight: Catchball is a genuine negotiation of objectives between organizational levels, not a communication exercise dressed up with a sports metaphor.

Catchball is one of the seven steps covered in [Hoshin Kanri: The 7-Step Strategy Deployment Process for Manufacturing], specifically the deployment phase where annual objectives get defined.

How Catchball Moves Through Organizational Levels

Catchball is not a single conversation. It repeats at each boundary between organizational levels, from executive leadership down through department managers to team leads and, in mature implementations, to the operators executing the daily work.

The Downward Pass

Each round starts with the level above sharing its objectives, targets, and the reasoning behind them with the level below. This is not a finished mandate. It is presented as a draft specifically to invite the response that comes next.

The Upward Pass

The receiving level evaluates the proposal against what it actually knows: current capacity, competing priorities, resource constraints, and risks the level above may not have visibility into. That assessment, including proposed modifications, returns upward as the second half of the exchange.

• Level above proposes objectives, targets, and supporting rationale
• Level below assesses feasibility against real operational constraints
• Level below proposes specific modifications, resourcing needs, or timeline adjustments
• Level above incorporates the feedback and either finalizes or issues a revised proposal for a further round

Key Insight: Catchball repeats the downward and upward pass at every organizational boundary until each level has genuinely shaped the objectives it will be accountable for.

What a Genuine Catchball Session Looks Like

A well-run catchball session has a specific and recognizable shape. A senior executive drafts a strategic objective with activities and targets, shares this pre-work with a cross-functional group of managers, and explicitly asks what they would modify, add, or delete. Discussion follows, edits are made, and the resulting plan is measurably different from the draft that opened the session.

Structuring the Session

Effective sessions bring together the right cross-functional group, typically representatives from every function the objective touches, rather than a single department in isolation. The facilitator's role is to draft a starting point specific enough to react to, not so polished that it discourages genuine edits, and specific enough that participants understand exactly what they are being asked to shape.

What the Session Should Produce

A catchball session should leave the room with a plan that has visibly changed from the opening draft, participants who understand the strategic reasoning behind the objective rather than just the number attached to it, and clear ownership of the specific commitments each function is now accountable for delivering.

Good to Know: One overlooked benefit of catchball beyond aligned strategy is capability development. Participants who engage in genuine problem-solving discussion during catchball build the same reasoning skills the objective ultimately requires them to apply, not just awareness of the target.

Key Insight: A catchball session succeeds when the plan visibly changes and every participant leaves with specific, understood ownership of their part of it.

Catchball Versus a Communication Rollout

The single most common catchball failure is running the process as a scripted communication tour while calling it catchball. The meetings happen, the language of dialogue is used, and the document still gets built, but the plan entering the room and the plan leaving it are identical.

Identifying a Cosmetic Catchball Process

The clearest signal is whether the objectives changed based on the input gathered. If every round of catchball across every level produces the same plan the executive team drafted at the outset, no negotiation actually occurred, and the alignment built is compliance rather than genuine ownership.

Why This Failure Is Costly

An organization that runs cosmetic catchball pays the full time cost of the process, the meetings, the scheduling, the perception of consultation, without gaining any of its benefit. Worse, participants who recognize the process as performative become more resistant to future planning cycles than they would have been under an openly top-down approach.

Key Insight: Catchball run without genuine plan changes produces the time cost of negotiation with none of its alignment benefit, and often more resistance than a transparent top-down process would.

Catchball and Resource Matching

A core objective of catchball, beyond alignment, is matching available resources to desirable projects so that only work that is desirable, important, and achievable gets authorized. This is a discipline conventional top-down planning frequently skips, setting objectives first and discovering resourcing gaps only during execution.

Surfacing Constraints Early

Because catchball requires the receiving level to assess feasibility honestly before the objective is finalized, resourcing conflicts, competing priorities, and capacity limits surface during planning rather than mid-year, when correcting course is far more expensive.

Preventing Overcommitment

Organizations that run genuine catchball consistently end up with fewer, better-resourced annual objectives than organizations that set goals top-down and catchball afterward as a formality, since the negotiation naturally trims objectives that the organization does not actually have the capacity to deliver.

Key Insight: Genuine catchball surfaces resourcing gaps during planning instead of during execution, producing fewer but better-resourced objectives.

Within the Lean System

Connection to Lean Principles

Catchball operationalizes the lean principle of respect for people by treating the input of every organizational level as a genuine input into the plan rather than a formality between the setting of strategy and its announcement. This distinguishes Hoshin Kanri, covered fully in [Hoshin Kanri: The 7-Step Strategy Deployment Process for Manufacturing], from conventional top-down strategic planning.

Connection to Lean Tools

Catchball is the formal counterpart to the informal groundwork covered in [Nemawashi: Japanese Consensus Building in Manufacturing]. Nemawashi prepares individual stakeholders ahead of time so that formal catchball sessions run as productive negotiation rather than surprise and defensiveness. The results of successful catchball rounds are recorded directly onto the [X-Matrix in Lean Manufacturing: Strategy Alignment Tool], where the negotiated annual objectives and improvement priorities become visible connections on the matrix.

Connection to Continuous Improvement

Catchball applies the same plan-do-check-act discipline covered in [PDCA Cycle: The Foundation of Continuous Improvement] to the negotiation phase of strategy itself: propose, assess feasibility, revise, and confirm. Objectives that emerge from genuine catchball are stronger candidates for sustained follow-through than objectives issued as mandates, since ownership built through negotiation carries directly into the execution and review steps that PDCA governs at the project level.

Frequently Asked Questions

Q: What is the catchball process in Hoshin Kanri?

Catchball is the structured, two-way negotiation of strategic objectives between organizational levels, where goals move downward and feasibility, resourcing input, and operational insight move back upward, refining the plan at each level.

Q: How is catchball different from nemawashi?

Nemawashi is informal, individual groundwork conducted before a proposal is presented. Catchball is the formal, often group-based negotiation of specific objectives and targets that follows, typically structured around cross-functional sessions.

Q: How do you know if catchball is working genuinely?

The plan changes measurably based on the input gathered at each level. If the objectives entering and leaving every round of catchball are identical, the process is a communication rollout rather than genuine negotiation.

Q: How many organizational levels does catchball involve?

It repeats at every boundary in the organizational hierarchy, typically from executive leadership through department managers to team leads, and in mature implementations extends down to the operators executing daily work.

Q: What happens to the objectives after a catchball session?

Finalized objectives and the resourcing commitments negotiated through catchball are recorded on the X-matrix, where they become the annual objectives and improvement priorities tracked through the review cycle.