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

Learning Objectives

• Translate a well-defined problem statement into a structured Kobetsu Kaizen kick-off sequence
• Identify the roles and responsibilities required to launch a Kaizen Board activity effectively
• Connect each step of the 8-step Kaizen Board framework to a concrete action at the start of a project
• Recognize the difference between Problem Solving Story and Kobetsu Kaizen Projects in terms of scope and approach
• Apply SMART criteria to transform an observed loss into a measurable improvement target

It is 6:45 on a Tuesday morning at a mid-sized automotive components plant. The line supervisor, Maria, has just finished the daily shift handover and is staring at the same recurring entry in the logbook for the third week in a row: “Machine C4 — unplanned stoppage, approx. 35 minutes.” The maintenance team has patched it, production has worked overtime to compensate, and yet the problem keeps coming back. Everyone knows something is wrong. Nobody has formally owned it. There is no structured analysis, no target, no timeline — just a growing frustration and a slowly worsening OEE figure. This moment, when a recurring loss is clearly visible but not yet framed, is exactly where Kobetsu Kaizen must begin.

Why the Problem Statement Is Not the Starting Line — It Is the Foundation

A common mistake in improvement initiatives is treating the problem statement as a formality — something to write down quickly before getting to the “real work” of fixing things. In Kobetsu Kaizen, the problem statement is the foundation. Without a precise, shared understanding of what the problem actually is, every subsequent step — from root cause analysis to countermeasure design — risks being misaligned.

The Kobetsu Kaizen Board structures problem solving into 8 steps, and the first two steps are entirely dedicated to framing: Step 1 – Problem Selection and Step 2 – Problem Representation (Concern). This is not accidental. The methodology recognizes that rushing to solutions before fully understanding the current situation is one of the most common causes of recurring problems in manufacturing environments.

Step 1 asks a deceptively simple question: Which difficulty should we focus on? In practice, this means prioritizing among the 16 major machine and plant losses to identify where chronic losses are concentrated. Tools such as Pareto diagrams and tally charts help the team speak with data rather than opinions. The output is not just a topic — it is a justified selection, visible on the Kaizen Board, that the entire team has committed to addressing.

Step 2 — the Concern step — requires the team to understand the current situation in depth. What exactly is happening? Where? When? How frequently? Who experiences the problem? This is where a 5W1H analysis (Who, What, Where, When, Why, How) becomes an essential discipline. It prevents the team from jumping to causes before the problem is fully visible. The result is a clear, data-supported description of the gap between the specified condition and the actual condition — the essential input for everything that follows.

From Theory to Action: Structuring the Kick-Off

Once the problem statement is solid, the Kaizen kick-off is not a spontaneous meeting — it is a structured transition from analysis to planned action. This transition covers Steps 3 through 5 of the Kaizen Board framework, and it is where the theoretical understanding of the problem begins to drive real decisions.

Step 3 – Setting Targets is where ambition meets discipline. Kobetsu Kaizen is oriented toward zero: zero defects, zero accidents, zero losses. Targets must be SMART — Specific, Measurable, Attractive, Realistic, and Time-limited. A vague target like “reduce machine stoppages” is insufficient. A SMART target sounds like: “Reduce unplanned stoppages on Machine C4 from an average of 3.5 per week to 0 within 3 months.” This clarity is what makes progress visible on the board and keeps the team accountable.

It is also important to distinguish at this stage between the two main approaches within Kobetsu Kaizen. For small to mid-sized problems requiring short-term resolution and simpler analysis, the Problem Solving Story approach is appropriate — team-oriented, structured, and relatively fast. For larger, more complex losses requiring detailed analysis and a mid- to long-term horizon, a full Kobetsu Kaizen Project with an expert team is the right structure. Choosing the wrong format wastes resources; choosing the right one accelerates results.

Steps 4 and 5 — identifying the problem cause and conducting root cause analysis — mark the transition from description to diagnosis. The Kaizen toolbox provides proven techniques: the 5x Why analysis to drill down through symptom layers, the fishbone (cause-and-effect) diagram to map contributing factors across categories, and Pareto diagrams to prioritize which causes account for the majority of the loss. The key discipline here is to resist the temptation to act on the first plausible cause. The team must validate the root cause with data before moving to countermeasures.

Practical Case Study: Veltran Manufacturing

Veltran Manufacturing produces precision-machined brackets at a plant in Central Europe. Over a 6-week period, their quality team observed a spike in surface defects on a CNC turning line, driving their OEE down from 78% to 69%. Scrap rates on the affected line doubled, and customer delivery performance began to show early warning signs.

The plant manager convened a Kobetsu Kaizen team of five people: the line team leader, a process engineer, a quality technician, a maintenance specialist, and an operator from the affected shift. Their first action was to populate the Kaizen Board — not with solutions, but with facts.

Using a tally chart and a Pareto diagram (Step 1), they confirmed that over 60% of all surface defects originated from a single machining station. This justified the problem selection. In Step 2, the team conducted a 5W1H analysis and discovered the defects appeared consistently during the first 90 minutes of the morning shift, predominantly on parts processed after a tool change.

With this clarity, they set a SMART target in Step 3: eliminate surface defects related to tool-change sequences within 10 weeks, reducing the defect rate on the station from 4.2% to under 0.5%. The problem scope matched a Problem Solving Story format — manageable, team-driven, and short-term.

In Steps 4 and 5, the team used a 5x Why analysis and traced the root cause not to the tools themselves, but to an inconsistent warm-up protocol after tool changes — a procedural gap that had never been standardized. This finding would have been invisible without disciplined problem framing at the start.

Countermeasures, validation, and standardization followed in Steps 6 through 8. Within 8 weeks, the defect rate had dropped to 0.3%. The team credited the structured kick-off — particularly the investment in Steps 1 through 3 — as the reason the solution held.

Key Takeaways

• The problem statement is the foundation, not a formality. Steps 1 and 2 of the Kaizen Board — Problem Selection and Problem Concern — must be completed with data and discipline before any analysis begins.
• SMART targets make improvement measurable and accountable. Kobetsu Kaizen targets are oriented toward zero losses, and must be time-limited and realistic to be effective on the board.
• Choosing the right format matters. Problem Solving Stories suit small to mid-sized, short-term problems; full Kobetsu Kaizen Projects are reserved for larger, more complex losses requiring expert teams and detailed analysis.
• Root cause analysis tools are only effective after the problem is fully framed. 5x Why, fishbone diagrams, and Pareto charts deliver reliable insights only when built on a solid, data-supported problem description.
• The Kaizen Board is a living management tool. It connects theory to action by making each step