Lesson 2: Running a KK Session: Facilitation Techniques, Structured Dialogue, and Decision Making

Opening: When the Clock Is Ticking and the Team Is Stuck

It is 8:15 on a Tuesday morning. The production line has been losing approximately 12% of its available run time over the past three weeks due to a recurring changeover issue. A Kobetsu Kaizen workshop has been scheduled — six people are sitting around a table, coffee in hand, waiting for someone to lead them somewhere useful. The facilitator walks in, opens a blank flipchart, and writes one sentence at the top: “What do we actually know about this problem?” What happens in the next two days will determine whether this team leaves with a real solution or simply a list of good intentions. The difference lies entirely in how the session is facilitated.

Learning Objectives

• Apply structured facilitation techniques to keep a KK session productive and on track
• Use structured dialogue methods to surface root causes without allowing the conversation to drift
• Guide a cross-functional team through a decision-making process that leads to prioritized, implementable actions
• Manage group dynamics, conflict, and participation imbalances during a KK workshop
• Understand the practical logistics and rhythm of a two-day KK session, including the 80/20 room-to-floor split

Setting the Stage: Structure, Roles, and the Rhythm of a KK Session

A Kobetsu Kaizen workshop is not a brainstorming meeting. It is a structured, time-boxed problem-solving event built around a specific, well-scoped problem — typically a small to medium-sized operational issue where focused analysis can resolve 80% of the loss. According to the KCI OpEx model, the ideal format spans two days, involves a group of six to ten participants, and critically, takes place 80% on the production floor and only 20% in a meeting room. This ratio is not arbitrary. It reflects a core Lean principle: go to where the problem lives. Data collected from the gemba is always more reliable than assumptions made from a conference room.

The composition of the team matters just as much as the location. A well-structured KK team typically includes the facilitator (the Kaizen Coach or trained internal leader), line team members (technicians, operators, maintenance), and — importantly — a representative from the next UGP (Unit of Production) that will begin its own KK cycle. This deliberate overlap creates what the KCI model calls the snowball effect: participants from one workshop become partial facilitators of the next, exponentially spreading knowledge and capability across the plant. For example, if Workshop 1 has eight participants, Workshop 2 might include three of those original eight plus five new participants. Workshop 3 draws from Workshop 2 in the same way — building an ever-expanding network of problem solvers.

Before the first day begins, the facilitator must confirm that all participants have received their summons, that logistics are in place, and that a clear problem statement — not a solution hypothesis — has been defined. If the problem is not yet well understood, the facilitator’s first job is to slow the team down. As the M&B performance coaching matrix explicitly warns: check if the problem is well understood before jumping into root-cause analysis or actions. Rushing past problem definition is one of the most common and costly mistakes in structured problem solving.

Facilitation Techniques: Guiding Without Dominating

The facilitator’s role in a KK session is not to be the smartest person in the room — it is to create the conditions in which the team can think clearly together. This requires a specific set of facilitation skills that go beyond technical Lean knowledge.

1. Structured dialogue over open discussion. Open-ended conversations tend to circle back, drift into blame, or get captured by the most vocal person. The facilitator should use structured tools such as the 5 Whys, fishbone (Ishikawa) diagrams, and 5W2H to give dialogue a visible skeleton. When the team can see their thinking mapped on a wall or whiteboard, it becomes easier to identify gaps, contradictions, and unexplored branches. The 5W2H framework — Who, What, Where, When, Why, How, How much — is particularly effective in the early stages of a KK session to ensure the problem is described with sufficient precision before analysis begins.

2. Managing participation imbalance. In any group of six to ten people, some voices will dominate and others will withdraw. The facilitator must actively manage this dynamic. Techniques include directing specific questions to quieter participants, using round-robin contributions during key steps, and using silent idea generation (individual sticky notes before group discussion) to prevent group think. The Kaizen Coach model emphasizes teamwork and moderation as inseparable skills — a good facilitator is also a skilled moderator who reads the room continuously.

3. Keeping focus on one problem at a time. The M&B coaching matrix captures this with a memorable phrase: “one problem at a time — how do you eat an elephant?” During a KK session, the team will inevitably surface adjacent issues, systemic complaints, or tangential concerns. The facilitator must acknowledge these without letting the session be pulled off course. A “parking lot” — a visible list of issues noted but set aside for later — is a simple and effective tool for doing this respectfully.

4. Respecting the PDCA rhythm. The KK session itself follows the Plan-Do-Check-Act cycle. The facilitator is responsible for ensuring this cycle actually turns. As the 5S workshop documentation notes, if the PDCA cycle is not moving, the facilitator must identify and remove the obstacle — whether it is a missing resource, an unresolved decision, or a hierarchical blocker. When escalation is needed, the facilitator contacts the appropriate level in the hierarchy or the Kaizen coordinator, not the group. This keeps the team focused and protected from organizational friction.

Decision Making: From Analysis to Prioritized Action

The closing phase of a KK session is where facilitation skill is most visibly tested. After root causes have been identified, the team must agree on countermeasures, assign owners, set deadlines, and commit to verification. Several failure modes are common here: action lists that are too long to be realistic, actions assigned to absent individuals, or countermeasures that treat symptoms rather than root causes.

An effective facilitator guides the team through a prioritization matrix — evaluating potential actions by their impact on the problem and the effort required to implement them. High-impact, low-effort actions become immediate priorities. The team should leave with a compact action plan — typically no more than five to eight items — with a named owner and a specific completion date for each. Vague commitments like “we will look into it” are not acceptable outputs of a KK session.

During debriefings, the facilitator (or the designated group representative, as outlined in the KCI workshop model) presents the findings and action plan to the broader organization. This is not a formality — it is a critical accountability mechanism and a visibility tool that sustains momentum after the workshop ends.

Practical Case Study: Reducing Micro-Stops at Brennan Confectionery

At Brennan Confectionery, a mid-sized food manufacturer, the wrapping line in Hall C was experiencing persistent micro-stops averaging 18 per shift, each lasting 30 to 90 seconds. A two-day KK workshop was convened with eight participants: the KK facilitator, two line operators, a maintenance technician, the line team leader, a quality technician, and — applying the snowball model — a facilitator and RTO from the adjacent Hall B line scheduled to begin its own KK cycle the following month.

Day one was spent 80% on the floor. The team conducted direct observation, filmed micro-stops, and used 5W2H to build a precise problem description. By end of day one, three distinct root cause clusters had been identified using a fishbone diagram: inconsistent film tension, worn guide rollers replaced outside the PM schedule, and operator adjustment habits that varied by shift.

On day two, the team used a prioritization matrix to agree on six countermeasures. The two Hall B observers, who had said little on