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

Imagine this: a recurring quality defect on an assembly line has been escalating for three weeks. The plant manager assigns a Kobetsu Kaizen (KK) activity to address it. A team is assembled — an engineer, two operators, a maintenance technician, and a quality specialist. The workshop kicks off, but within hours, confusion sets in. Who makes the final call on countermeasures? Who speaks during the debriefing? Who removes the organizational roadblocks that are slowing the team down? Without clearly defined roles, even the most technically capable team can stall — not because they lack answers, but because they lack structure. This lesson establishes the foundation: who does what in a KK activity, and why each role is indispensable.

The Three Core Roles in a Kobetsu Kaizen Activity

A well-functioning KK activity is not simply a meeting with tools. It is a structured problem-solving system where people, responsibilities, and interactions are deliberately designed to produce results. Three roles form the backbone of this system: the KK Leader (also referred to as the Team Leader or Problem Solving Team Leader), the Team Members, and the Sponsor (typically a line manager or department head who holds hierarchical authority). Understanding these roles — and how they interact — is as important as knowing any specific Lean tool.

The KK Leader: Facilitator, Driver, and Representative

The KK Leader is the operational engine of the activity. This person is responsible for making the workshop run — not by having all the answers, but by ensuring the right questions are asked, the right people are engaged, and the right process is followed. According to the Kaizen coaching framework, the KK Leader must be ready and prepared before the workshop begins, able to summarize findings on a single page, and capable of keeping the team focused on one problem at a time — avoiding the common trap of trying to solve everything at once.

The KK Leader’s responsibilities span the full PDCA cycle. Before the workshop, they ensure all participants have received their invitations and are briefed on the scope. During the grouping days — typically a two-day intensive session held 80% on the production floor — the Leader coordinates team actions in alignment with the Kaizen consultant or facilitator, manages the schedule, and represents the group during debriefings and presentations to management. After the workshop, they are accountable for ensuring that action plans are implemented. If the PDCA cycle stalls, the Leader must act to unblock the situation — not wait for someone else to intervene.

A critical behavioral expectation: the KK Leader does not accept the status quo. They push the team to find root causes rather than just applying quick repairs, and they check that the problem is genuinely understood before jumping into solutions. This requires both technical discipline and interpersonal skill — the ability to challenge assumptions without alienating team members.

Team Members: The Core of Problem-Solving Power

Team members are the people closest to the problem. In a KK workshop, the participant profile typically includes a facilitator, line team representatives, and direct production operators — a group of between six and ten people. This composition is intentional: operators bring direct observation and practical knowledge; engineers and technicians bring analytical depth; cross-functional members bring perspective from adjacent processes.

The “snowball effect” principle, central to the KK deployment model, relies on team members becoming multipliers. In the first workshop, eight people participate. In the second, three to eight of those same participants join the new team — carrying their experience forward. By the third workshop, a new cohort has been trained indirectly through participation. This cascade structure means that each team member is not just solving a problem — they are building organizational problem-solving capability.

Team members are expected to be autonomous contributors, not passive receivers of instruction. They observe, measure, hypothesize, test, and report. They are encouraged to share learnings visually — through A3s, action boards, or visual management tools — so that knowledge does not stay locked in one person’s head. The coaching matrix is clear: mistakes are accepted as part of the learning process. What is not accepted is silence, disengagement, or unchallenged assumptions.

The Sponsor: Enabler, Escalation Point, and Cultural Signal

The Sponsor — often a plant manager, production manager, or department head — plays a role that is easy to underestimate. They are not present on the floor for every step of the workshop, but their influence shapes everything. The Sponsor is the person who, when the KK Leader encounters an organizational obstacle they cannot resolve independently, steps in to unblock the path. This might mean reassigning resources, authorizing budget for a countermeasure, or resolving a conflict between departments.

Beyond problem-solving logistics, the Sponsor sends a cultural signal. When a senior leader visibly supports a KK activity — attending the debriefing, asking informed questions, celebrating the team’s progress — they communicate that problem solving is valued, not just tolerated. Conversely, a disengaged Sponsor who never appears and never follows up tells the organization that KK is just another compliance exercise. People involvement, as a Lean pillar, depends on this leadership behavior to be real and sustained.

The Sponsor is also responsible, in coordination with the KK Leader, for ensuring that development of problem-solving skills is distributed across the team — not concentrated in a few overloaded individuals. The goal is to build a department where multiple people can lead problem-solving activities, reducing dependency on any single expert.

Practical Case Study: Arvex Automotive Components

At Arvex Automotive Components, a mid-size manufacturer of interior trim parts, the production team faced a persistent issue: a 4.2% defect rate on a new injection molding line, causing internal rework and occasional customer complaints. The plant manager, Elena, designated herself as Sponsor and appointed Marco — a senior process engineer with two previous KK workshops under his belt — as KK Leader.

Marco assembled a team of eight: two machine operators, one quality technician, one maintenance specialist, one shift supervisor, and two participants from an adjacent line scheduled for their first KK in three weeks (applying the snowball principle). The two-day workshop was structured with a morning briefing in the meeting room and the bulk of activity directly on the production floor — measuring, observing, and testing.

On day one, the team hit a roadblock: the maintenance logs needed to verify a hypothesis about mold temperature fluctuation were stored in a legacy system that required IT access. Marco escalated to Elena, who contacted IT and resolved the access issue within two hours. Without this sponsor intervention, the team would have lost half a day. The debriefing on day two was attended by Elena, who publicly acknowledged the team’s root cause analysis and committed to the three-week implementation timeline for the validated countermeasures. Six weeks later, the defect rate had dropped to 0.8% — and two of the original team members were already co-leading the next KK activity.

Key Takeaways

• Three distinct roles — KK Leader, Team Members, and Sponsor — each carry specific responsibilities that must be understood and fulfilled for a KK activity to succeed.
• The KK Leader is the operational hub: preparing the workshop, coordinating during the activity, representing the team in debriefs, and driving PDCA completion after the event.
• Team members are both problem solvers and capability multipliers — the snowball effect depends on their active participation and their role as future facilitators of subsequent workshops.
• The Sponsor’s value is greatest at two moments: removing organizational obstacles during the workshop, and publicly validating the team’s work during the debriefing — both acts reinforce a problem-solving culture.
• Role clarity prevents the most common KK failure mode: not a lack of tools, but a lack of structure — when no one is sure who decides, who escalates, and who is accountable for implementation.