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

Opening: When the Meeting Room Becomes a Barrier

Picture this: a cross-functional team has gathered in a conference room to tackle a recurring quality defect on Line 3. The facilitator opens with a vague question — “So, what do you think the problem is?” — and within minutes, three supervisors are debating whose department is to blame, a technician is checking his phone, and the line operator who actually lives with the problem every day hasn’t said a word. Forty-five minutes later, the team agrees to “investigate further” and schedules another meeting. Sound familiar? Running a Kobetsu Kaizen (KK) session is not simply about gathering the right people in a room. It demands structured facilitation, purposeful dialogue, and a clear decision-making process — all grounded in the reality of the shop floor, not the comfort of the boardroom.

The Architecture of a KK Session: Structure Before Conversation

Effective KK sessions do not happen by accident. As confirmed by Kaizen Coach International’s operational model, a standard KK workshop runs over two days, involves a maximum of 6 to 10 participants, and — critically — takes place 80% on the production floor and only 20% in a meeting room. This ratio is not arbitrary. It forces the team to confront the problem where it actually exists, making assumptions harder to sustain and evidence easier to gather.

The composition of the team is equally deliberate. A well-structured KK session includes:

• The Facilitator — responsible for guiding the process, managing time, and ensuring psychological safety within the group
• Line Team and Line People — the operators and technicians who have direct knowledge of the problem
• A Facilitator or RTO (Resource Team Owner) from the next UGP (Unit of Production) — to initiate the “snowball effect,” where knowledge and methodology multiply across the plant

This snowball design is a strategic multiplier. In Workshop 1, eight people participate. In Workshop 2, three of those eight return as experienced contributors, transferring methodology to new participants. By Workshop 3, the same transfer repeats — spreading both problem-solving competence and Lean culture organically across the organisation.

Before the session begins, the facilitator carries several non-negotiable responsibilities: confirming that all participants have received their summons, coordinating with hierarchy if obstacles arise, and ensuring the PDCA cycle will actually turn — not just be discussed. As one KB source notes plainly, “If the PDCA cycle does not turn, he has to free the situation.” The facilitator is not a passive moderator. They are an active guardian of the process.

Facilitation Techniques and Structured Dialogue in Practice

Once the session is underway, the facilitator’s role shifts to one of structured guidance. The goal is to create the conditions for rigorous thinking — not to provide answers, but to ask the right questions at the right moment.

A core principle from the KB material is the discipline of one problem at a time. As the coaching matrix puts it: “How to eat an elephant? One problem at a time.” This seemingly simple idea is frequently violated in practice. Teams jump between symptoms, conflate root causes with solutions, and lose focus. The facilitator must continuously redirect: “Is this still about the same problem, or are we now talking about something different?”

Structured dialogue in a KK session typically follows a progression anchored in the 5W2H framework — asking What, Where, When, Who, Which, How, and How Much about the problem before any root cause analysis begins. This is a deliberate sequencing: check that the problem is well understood before jumping into root-cause analysis or corrective actions. Skipping this step is one of the most common facilitation failures and leads teams to solve the wrong problem with great efficiency.

For productive dialogue, the facilitator should apply the following techniques:

1. Go to the Gemba first. Walk the line with the team before any discussion. Let the physical reality anchor the conversation.
2. Use silence strategically. After posing a structured question, allow space for operators to respond before supervisors fill the gap.
3. Reflect and summarise frequently. Paraphrase what has been said to confirm shared understanding and expose hidden assumptions.
4. Separate observation from interpretation. “The seal is worn” is an observation. “Someone didn’t maintain it properly” is an interpretation — and a conversation-stopper.
5. Manage energy and status dynamics. In a mixed-level group, actively draw out quieter voices. The operator who runs the machine eight hours a day holds invaluable knowledge that hierarchy can inadvertently suppress.

Decision-making in a KK session should be consensus-based but time-bounded. The facilitator tracks the agreed actions in real time, assigns owners, and sets deadlines before the session closes. Debriefing at the end of each day reinforces accountability and provides visibility to wider stakeholders.

Practical Example: BakTech Manufacturing

BakTech Manufacturing, a mid-sized producer of baked snack products, was experiencing a recurring over-packaging defect on Line 7 — roughly 4% of packs were being sealed incorrectly, generating significant waste and customer complaints. The plant manager decided to run a KK session targeting this specific, small-to-medium-sized problem, consistent with the methodology’s recommendation to select issues of appropriate scope.

The facilitator assembled a team of eight: two line operators, a maintenance technician, a quality inspector, the line team leader, a process engineer, and — importantly — the RTO from Line 9, which was scheduled to begin its own KK cycle the following month. The session opened with 90 minutes on the production floor, observing the sealing station during a live production run. No solutions were discussed. Only observations were recorded.

Back in the meeting room (Day 1, afternoon), the facilitator used the 5W2H structure to define the problem with precision. This immediately revealed that the defect occurred predominantly during the first 20 minutes after a product changeover — a detail the operator knew but had never been asked to articulate. With the problem properly understood, the team moved into root-cause analysis using a cause-and-effect diagram, maintaining focus on the changeover context throughout.

By Day 2, three root causes had been confirmed through direct testing on the line: inconsistent jaw temperature at startup, an absent visual standard for seal pressure setting, and unclear operator instructions for the changeover sequence. Action owners were assigned before the session closed. The RTO from Line 9 left with both the methodology and the confidence to replicate the process — the snowball had begun to roll.

Key Takeaways

• Structure enables dialogue: A KK session’s effectiveness depends on deliberate preparation — right team composition, right location (80% on the floor), and a clear facilitation agenda anchored in PDCA.
• Understand before you solve: Use 5W2H and structured observation to fully define the problem before root-cause analysis begins. Jumping ahead wastes time and builds the wrong solutions.
• The facilitator is an active guardian: Their role is not passive moderation but active ownership of the process — managing time, protecting focus, and ensuring the PDCA cycle actually moves forward.
• One problem at a time: Maintaining disciplined scope is one of the most powerful — and most overlooked — facilitation techniques in any KK session.
• The snowball effect is by design: Including participants from the next KK cycle is not optional. It is the mechanism through which Lean culture and problem-solving capability multiply across the organisation.