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

It’s Monday morning at a manufacturing plant, and a recurring quality defect has just caused the third line stoppage this week. The production manager calls for a Kobetsu Kaizen (KK) activity to tackle the root cause once and for all. Within hours, a small team is assembled — but without clearly defined roles, the workshop quickly turns into a disorganized debate. The facilitator loses control of the discussion, team members wait for someone else to take ownership, and the sponsor is nowhere to be found when a critical resource decision needs to be made. Sound familiar? This scenario plays out more often than it should, and the root cause is almost never the problem itself — it’s the lack of role clarity within the KK activity.

Why Roles Matter in Kobetsu Kaizen

A Kobetsu Kaizen activity is not simply a meeting or a brainstorming session. It is a structured, time-boxed problem-solving workshop — typically two days in duration — involving a focused team of 6 to 10 people, spending roughly 80% of their time on the production floor and 20% in a meeting room. Within this compact and intensive format, every participant must know exactly what is expected of them before the workshop begins, during its execution, and after the action plans have been defined.

People involvement is one of the foundational pillars of any Lean system. Kaizen is not something done to people — it is done with people, and done effectively only when motivation, teamwork, and clear accountability are aligned. When roles are ambiguous, even the best problem-solving tools lose their power. The three core roles in a KK activity — the KK Leader, the Team Members, and the Sponsor — each carry distinct responsibilities that, when properly understood and executed, create the conditions for sustainable improvement.

The Three Core Roles: Responsibilities and Interactions

The KK Leader (Kaizen Coach / Facilitator)

The KK Leader is the engine of the workshop. This person is responsible for the technical facilitation of the problem-solving process, team moderation, and ensuring that the PDCA cycle actually turns — not just during the workshop, but in the weeks that follow. The Leader is not necessarily the most senior person in the room; they are the most prepared.

Key responsibilities of the KK Leader include:

• Ensuring all participants have received proper summons and briefing before the workshop begins
• Coordinating actions in alignment with the Lean/OpEx methodology and the guidance of any supporting consultant or coordinator
• Respecting and enforcing the workshop schedule and agenda
• Representing the group during debriefing sessions and final presentations to management
• Following up on action plan implementation after the three grouping days, and escalating blockers to the sponsor when the PDCA cycle stalls
• Being thoroughly prepared before the workshop — having reviewed available data, pre-mapped the problem, and prepared a clear one-page summary framework

The KK Leader must resist two common failure modes: becoming the person who solves everything alone (thereby disempowering the team), and becoming so focused on the process that they lose sight of the actual problem. As one coaching matrix used in industrial practice puts it, the Leader must stay focused on the problem — “ne pas faire le chalutier” (don’t trawl the sea looking for everything) — and ensure the problem is well understood before jumping into root-cause analysis or countermeasures.

Team Members

Team members are the people closest to the process — line operators, technicians, quality engineers, and maintenance staff. Their value in a KK activity is irreplaceable: they carry the tacit knowledge that no data report can fully capture. The snowball effect built into the KK workshop design (where participants from one workshop seed the next) is only possible when team members are genuinely engaged, not passive attendees.

Effective team members in a KK activity are expected to:

• Actively contribute observations, ideas, and operational knowledge during root-cause analysis
• Participate in on-floor observation and data collection — spending the majority of workshop time at the gemba
• Take ownership of specific action items assigned during the workshop
• Remain open to questioning current practices without defaulting to “that’s how we’ve always done it”
• Accept that mistakes and hypotheses that don’t pan out are part of the process, not failures

It is the KK Leader’s responsibility to create the psychological safety for team members to speak up. But it is the team members’ responsibility to show up prepared, present, and engaged — not as passive recipients of instructions.

The Sponsor

The Sponsor is typically a plant manager, department head, or senior operations leader. Their role is often misunderstood: many sponsors believe their job is simply to “kick off” the workshop and then disappear. In reality, the Sponsor plays a critical enabling role throughout the entire KK activity lifecycle.

The Sponsor’s core responsibilities include:

• Selecting and clearly scoping the problem — ensuring it is a small-to-medium-sized problem appropriate for KK methodology, not a systemic strategic challenge
• Allocating the right people and resources to the team, including protecting participants’ time during the workshop
• Removing organizational obstacles that the KK Leader cannot resolve independently
• Being present at key milestones — particularly debriefing sessions — to signal that this activity has real organizational priority
• Supporting the implementation of action plans post-workshop by holding the team accountable through standard routines

The Sponsor must not micromanage the workshop, but they cannot be absent either. Their presence signals commitment; their absence signals that the activity is optional — and that perception spreads fast on the shop floor.

Practical Example: AeroParts Manufacturing

At AeroParts Manufacturing, a mid-sized supplier of precision components, the maintenance team had been dealing with a recurring hydraulic press failure for several months. Repair times were inconsistent, and the issue kept reappearing every three to four weeks. A two-day KK activity was launched.

The KK Leader — an experienced process engineer named Marco — spent two hours the evening before the workshop reviewing maintenance logs, preparing a structured problem statement, and organizing a one-page brief for the team. During the workshop, he kept the team on track, prevented discussions from spiraling into unrelated topics, and facilitated a root-cause analysis that led the team to identify a lubrication interval mismatch as the primary driver. He also scheduled a debriefing presentation for the plant manager on day two.

The team members — two line operators, a maintenance technician, and a quality engineer — contributed observations that the data alone hadn’t revealed: the press was operated differently during night shifts, which accelerated wear. This insight, invisible in any report, became the cornerstone of the corrective action plan.

The Sponsor, Plant Director Sofia, attended the closing debrief, approved immediate changes to the maintenance schedule on the spot, and committed to a monthly review of the action plan status in her operational routine. Three months later, the failure had not recurred.

The difference was not the tool. It was the clarity of roles.

Key Takeaways

• Role clarity is a prerequisite, not a luxury: In a KK activity, ambiguous responsibilities lead directly to poor outcomes — regardless of which problem-solving tools are used.
• The KK Leader is a facilitator and coach, not a solo problem solver: Their job is to make the team effective, ensure PDCA turns, and represent the group — not to provide all the answers.
• Team members are the knowledge source: Their proximity to the process is the most valuable asset in any KK workshop; their engagement must be actively cultivated.
• The Sponsor enables, protects, and sustains: A sponsor who is present at key moments and removes blockers is the difference between a workshop that