The 4 Types of Problems in Kobetsu Kaizen: A Conceptual Framework

When Every Problem Looks the Same — Until It Isn’t

It’s 6:45 AM on the assembly floor. The shift supervisor at a mid-sized automotive parts plant gets three calls before the morning briefing even starts: a machine has just stopped unexpectedly, a recurring quality defect on Line 4 still hasn’t been resolved after three weeks, a team leader wants to push throughput beyond current benchmarks, and the plant manager is asking why the same type of breakdown keeps appearing across different cells every quarter. Four problems — but should they all be handled the same way? The answer, according to Kobetsu Kaizen methodology, is a clear no. Each of these situations belongs to a fundamentally different problem type, and misidentifying them is one of the most common reasons improvement efforts fail before they begin.

Why Problem Classification Matters in Kobetsu Kaizen

In Lean and Kobetsu Kaizen thinking, a problem is defined as the gap between the current condition and the expected or desired standard. But not all gaps are created equal. They differ in urgency, root cause complexity, the thinking style required to address them, and the depth of analysis needed. Treating a complex, multi-factor chronic loss with the same reactive approach you’d use for a sudden breakdown is not just inefficient — it’s a systematic way to waste resources and frustrate your teams.

Kobetsu Kaizen provides a conceptual framework that classifies problems into four distinct types. This framework acts as a diagnostic lens: before selecting your tools, forming your team, or launching an improvement project, you first need to correctly identify what kind of problem you are facing. The classification shapes everything that follows — the urgency of response, the depth of analysis, the tools applied, and the thinking modes engaged.

It is also worth noting that Kobetsu Kaizen itself sits within a broader improvement landscape. As the foundational materials make clear, Kobetsu Kaizen projects are expert-team driven efforts focused on middle to large-sized problems requiring detailed analysis over mid-to-long timeframes. This distinguishes them from simpler Problem Solving Stories, which handle small to medium problems with shorter timeframes and simpler analysis. Understanding problem types helps you make that first critical routing decision: does this belong in a quick problem-solving story, or does it demand a full Kobetsu Kaizen project?

The Four Types of Problems: A Practical Framework

Type 1 — Problems That Require Urgent Action

Type 1 problems are characterized by immediacy. Something has gone wrong, it is happening now, and it demands a rapid response to restore normal operations. The primary thinking mode here is reactive thinking — act first to contain the situation, then stabilize. These are the breakdowns, safety incidents, and sudden quality failures that trigger emergency stops and immediate escalation.

The goal at this stage is not root cause elimination — it is containment and restoration. However, a critical discipline in Lean is to treat Type 1 responses not as the end of the story but as the trigger for deeper investigation. If the same urgent problem recurs, it almost certainly belongs to a different type as well.

Type 2 — Problems Arising from Non-Compliance or Missing Standards

Type 2 problems emerge when a gap exists between an established standard and actual performance. This can happen in two ways: either a standard exists but is not being followed, or no standard exists at all, creating unpredictable variation. The thinking mode required is critical thinking — analyze the gap, identify where adherence has broken down, and either reinforce or create the appropriate standard.

These problems are extremely common on production floors. Operators following slightly different procedures, maintenance routines that have drifted over time, or inspection criteria that were never formally defined all fall into this category. The structured 8-step Kobetsu Kaizen approach, with its emphasis on understanding the current situation, analyzing problem fields, and setting targets against Quality, Cost, Delivery, Motivation, and Safety (QCDMS) dimensions, is well suited to addressing Type 2 problems systematically.

Type 3 — Problems Arising from the Need to Improve a Standard Performance

Type 3 problems are improvement-driven. Here, the standard is being met — but the standard itself is no longer good enough. The organization wants to raise the performance bar: reduce cycle time further, improve OEE beyond current levels, reduce defect rates below what the current process allows. This requires both critical thinking and creative thinking, because you are not fixing a deviation — you are redesigning what “good” looks like.

Type 3 work is at the heart of the OEE improvement projects and chronic loss elimination efforts that Kobetsu Kaizen was originally designed to address. Tools like Pareto diagrams, histograms, 5x Why analysis, and cause-and-effect diagrams come into full play here, as teams work to understand the limits of the current standard and engineer a better one.

Type 4 — Problems Arising from Multiple Factors Requiring a Systemic View

Type 4 problems are the most complex. They cannot be attributed to a single cause, a single department, or a single process. They emerge from the interaction of multiple variables across the system and require a systemic thinking approach combined with both critical and creative thinking. Chronic losses that persist despite multiple improvement efforts, performance patterns that vary unpredictably across shifts or cells, and cross-functional quality issues often fall into this category.

Addressing Type 4 problems demands a more comprehensive investigation scope, a cross-functional expert team, and analytical methods capable of capturing multi-factor interactions — including PM Analysis for equipment-related chronic issues. These are the problems most likely to evolve into full Kobetsu Kaizen projects with mid-to-long-term timelines.

Practical Example: Meccanica Nordest S.r.l.

Consider Meccanica Nordest S.r.l., a fictional precision machining company producing hydraulic components. Their production team identified four ongoing issues during a monthly review meeting:

• A CNC machining center stopped mid-cycle due to a coolant pressure fault — operations needed to resume within the hour. (Type 1: urgent action required)
• Finished part dimensions were drifting out of tolerance on one shift but not others, traced to operators using slightly different tool change intervals. (Type 2: standard not being followed consistently)
• Management set a new target to reduce scrap rate from 1.8% to 0.8% — better than the current process was designed to achieve. (Type 3: performance improvement beyond existing standard)
• Overall equipment effectiveness had been fluctuating unpredictably for six months despite several corrective actions, with no single root cause identified. Different machines, different operators, different material batches all seemed involved. (Type 4: multi-factor, systemic problem)

By correctly classifying each problem, the team was able to assign the right resources, apply the right tools, and set realistic timelines. The Type 1 issue was handled by the shift team immediately. The Type 2 issue was resolved through a standard reinforcement exercise within two weeks. The Type 3 and Type 4 issues were escalated into formal Kobetsu Kaizen projects with dedicated expert teams, detailed PDCA cycles, and structured root cause analysis using fishbone diagrams and 5x Why methodology.

Key Takeaways

• Correct problem classification is the foundation of effective improvement. Applying the wrong approach to the wrong problem type wastes time, resources, and credibility.
• The four types differ in urgency, complexity, and required thinking mode: Type 1 demands reactive thinking; Type 2 requires critical thinking; Type 3 combines critical and creative thinking; Type 4 demands a systemic approach across all thinking modes.
• Not every problem needs a full Kobetsu Kaizen project. The framework helps route problems appropriately — from quick problem-solving stories to long-term expert-team projects.
• Recurring Type 1 problems are often signals of Type 2, 3, or 4 issues underneath.