Type 1 vs. Type 2 Problems: Restoring the Standard vs. Raising It

When the Line Goes Down: Two Very Different Problems

It is Monday morning, 6:47 AM. The assembly line at your facility has just stopped. The shift supervisor is on the radio, quality is flagging a batch of non-conforming parts, and the maintenance team is already running toward the affected station. Meanwhile, in the conference room one floor up, the operations manager is reviewing last quarter’s OEE data and asking a very different question: “We are running at 72% efficiency — our competitors are at 85%. What do we need to do to close that gap?” Both situations involve problems. Both demand attention. But they are fundamentally different in nature, and treating them the same way is one of the most common — and costly — mistakes in continuous improvement work. Understanding the distinction between Type 1 and Type 2 problems is not a theoretical exercise. It is the foundation of effective problem-solving within the Kobetsu Kaizen framework.

The Four-Type Model: Where Type 1 and Type 2 Fit

The Kobetsu Kaizen methodology recognizes four distinct types of problems, each requiring a different thinking mode and a different structured approach. Before diving into Type 1 and Type 2 specifically, it helps to understand the full landscape:

• Type 1: Problems that require urgent actions — reactive in nature.
• Type 2: Problems that arise from the non-respect of standards or from the lack of standards — critical in nature.
• Type 3: Problems that arise from the need to improve a standard performance or situation, ultimately requiring a new standard — creative and critical in nature.
• Type 4: Problems that arise from multiple interacting factors and need a systemic view and approach — systemic in nature.

This lesson focuses on the critical distinction between Type 1 and Type 2 — the two most frequently encountered categories on the shop floor, and the two most often confused with each other. Getting this classification right before acting is the first discipline of structured problem-solving.

Type 1: Restoring the Standard — Reactive and Urgent

A Type 1 problem is characterized by urgency. Something was working correctly, according to a known standard, and now it is not. The gap between the expected condition and the current condition is visible, immediate, and demands a fast response. The primary thinking mode here is reactive thinking — the goal is to stop the bleeding and return operations to the previously established baseline as quickly as possible.

In Lean terms, a Type 1 problem represents a deviation from a defined standard. The standard already exists. The target is already known. Your task is not to invent a new way of doing things — it is to identify why the current condition has fallen below the standard and restore it. Common examples include:

• An unexpected machine breakdown that halts production
• A sudden spike in defect rates after a previously stable process
• A safety incident or near-miss that disrupts normal operations
• A supplier delivering out-of-specification material that affects the line

The critical discipline for Type 1 is speed combined with rigor. While the immediate priority is containment — protecting the customer and the process — the structured response must also include a root cause investigation to prevent recurrence. Tools such as the 5-Why analysis, rapid problem-solving stories, and the 8-step Kaizen Board structure are well-suited here. The question driving Type 1 is always: “Why did we fall below the standard, and how do we get back there — permanently?”

Type 2: Raising the Standard — Analytical and Deliberate

A Type 2 problem has a fundamentally different character. There is no emergency, no alarm sounding, no line down. In fact, on the surface, things may appear to be running normally. The problem is that “normal” is not good enough — either because a standard is not being consistently respected, or because no adequate standard exists at all. The gap here is not between yesterday’s performance and today’s. It is between the current level of performance and a better, achievable level.

The thinking mode for Type 2 is critical thinking — methodical, evidence-based, and analytical. This type of problem often emerges from data review, audit findings, benchmarking, or structured observation. It is the domain of Kobetsu Kaizen projects where teams dig into chronic losses, variability in cycle times, or recurring quality issues that never quite break the threshold for a full emergency but continuously erode performance over time.

Consider the OEE improvement journey described in the Kobetsu Kaizen framework: chronic losses — those persistent, low-level inefficiencies — are precisely the territory of Type 2 thinking. The Kobetsu Kaizen methodology distinguishes between Problem Solving Stories (typically team-oriented, addressing small to mid-sized problems over a shorter timeframe) and Kobetsu Kaizen Projects (expert-team driven, tackling larger, more complex problems requiring detailed analysis over a mid-to-long term). Both, however, share the Type 2 orientation: raising performance to a new standard.

Key questions driving Type 2 work include:

• Where does a standard not exist, and what should it be?
• Where is a standard poorly defined, inconsistently applied, or not understood by operators?
• What does data tell us about the gap between our current performance and our target performance?
• What new standard should we set, and how do we lock it in through training, visual management, and process control?

Practical Case Study: Ferro Meccanica S.p.A.

Ferro Meccanica S.p.A. is a mid-sized automotive components manufacturer with three production lines running two shifts. During a monthly performance review, the continuous improvement team noticed two distinct issues.

Issue A: Line 2 had experienced four unplanned stoppages in the past week, each lasting between 20 and 45 minutes. Operators reported unusual vibrations before each stoppage. This is a Type 1 problem. The line had previously run without stoppages; a known standard existed and was not being met. The team immediately applied containment actions, escalated to maintenance, and launched a 5-Why analysis. Within 48 hours, they identified a worn bearing assembly that had not been flagged in the preventive maintenance schedule — and they updated the PM checklist accordingly to prevent recurrence.

Issue B: A review of Line 1’s changeover data over the past six months revealed that average changeover time was 94 minutes — well above the 60-minute target set during the last production planning cycle. There was no single crisis, no alarm. But the gap was real, consistent, and costing the plant approximately 12 hours of productive capacity per month. This is a Type 2 problem. The team launched a structured Kobetsu Kaizen project: they observed and filmed changeovers, applied Pareto analysis to identify the most time-consuming steps, and discovered that two preparation activities that should have been performed during production were consistently being done after the line stopped. A revised standard — including a pre-changeover checklist and an updated operator training procedure — brought average changeover time down to 58 minutes within six weeks.

The lesson from Ferro Meccanica is clear: the right classification led to the right response. Treating Issue B with the urgency of Issue A would have wasted resources. Treating Issue A with the patience of a long-term improvement project would have prolonged the damage.

Key Takeaways

• Type 1 problems require reactive thinking: something has deviated from a known standard and must be restored urgently, with containment first and root cause analysis to prevent recurrence.
• Type 2 problems require critical thinking: the goal is not to restore but to elevate — to establish or strengthen a standard that moves performance to a higher level.
• Misclassifying a problem leads to misallocated effort: