The Kobetsu Kaizen Preparation Phase: Scope, Team, and Timeline

Setting the Scene: When Good Intentions Aren’t Enough

Picture this: a production line at a food packaging facility has been experiencing recurring micro-stoppages for weeks. The maintenance team has already replaced two motors, the shift supervisors have filed multiple reports, and everyone agrees something must be done. A meeting is called, people gather around the machine, ideas fly across the room — and two weeks later, the stoppages are still happening. The problem was not a lack of motivation or talent. The problem was a lack of structure. No one had clearly defined what the problem was, who was responsible for solving it, what success would look like, or by when results were expected. This is precisely the gap that the Kobetsu Kaizen Preparation Phase is designed to close.

What the Preparation Phase Is — and Why It Cannot Be Skipped

The Kobetsu Kaizen methodology is a structured, expert-team approach to solving middle- to large-sized chronic losses. Unlike simpler team-oriented Problem Solving Stories, Kobetsu Kaizen projects involve detailed analysis and mid- to long-term commitment. Because the methodology demands this level of rigor, the Preparation Phase is not a formality — it is the foundation on which everything else is built.

According to the Kobetsu Kaizen Workshop Standardization Process, the Preparation Phase requires three essential activities:

• Collecting information about the given problem — going to the Gemba, gathering data, and understanding the current condition before any analysis begins.
• Establishing goals and KPIs to measure workshop effectiveness and define what success looks like in measurable terms.
• Preparing the team of participants — selecting the right people, clarifying roles, and ensuring everyone understands the scope and expectations.

Each of these activities maps directly onto the first steps of the Kobetsu Kaizen Board: Problem Selection and Problem Representation. You cannot meaningfully represent a problem — or set targets — if the preparation work has not been done. In Lean terms, you would be working without a clear understanding of the current state, which violates one of the most fundamental principles of continuous improvement.

Scope, Team, and Timeline: The Three Pillars of Preparation

Defining the Scope

Scope definition answers the question: Which problem should we work on, and how far does our mandate extend? The Kobetsu Kaizen Board explicitly begins with Step 1 — Problem Selection — framing the question as “Which difficulty to focus on?” This is not as obvious as it sounds. In a manufacturing environment, chronic losses are everywhere. Without a disciplined selection process, teams risk choosing a problem that is too broad, too vague, or not aligned with strategic priorities.

Effective scope definition means:

• Linking the problem to one or more of the 16 machine and plant losses identified in the TPM framework (referenced directly in the Kobetsu Kaizen Board’s Step 1).
• Establishing boundaries — what is inside the scope of this project and what is not.
• Confirming that the problem is self-influenced, meaning the team has actual authority and capability to address it, consistent with the SMART target-setting criteria used in Kobetsu Kaizen (Specific, Measurable, Attractive, Realistic, Time-limited).
• Framing the problem in terms of OEE impact — Kobetsu Kaizen is specifically designed to drive OEE improvements by eliminating chronic losses that account for significant efficiency gaps.

The orientation toward zero — zero defects, zero accidents, zero errors — is a guiding principle that should inform scope definition from the very beginning. It prevents teams from accepting “good enough” as a target.

Building the Right Team

Kobetsu Kaizen is described as an expert-team project. This distinguishes it from broader, team-oriented Problem Solving Stories. The team is not assembled randomly or simply by availability. It must bring together the technical depth required for detailed root cause analysis.

A well-structured Kobetsu Kaizen team typically includes:

• A team leader — responsible for facilitating the process, maintaining the Kaizen Board, and driving progress against the timeline.
• Technical experts — engineers, maintenance specialists, or quality technicians with deep knowledge of the equipment or process in question.
• Operators from the Gemba — the people closest to the problem, whose firsthand experience is irreplaceable during problem representation and cause analysis.
• A sponsor or champion from plant management — to provide resources, remove obstacles, and ensure alignment with plant-level KPIs.

Roles must be explicit. Ambiguity about who owns what leads to duplicated effort or, worse, critical tasks falling through the gaps between the intensive and follow-up phases.

Establishing a Realistic Timeline

Time management is where many improvement projects quietly fail. The Kobetsu Kaizen Board references a 3-month horizon as a typical timeframe for the full structured problem-solving cycle. This is not arbitrary. It reflects the mid- to long-term nature of Kobetsu Kaizen projects, which require time for data collection, in-depth root cause analysis (including tools such as 5x Why, Pareto diagrams, and cause-effect analysis), countermeasure implementation, and result verification.

During the Preparation Phase, the team must create a working plan that allocates time across all eight steps of the Kaizen Board — from Problem Selection through Checking the Solution. Key milestones should be agreed upon and visible to all stakeholders. Transparency is not optional; it is built into the Kaizen Board itself, which is designed to be a living, visible management tool displayed in the work area.

Practical Example: Albanova Foods

Albanova Foods is a mid-sized pasta manufacturing company with three production lines. Line 2 has been experiencing a chronic packaging defect rate of approximately 4.5%, far above the target of 0.5%. The problem has persisted for over six months despite multiple quick fixes by the maintenance team.

The plant manager decides to launch a Kobetsu Kaizen project. During the Preparation Phase, the team conducts the following steps:

1. Scope definition: The problem is formally defined as “excessive packaging defects on Line 2 related to the sealing station.” Other potential causes upstream are noted but explicitly excluded from this project scope to maintain focus.
2. KPI establishment: The team defines a SMART target — reduce the defect rate from 4.5% to below 0.8% within 90 days, with OEE on Line 2 as the primary KPI. Weekly defect counts will be tracked using a tally chart, and a Pareto diagram will be built during the analysis phase.
3. Team formation: The team includes the Line 2 supervisor (team leader), two maintenance technicians, a quality engineer, and two experienced operators. The Operations Manager serves as sponsor.
4. Timeline: A 12-week plan is developed and posted on the Kaizen Board in the production area. Weeks 1–2 are allocated to problem representation and data collection at the Gemba. Weeks 3–5 cover root cause analysis. Weeks 6–9 are for countermeasure design and implementation. Weeks 10–12 are reserved for checking results and standardizing solutions.

With this structure in place, the intensive phase begins with clarity, ownership, and measurable expectations. The team is not starting from zero — they are starting from a well-prepared baseline.

Key Takeaways

• The Preparation Phase is structural, not optional. Skipping it leads to unfocused effort, team confusion, and failed improvement initiatives — regardless of technical skill.
• Scope must be precise and bounded. Link the problem