Catchball

What is Catchball?

Catchball is a goal-setting practice from Hoshin Kanri in which plans and targets are passed back and forth between management levels, so each level shapes and commits to its part of the strategy.

Updated November 2026 · 5 min read


Catchball takes its name from the image of throwing a ball back and forth. In strategy deployment, the ball is an idea, a goal or a plan. Senior leaders set the overall direction and pass it to the next level of management, who consider what it means for their area and what they can realistically achieve. They respond with questions, concerns and proposed targets, which leaders review and respond to in turn. The exchange continues until both sides agree on goals and plans that support the strategy and that the people responsible believe they can deliver. The final plan belongs to both levels, rather than being imposed by one on the other.

The practice is a core part of Hoshin Kanri, the strategy deployment method developed in Japan. It contrasts with purely top-down goal setting, where targets are simply assigned, and with purely bottom-up planning, where each unit sets its own goals without reference to strategy. For strategy and planning teams, catchball is a practical way to combine direction from the top with knowledge from the front line, improving both the quality of plans and commitment to them.

Definition of Catchball

Catchball is an iterative, two-way dialogue between management levels, used to translate strategic objectives into aligned goals, targets and plans at each level, through repeated proposal, feedback and adjustment until agreement is reached.

It is one way of building strategic alignment, and it is closely related to cascading goals and top-down and bottom-up planning.

How Catchball Works

Leaders set direction by sharing strategic objectives, the reasons behind them and initial expectations for each area. Explaining the reasons matters, since managers who understand why an objective was chosen can propose better ways to achieve it.

The next level considers the objectives, assesses what is achievable and proposes goals, plans and the resources they would need. Proposals often include risks and dependencies that leaders had not considered.

Leaders review the proposals, ask questions, challenge assumptions and suggest changes, and the two sides discuss until they agree.

The agreed goals then become the starting point for the next level down, and the process repeats until plans reach teams.

Catchball can also move sideways between functions whose plans depend on each other, so that dependencies are agreed as well.

What Makes Catchball Effective

Leaders must be willing to listen and change targets when the evidence supports it. If proposals are always overruled, the exercise becomes top-down goal setting in disguise.

Participants need good information about performance, capacity and constraints to make realistic proposals. Without it, proposals tend to be based on guesswork or on last year's targets.

The discussion should focus on how to achieve the strategy, not whether to pursue it, keeping the process constructive.

Time must be built into the planning calendar, since several rounds of discussion take longer than simply assigning goals.

Importance of Catchball in Strategy Deployment

Catchball builds commitment. People who help shape their goals understand them better and are more committed to achieving them. They are also more likely to raise problems early, since they feel ownership of the plan.

It improves the quality of plans. Front-line managers often know about constraints and opportunities that senior leaders do not, and catchball brings that knowledge into the plan. Plans built this way are more likely to survive contact with reality.

It also exposes problems early. Unrealistic targets, missing resources and conflicting priorities surface during planning rather than during execution.

Catchball and Financial Management

Catchball discussions often include budgets and resources, so that each level's goals are matched with the money and people needed to achieve them.

Exposing unrealistic targets early reduces the risk of overspending later on rushed recovery efforts.

When finance teams take part in catchball, they can test whether proposed plans fit within the overall budget and help resolve trade-offs.

Agreements reached through catchball give a clearer basis for tracking spending against goals during the year.

Common Challenges

Catchball takes time, which can be difficult when planning calendars are tight. Starting the annual planning cycle a few weeks earlier often solves this.

In hierarchical cultures, managers may be reluctant to challenge targets set by senior leaders, which limits the value of the dialogue.

Without clear rules for when discussion ends, catchball can drag on or turn into negotiation for easier targets. Setting a deadline for agreement and a clear process for resolving disputes keeps it on track.

How to Practice Catchball

Practicing catchball involves sharing direction clearly, inviting proposals, holding structured discussions and recording agreements.

It works best when built into the annual planning cycle with defined steps and deadlines. Many organizations limit it to two or three rounds at each level.

Preparing for Catchball

Share strategic objectives with clear explanations of why they matter and what success looks like.

Provide data on current performance and capacity, so that proposals can be based on evidence. Share the same data with every level.

Set a timetable for each round of discussion and agree who will take part at each level.

Running the Discussions

Ask each level to propose goals, plans and resource needs that support the objectives, and to explain the reasoning behind them.

Hold focused discussions where leaders and managers test proposals, discuss options and agree on targets. Keep a record of the main points raised.

Record the agreed goals, plans and resources, often on an X Matrix or similar planning document, and share them with the levels above and below.

Examples of Catchball in Strategy Deployment

The examples below show catchball in practice.

Both use illustrative figures. The first sets a realistic cost target, and the second resolves a cross-functional dependency.

In each, two-way discussion produced better plans than top-down targets would have.

Setting a Realistic Cost Target

A logistics company's leaders set an objective to reduce operating costs by 10%, and initially expect each depot to deliver the same reduction.

Through catchball, depot managers show that some sites have already made major savings while others have more room to improve. They propose targets ranging from 4% to 16%.

Leaders accept the revised targets, which still add up to 10% overall, and depot managers report much stronger commitment than in previous years. The company achieves a 9.5% reduction.

Resolving a Dependency

A software company's product team proposes a goal to launch a new feature in the second quarter, which depends on work from the platform team.

Sideways catchball between the two teams reveals that the platform team cannot deliver the needed work until the third quarter without dropping another priority.

Leaders agree to move the launch to early in the third quarter and adjust both teams' goals, avoiding a missed commitment later in the year.

Conclusion

Catchball is a goal-setting practice from Hoshin Kanri in which plans and targets are passed back and forth between levels until each level shapes and commits to its part of the strategy. It combines top-down direction with bottom-up knowledge.

In strategy deployment, catchball builds commitment, improves the quality of plans and exposes problems early. Sharing direction and data clearly, inviting real proposals, listening and adjusting targets when evidence supports it and recording agreements help organizations use catchball to turn strategy into plans that people believe in.