Quality
Catchball: When Your Organization Stops Shouting Strategy Down the
Stairwell and Starts Playing Catch With It — and the Simple Act of
Throwing an Idea Back and Forth Until Both Sides Understand It Becomes
Your Most Powerful Deployment Tool
The Strategy That Died in
Translation
Picture this: The executive team spends three days in an off-site
retreat. Whiteboards fill up. Post-it notes cover every wall. The CEO
stands in front of the room and declares that this year, the
organization will achieve “zero critical defects across all product
lines.” The VP of Quality nods vigorously. The CFO calculates the
savings. Everyone shakes hands and goes home feeling like they’ve
changed the world.
Six months later, the quality engineer on Line 7 has no idea what
“zero critical defects” means for her process. The supplier quality
manager in the satellite plant never heard about it. The calibration
technician thinks it’s just another slogan for the lobby wall. The
second-shift supervisor heard a rumor at a toolbox talk but assumed it
was aspirational — like “world peace” or “paperless office.”
The strategy didn’t fail because it was bad. It failed because it was
thrown like a brick over a wall instead of tossed like a ball between
two people who both need to hold it.
This is the problem that catchball was invented to solve.
What Catchball Actually Is
Catchball is a practice rooted in Hoshin Kanri, the Japanese
strategic planning methodology that translates roughly as “direction
management.” But where most strategy deployment methods focus on
documentation — cascading goals through spreadsheets, scorecards, and
PowerPoint decks — catchball focuses on conversation.
The metaphor is deliberately simple. Think of playing catch in the
backyard. One person throws. The other catches, feels the weight of the
ball, adjusts their grip, and throws it back. Each throw is a little
more accurate. Each catch builds confidence. Neither person is passive.
Both are engaged. And after enough rounds, the ball travels smoothly
between them with almost no effort.
In organizational terms, catchball works like this: Leadership sets a
strategic direction — a “what” and a “why.” They throw it to the next
level. That level catches it, asks questions, interprets what it means
for their domain, and throws back their understanding along with a
proposed “how.” Leadership reviews, adjusts, and throws it back. This
continues until both sides genuinely agree — not just sign a form, but
actually understand and commit.
The critical difference between catchball and traditional top-down
deployment is the word “back.” In most organizations, strategy flows in
one direction: down. In catchball, it moves in both directions. And that
changes everything.
Why Most Strategy Deployment
Fails
Before we go deeper into how catchball works, let’s be honest about
why most strategy deployment breaks down. It’s not because people are
resistant or incompetent. It’s because the system is designed for
compliance, not comprehension.
Here’s what typically happens:
The Waterfall Illusion. Leadership develops strategy
in isolation, documents it in a polished presentation, and “deploys” it
through a series of cascade meetings. Each level receives the message,
nods, and passes it down. By the time it reaches the shop floor, it has
been through so many filters that the original intent is unrecognizable.
It’s like playing telephone with your company’s future.
The Metrics Trap. Goals are translated into KPIs
before anyone has a conversation about what they actually mean in
practice. “Reduce defect rate by 50%” becomes a target on a dashboard
before anyone asks: Which defects? Which lines? At what cost? By when,
specifically? And what resources will we need to reallocate?
The Sign-Off Theater. Deployment is considered
complete when every department head has signed the annual plan. But
signing is not understanding. Agreeing is not committing. And a
signature on a document nobody will open again for eleven months is not
a deployment strategy — it’s a filing exercise.
The Context Chasm. The executive who set the goal
has never stood at the press where the defect occurs. The operator who
creates the defect has never seen the customer complaint that it caused.
Neither side understands the other’s reality, and nobody has built a
mechanism for them to exchange that understanding.
Catchball addresses all four of these failures simultaneously. Not
through a new software platform or a different meeting structure, but
through a fundamentally different way of communicating.
The Mechanics of a Catchball
Round
Let’s get specific. A catchball round between a plant manager and a
quality manager might look something like this:
Throw 1 (Plant Manager): “Our strategic priority
this year is to reduce customer complaints by 40%. This line produces
60% of our complaints. I need you to figure out how to cut yours in
half.”
Catch 1 (Quality Manager): “I understand the target.
But when I look at the data, 70% of our customer complaints from this
line come from one specific defect type — seal integrity failures. To
cut complaints in half, I need to solve the seal integrity problem.
That’s going to require a cross-functional team, new testing equipment,
and probably a design modification. Can we scope the goal to ‘eliminate
seal integrity failures’ specifically?”
Throw 2 (Plant Manager): “Good. That’s more specific
than what I gave you, and it’s more actionable. But I need to make sure
the fix doesn’t slow down the line. Throughput targets still apply. Can
you build a plan that addresses seal integrity without sacrificing cycle
time?”
Catch 2 (Quality Manager): “Fair point. I’ll develop
two options: one that uses in-line detection with no cycle time impact,
and one that requires a brief process change with a calculated
throughput trade-off. I’ll present both with cost and risk analysis so
you can make the call.”
Throw 3 (Plant Manager): “That works. Let’s review
both options next Thursday. And bring the process engineer who knows the
sealing operation best — I want to hear from the person closest to the
problem.”
Notice what happened here. The plant manager didn’t just hand down a
number. The quality manager didn’t just accept it blindly. They shaped
the goal together. The target got more specific. The constraints got
clearer. The resources got identified. And both sides walked away with a
shared understanding that no spreadsheet could have produced.
Now imagine this happening at every level of the organization. CEO to
VP. VP to Director. Director to Manager. Manager to Supervisor.
Supervisor to Operator. Each round refines the goal, adds context, and
builds ownership.
The Seven Rules of
Effective Catchball
Over years of watching catchball work (and watching it fail), I’ve
identified seven rules that separate the organizations that get it right
from the ones that just go through the motions.
Rule 1: Start With “Why,” Not
“What”
If you throw a target without explaining the strategic rationale, you
get compliance — not commitment. The quality manager who understands
that seal integrity failures are causing warranty claims that threaten a
major customer relationship will fight harder than the one who’s simply
told to “hit a number.” Context creates motivation. Motivation creates
ownership. Ownership creates results.
Rule 2:
The Thrower Must Be Willing to Have the Ball Changed
If you’re not prepared to have your original idea modified by the
person catching it, you’re not playing catchball — you’re issuing
orders. The whole point of the exercise is that the person closer to the
work sees things you don’t. If their feedback doesn’t change anything,
the process is theater.
Rule 3: The
Catcher Must Propose, Not Just Question
It’s easy to poke holes in a goal. It’s harder — and more valuable —
to propose an alternative. The quality manager in our example didn’t
just say “that won’t work.” They said “here’s what I see in the data,
and here’s what I propose instead.” Constructive catchball requires that
every catch includes a counter-proposal.
Rule 4: Limit the Rounds
Catchball is not an infinite loop. Three to five rounds should be
enough to reach alignment. If you’re still going back and forth after
round five, the problem isn’t the communication method — it’s the goal
itself. Either it’s unclear, unrealistic, or unsupported. Name it and
escalate.
Rule 5: Document
the Agreement, Not the Process
The output of catchball is a shared understanding, not a transcript.
Record the final agreed goal, the key metrics, the resources committed,
and the timeline. Don’t document every throw and catch — that turns a
conversation into a bureaucracy. The value is in the dialogue, not the
paper trail.
Rule 6: Vertical and
Horizontal Catchball
Most organizations only play catchball vertically — up and down the
hierarchy. But the most critical catchball happens horizontally, between
departments that depend on each other. The quality team needs to play
catchball with engineering. Engineering needs to play it with
procurement. Procurement needs to play it with suppliers. Strategy
deployment that only moves vertically creates siloed alignment.
Horizontal catchball creates organizational coherence.
Rule 7: Catchball Never
Really Ends
The initial deployment is just the beginning. Throughout the year, as
conditions change and new information emerges, the catch continues.
Monthly reviews should include a catchball element — not just “are we
hitting the number?” but “does the number still mean what we agreed it
meant?” Strategy is not a static document. It’s a living
conversation.
What Catchball Looks
Like When It Fails
Let me tell you about a company I worked with — a Tier 1 automotive
supplier that will remain nameless. They had implemented Hoshin Kanri,
complete with X-matrices, bowling charts, and the whole apparatus. They
even had a catchball step in their deployment process.
But their catchball was broken, and they didn’t know it.
Here’s how it worked in practice: The VP would send his goals to the
plant managers via email. The plant managers would fill in their
“catchball response” form — a standardized template with boxes for
“understanding of goal,” “proposed actions,” and “resource
requirements.” They would email it back. The VP’s assistant would
compile the responses into a summary. The VP would review the summary
and approve it. Nobody ever had a conversation.
The form said “catchball.” The reality was paperwork.
When I interviewed the plant managers, here’s what I heard:
- “I filled in the form based on what I thought he wanted to
hear.” - “We never actually discussed it. I just checked the
boxes.” - “I have no idea if my interpretation matches anyone
else’s.” - “The form is due Friday. I’ll write something reasonable and
move on.”
This isn’t catchball. This is compliance theater dressed up in lean
terminology. The form doesn’t matter. The conversation does.
What Catchball Looks
Like When It Works
Contrast that with another organization — a medical device
manufacturer I worked with that treated catchball as a sacred
practice.
Their CEO set a strategic priority: “First-pass yield above 98% on
all Class III devices within 18 months.” That was the opening throw.
The first catchball round happened in a room, not an email. The VP of
Operations asked clarifying questions: “Which Class III devices? All
production lines or just the high-volume ones? What’s our current
baseline?” The CEO didn’t have all the answers — and said so. They
agreed to refine the scope together.
The second round included data. The VP came back with a Pareto
analysis showing that three product lines accounted for 80% of the yield
loss. The CEO adjusted the scope to focus on those three. The VP then
cascaded it to the three plant managers — in person, with the data, and
with the context of why this mattered (a key customer was threatening to
qualify a second source).
Each plant manager played catchball with their quality managers. Each
quality manager played it with their team leaders. By the time the goals
reached the production floor, every operator understood what they were
trying to achieve, why it mattered, and what specifically was changing
in their process to get there.
The result? They hit 98.3% first-pass yield in 14 months — four
months ahead of schedule. And when I visited the floor and asked
operators about the yield target, they didn’t just know the number. They
could explain which defect modes they were targeting, what
countermeasures were in place, and how their daily huddle board
connected to the CEO’s strategic priority.
That’s what catchball does when it’s done right.
The
Deeper Purpose: Building Organizational Intelligence
Here’s something most people miss about catchball: It’s not just a
deployment tool. It’s an organizational learning mechanism.
Every catchball round transfers two things. The first is obvious —
information about the goal, the metrics, the plan. But the second is
more subtle and more valuable: context. The CEO learns what’s actually
happening on the production floor. The operator learns why the customer
keeps complaining. The quality manager learns what the finance team is
worried about. Each round builds a richer, more accurate shared picture
of reality.
Over time, this does something remarkable. It builds organizational
intelligence — the ability of the organization as a whole to sense,
interpret, and respond to its environment more effectively than any
individual could alone.
Organizations that practice catchball well develop a quality of
communication that I can only describe as “aligned intuition.” People at
different levels start to anticipate each other’s concerns. They make
decisions that are consistent with the strategy even when they can’t
check with leadership first. They catch problems earlier because they
understand the broader context, not just their narrow function.
This is the real return on investment of catchball. Not better goal
deployment — though that happens too. But a smarter, more adaptable
organization.
Common Pitfalls and How
to Avoid Them
Pitfall 1: Skipping the dialogue. If your catchball
happens via email or form, it’s not catchball. It requires real-time,
face-to-face (or at least voice-to-voice) conversation. The nuance, the
questions, the pushback — these only emerge in dialogue. Schedule the
time. Protect it. Show up.
Pitfall 2: One-sided “catch.” If the thrower never
adjusts based on what comes back, the catcher learns quickly that their
input doesn’t matter. After two rounds of “thanks, but we’re going with
the original plan,” people stop engaging. And you’re back to top-down
deployment with extra steps.
Pitfall 3: Too many levels. Catchball works best
when there are no more than four to five organizational levels between
the strategy-setter and the strategy-executor. If your organization has
seven layers between the CEO and the shop floor, you need to flatten the
catchball process — perhaps by having skip-level sessions where the CEO
plays catch directly with the people who will execute.
Pitfall 4: Confusing catchball with negotiation.
Catchball is not a negotiation where each side tries to get the best
deal. It’s a collaborative refinement where both sides are working
toward the same outcome: a goal that is both strategically meaningful
and operationally achievable. If it feels like a negotiation, something
has gone wrong.
Pitfall 5: No follow-through. The catchball
conversation is the beginning, not the end. If you play catchball in
January and don’t revisit the agreements until December, the dialogue
has no consequence. Monthly reviews, visual management boards, and
regular check-ins are what give catchball its staying power.
Getting Started:
Your First Catchball Session
If you’ve never done catchball and want to start, here’s a simple
approach:
-
Pick one strategic priority. Not five. Not
three. One. The most important one. The one that keeps the CEO up at
night. -
Schedule a 90-minute session with your direct
reports. No slides. No handouts. Just the goal, a whiteboard, and a
conversation. -
Throw the ball. Explain the goal and the “why.”
Then stop talking. Listen to the questions. Write them down. Let the
group discuss what the goal means for their areas. -
Ask them to come back in one week with their
interpretation of the goal and a proposed plan. Not a PowerPoint. A
conversation. -
Play catch for three rounds. Adjust. Refine.
Agree. -
Have them repeat the process with their teams.
And have those teams repeat it with theirs. -
Review the agreements monthly. Not quarterly.
Monthly. The cadence of review determines the speed of
alignment.
You will be tempted to skip steps. You will be tempted to do it by
email. You will be tempted to combine it with other meetings and give it
twenty minutes. Resist all of these temptations. The power of catchball
is in the discipline of the practice.
The Paradox of Slowing
Down to Speed Up
Here’s the counterintuitive truth about catchball: It feels slow.
Having real conversations takes longer than sending emails. Multiple
rounds of dialogue take longer than a single sign-off meeting. Building
shared understanding takes longer than distributing a document.
But what feels slow at the beginning turns out to be fast in the end.
Organizations that practice catchball execute faster because they waste
less time on misalignment. They avoid rework because people understand
the intent, not just the instruction. They solve problems more quickly
because the context for decision-making is already shared.
The organization that spent three days in a room playing catchball
and then executed flawlessly for twelve months always beats the
organization that spent one hour deploying strategy and then spent
twelve months wondering why nothing happened.
Catchball is not the slow way to deploy strategy. It’s the fast way
to execute it.
A Final Thought
In a world of instant messaging, dashboards, and AI-generated
reports, the idea that the most powerful strategy deployment tool is a
simple conversation feels almost quaint. But that’s exactly why it
works.
Strategy doesn’t fail because we lack data. It fails because we lack
shared understanding. And shared understanding doesn’t come from a
spreadsheet. It comes from looking another human being in the eye,
throwing an idea at them, and being willing to catch what they throw
back.
Play catch. It works.
Peter Stasko is a Quality Architect with 25+ years
of experience transforming organizations across automotive, aerospace,
and pharmaceutical industries. He has deployed Hoshin Kanri and
catchball practices in organizations ranging from 50-person specialty
manufacturers to multinational Tier 1 suppliers, and he has seen
firsthand the difference between strategy that’s broadcast and strategy
that’s caught.
