From Problem Statement to Kaizen Kick-Off: Connecting Theory to Action

Learning Objectives

By the end of this lesson, you will be able to:

• Translate a well-defined problem statement into a structured Kobetsu Kaizen kick-off sequence
• Identify the correct entry point on the Kaizen Board based on the nature and severity of a problem
• Connect the 8-step KAIZEN® Board framework to real preparation activities performed before a project begins
• Distinguish between Problem Solving Story (team-oriented, short-term) and full Kobetsu KAIZEN® projects (expert-team, mid-to-long-term)
• Apply SMART goal-setting principles to move from a problem description to a measurable improvement target

It is 6:45 AM on a Monday. The production floor of a mid-sized automotive components plant is already running at full speed — or rather, it should be. Line 4 has been losing roughly 12% of its planned output every week for the past two months. Operators call it “the usual stops.” Maintenance logs it as “intermittent fault.” The shift supervisor shrugs and says, “We always recover by end of shift.” Yet the numbers tell a different story: OEE is slipping, delivery commitments are at risk, and no one has formally owned the problem. The issue is not that people are unaware — it is that the problem has never been properly framed, assigned, or kicked off as a structured improvement initiative. That is exactly the gap this lesson addresses.

Why the Kick-Off Moment Matters

In Lean practice, the distance between noticing a problem and acting on it in a structured way is where chronic losses live. Kobetsu KAIZEN® — literally “focused continuous improvement” — exists precisely to close this gap. It provides a disciplined pathway from problem identification all the way to verified countermeasures, governed by the PDCA cycle (Plan, Do, Check, Act).

The kick-off is the hinge point. Before it, you have observations, complaints, and intuitions. After it, you have a team, a target, a timeline, and a visual management tool — the KAIZEN® Board — that makes the entire problem-solving story visible to everyone on the floor.

The KAIZEN® Board structures the journey into 8 clear steps:

1. Problem Selection — Which difficulty should we focus on?
2. Problem Representation (Concern) — Understand the current situation
3. Set Targets — Define SMART goals oriented toward zero losses
4. Root Cause to the Problem — Analyse the problem field
5. Analysis of Causes — Use quality tools (5×Why, Pareto, fishbone, histograms)
6. Countermeasures — Generate, evaluate, and plan solutions (5W1H)
7. Check the Solution — Compare original and present condition; did it work?
8. Standardisation and Follow-Up — Lock in gains and prevent recurrence

The kick-off formally activates Steps 1 through 3. Everything before that moment — selecting the right problem, scoping it correctly, and setting a measurable target — is what this lesson focuses on.

Connecting the Problem Statement to the Board: A Step-by-Step Bridge

A strong problem statement is not just a complaint written down. It is a factual description that answers: What is happening? Where? How often? Who experiences it? What is the impact on Quality, Cost, Delivery, Motivation, or Safety (QCDMS)? When you can answer all five of those questions with data, you are ready to open the Kaizen Board.

Step 1 — Problem Selection: Choosing the Right Focus

Not every problem deserves a Kobetsu KAIZEN® project. The methodology distinguishes clearly between two levels of intervention:

• Problem Solving Story: Team-oriented, suitable for small to mid-sized problems, short to mid-term horizon, simple analysis. This is the right vehicle for most front-line issues.
• Kobetsu KAIZEN® Project: Expert-team driven, for mid-to-large problems requiring detailed analysis over a longer period — typically connected to significant OEE losses or chronic machine/equipment failures.

During kick-off, the team and the responsible leader must make this classification explicit. The 16 machine and plant losses framework — covering speed losses, breakdowns, defects, minor stops, and more — provides a structured catalogue to anchor the selection. Speaking with data, not assumptions, is non-negotiable at this stage.

Step 2 — Problem Representation: Making the Current Condition Visible

Once the problem is selected, the team must describe the actual condition in measurable terms. This means going to the Gemba — where the work is done, where value is created — and collecting direct evidence. Tools like tally charts, frequency tables, flow diagrams, and Pareto diagrams help visualise where the emphasis lies and what the biggest contributor is. The Kaizen Board at this stage should show factual data, not opinions.

A useful discipline here is the N5W (Who, What, Where, When, Why — times five) combined with 5W1H (What, Who, Where, When, Why, How) to frame the concern completely before moving forward.

Step 3 — Set Targets: SMART and Oriented Toward Zero

Kobetsu KAIZEN® targets are intentionally ambitious. The orientation is toward zero — zero defects, zero accidents, zero unplanned stops — because this mindset prevents the team from anchoring to historically poor performance. However, targets must also be SMART:

• Self-influenced — the team must be able to act on it
• Measurable — expressed in numbers, not feelings
• Attractive — motivating and meaningful to the team
• Realistic — achievable within the given constraints
• Time-limited — with a clear deadline, typically within a 3-month horizon

This is the moment where the problem statement officially becomes an improvement commitment. The target is written visibly on the board, signed off by the team leader, and becomes the reference point for every subsequent step.

Practical Case Study: Precision Parts GmbH, Line 4

Precision Parts GmbH is a fictional mid-tier supplier producing machined components for the commercial vehicle sector. Their Line 4 produces steering column brackets and has been experiencing a recurring minor stop pattern — short interruptions of 1 to 3 minutes that individually seem insignificant but collectively account for a 12% OEE loss over eight weeks.

The plant manager, together with the team leader and a process engineer, decides to open a Kobetsu KAIZEN® project. Here is how the kick-off unfolds:

1. Problem Selection: Data from the OEE tracking system confirms that Line 4 accounts for 43% of all minor stops on the floor (Pareto analysis). The team classifies this as a Kobetsu KAIZEN® project given its impact and required analysis depth.
2. Problem Representation: A tally chart collected over five days reveals that 68% of minor stops occur at the loading station between 10:00 AM and 1:00 PM. A flow diagram of the process highlights a manual re-positioning step as a recurring interruption point. The concern is documented with photos and data on the board.
3. Set Targets: The team sets a SMART target: “Reduce minor stops on Line 4 loading