Lesson 1: Roles in a KK Activity: Leader, Team Member, and Sponsor — Responsibilities and Interactions

Opening: When Nobody Knows Who Is in Charge

Picture this: a recurring quality defect on a stamping line has been escalating for three weeks. A Kobetsu Kaizen workshop is launched, six people gather in the meeting room on Monday morning, tools are distributed, and the energy is high. By Tuesday afternoon, however, the group has produced three separate action lists with conflicting priorities, the plant manager has not been seen since the kickoff, and the line supervisor is fielding production calls instead of driving the analysis. The root cause remains unidentified. The problem? It was not the methodology that failed — it was the absence of clearly defined roles. In a KK activity, knowing who does what, when, and with whom is just as critical as knowing which problem-solving tool to apply.

The Three Pillars: Leader, Team Member, and Sponsor

Every effective Kobetsu Kaizen activity rests on three distinct roles. Each one carries specific responsibilities, and each one interacts with the others in ways that either accelerate or derail the workshop. Understanding these roles — and living them — is what separates a productive KK event from a frustrating meeting marathon.

The KK Activity Leader (Problem-Solving Team Leader)

The Activity Leader is the engine of the KK workshop. This person is typically an experienced facilitator, a line team leader, or a Kaizen Coach who has both the technical grounding to guide structured problem solving and the interpersonal skills to manage group dynamics under pressure. The Leader is accountable for the entire process — from preparation through follow-up.

Before the workshop begins, the Leader ensures that all participants have received their summons, that the problem statement is clear and scoped appropriately, and that the workspace — primarily on the production floor — is ready. As the knowledge base reminds us, KK workshops happen 80% in production and 20% in the meeting room. The Leader must therefore be comfortable operating in both environments and moving the team between them fluidly.

During the workshop, the Leader:

• Moderates discussions and keeps the team focused on one problem at a time — resisting the temptation to “trawl” for every adjacent issue on the shop floor
• Coordinates actions according to the structured problem-solving methodology (applying the PDCA cycle rigorously)
• Represents the group during debriefing sessions and presentations to management
• Ensures that action plans are built, assigned, and moving — and if the PDCA cycle stalls, the Leader is responsible for unblocking the situation
• Is prepared with a one-page summary of findings and actions, ready to communicate progress clearly and concisely

Critically, the Leader must accept that mistakes will happen and signal to the team that this is an expected part of learning. Psychological safety is not a soft extra — it is a precondition for honest root-cause analysis. A Leader who punishes errors will receive filtered information, which guarantees that real root causes stay hidden.

The Team Members

A KK workshop typically involves a maximum of six to ten participants, combining facilitators, line team members, and direct production operators. This diversity is intentional: the people closest to the problem bring observational knowledge that no report or dashboard can replicate. Team members are not passive attendees. They are active contributors to every phase of the analysis.

Effective team members in a KK activity:

• Bring direct, first-hand knowledge of the process, machine, or quality issue under examination
• Commit to honest observation and data sharing — not defending the current state, but understanding it
• Participate in the snowball effect by carrying what they learn into future workshops, acting as multipliers of problem-solving capability across the plant
• Challenge assumptions constructively and check that the problem is truly understood before jumping into root-cause analysis or solution generation
• Remain present and engaged throughout the workshop rather than retreating to routine operational tasks

The snowball effect described in the knowledge base is worth highlighting: when three or four members of the first workshop participate in the second, and the same pattern repeats into the third, the plant organically builds a growing network of people with shared problem-solving language and experience. This is how KK scales from a one-off event into a cultural capability.

The Sponsor

The Sponsor — typically a plant manager, department head, or senior operations leader — plays a role that is easy to underestimate and catastrophic to neglect. The Sponsor does not facilitate the workshop. Their role is to enable and protect it.

In practice, this means:

• Releasing the right people to participate for the full duration of the workshop without pulling them back to cover operational gaps
• Resolving escalations that the Leader cannot handle alone — particularly those involving cross-functional resources, budget, or hierarchical decisions
• Attending the debriefing and acting visibly on the recommendations, signaling to the entire organization that KK results matter
• Modeling result orientation by refusing to accept “just repair” as an outcome — insisting on eradication of root causes, not patching of symptoms
• Developing problem-solving skills within their broader team over time, so that the demand on a small group of expert Leaders does not become a bottleneck

When Sponsors are absent or disengaged, action plans accumulate without implementation, and teams quickly learn that KK workshops are theater rather than transformation.

Practical Case Study: Mertens Automotive Components

Mertens Automotive Components, a mid-sized supplier of pressed metal brackets, launched a Kobetsu Kaizen activity targeting a recurring dimensional non-conformity on a progressive die line. The workshop ran for two days with eight participants: one external KK facilitator (acting as Leader), two process engineers, three press operators, one quality technician, and one maintenance specialist.

Before day one, the Leader confirmed attendance, prepared the problem definition card, and arranged floor access. The plant operations director served as Sponsor, attending the morning kickoff and the final debriefing on day two.

On the floor, operators identified a micro-vibration pattern linked to a worn guide column — something that had never appeared in maintenance records because it was only detectable during a specific production sequence. The engineers had been analyzing the wrong variable for weeks. The Leader kept the team focused on this single mechanism, resisting pressure to address three other “while we’re here” issues flagged by the maintenance specialist.

At the debrief, the Sponsor immediately approved the guide column replacement budget and committed to a 48-hour resolution window. Three team members from that first workshop were assigned to the next KK event on a different line — the snowball had started rolling.

Key Takeaways

• Three roles, three accountabilities: The Leader facilitates and drives the process; Team Members contribute knowledge and become multipliers; the Sponsor enables, protects, and acts on results. All three must be present and engaged.
• The Leader’s job is moderation and momentum: Keeping the team focused on one problem at a time, managing the PDCA cycle, and communicating outcomes clearly are the Leader’s core deliverables — not just technical expertise.
• Team composition creates the snowball effect: Including people who will participate in future workshops is a strategic choice, not a scheduling convenience. It is how KK capability spreads organically through the plant.
• Sponsors who show up change outcomes: Visible commitment at kickoff and debriefing, combined with fast resource decisions, is the signal that turns workshop output into real operational change.
• Psychological safety is a functional requirement: Teams that fear blame will not surface real root causes. The Leader must explicitly normalize mistakes as part of the learning process to get honest data from the floor.