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

Opening: When the Line Stops, What Kind of Problem Do You Have?

It is 6:47 AM on a Tuesday. The morning shift has just started at a mid-sized automotive components plant, and within minutes the team leader receives two separate alerts. First: a welding station has started producing parts with inconsistent seam depth — a deviation from the defined quality standard that began overnight. Second: the plant manager walks in with a challenge from the customer — they want a 15% reduction in lead time over the next quarter, something the current process was never designed to deliver. Both situations are called “problems” in everyday language. But in Kobetsu Kaizen, treating them the same way would be a costly mistake. They belong to fundamentally different categories — and each demands a fundamentally different response.

Understanding the Four-Type Framework: Where Type 1 and Type 2 Fit

The Kobetsu Kaizen methodology classifies problems into four distinct types, each defined by its nature, its relationship to existing standards, and the thinking mode required to address it. This classification is not academic — it directly determines which tools to apply, which team to involve, and how much time and resource to invest.

The four types are:

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

This lesson focuses on the critical distinction between Type 1 and Type 2 — two categories that are often confused but serve very different purposes in structured problem solving. Understanding this distinction is one of the first and most important skills a team leader or plant manager must develop before selecting a problem-solving path.

Type 1 vs. Type 2: A Deep Dive into the Difference

Type 1 — Restoring What Should Already Be There

Type 1 problems are defined by urgency. Something has gone wrong that was not supposed to go wrong — a machine breaks down unexpectedly, a quality defect suddenly appears on the line, a safety incident occurs. The defining characteristic of Type 1 is that a known, accepted standard exists, but for some reason the current reality has deviated from it.

The thinking mode required here is primarily reactive and critical. You are not designing something new. You are diagnosing what changed, identifying the root cause of the deviation, and restoring normal operating conditions as quickly and reliably as possible. In Lean terms, this is often referred to as getting back to standard.

Type 1 problems are well-suited to the structured 8-step Kaizen Board approach, where teams compare the original condition against the present condition, analyze causes using tools like 5-Why analysis, Pareto diagrams, and cause-and-effect diagrams, then deploy countermeasures and verify their effectiveness. The goal is clear: return to the defined standard and prevent recurrence.

In a Type 1 problem, the standard is your destination. You already know where you need to go — the challenge is figuring out why you drifted away and how to get back.

Type 2 — Raising the Bar Beyond Current Performance

Type 2 problems are fundamentally different in nature. Here, the standard itself is no longer sufficient. Either the process is performing exactly as designed but the result is no longer good enough, or there is no standard at all for a new situation the organization is facing. In both cases, the task is not to restore something that existed — it is to create a new, higher level of performance.

This type of problem requires a shift in thinking mode. While critical thinking still plays a role, creative thinking becomes essential. The team must imagine a future state that does not yet exist, design the path to reach it, implement the necessary changes, and then establish a new standard that locks in the improvement. This is the essence of Kaizen in its most proactive form.

Type 2 problems are closely linked to what the Kobetsu Kaizen framework describes as improvement-driven projects — efforts that are mid-term to long-term, often involve cross-functional expert teams, and require detailed analysis. They are not solved by simply fixing what broke; they are solved by redesigning what exists.

In a Type 2 problem, the standard is your starting point — not your goal. You are being asked to go beyond what has ever been achieved before in this process.

Why the Distinction Matters for Problem Solvers

Misclassifying a problem leads to wasted effort and poor outcomes. Applying a Type 1 mindset to a Type 2 problem means you will restore a standard that is no longer adequate — and the gap between performance and expectation will persist. Applying a Type 2 mindset to a Type 1 problem means you may spend months redesigning a process when the real issue was a single operator skipping a step in the work instruction. The classification step is not bureaucracy — it is a form of precision that saves time, money, and frustration.

Practical Case Study: Metalform Industries

Metalform Industries is a fictional mid-tier supplier of stamped metal components. Their press line has been running at an OEE of 72% for the past 18 months — stable, consistent, but below the 80% world-class benchmark their operations director has set as a strategic target for the year.

Last week, OEE dropped sharply to 58% over three consecutive shifts. Investigation revealed that a lubrication interval had been missed due to a gap in the maintenance schedule — a clear deviation from the existing preventive maintenance standard.

The team correctly identifies this as a Type 1 problem. They use the 8-step Kaizen Board: they document the current condition versus the standard, perform a 5-Why analysis, discover that the maintenance checklist had not been updated after a machine modification six months earlier, deploy a corrective action, update the standard work document, and verify that OEE returns to 72% within one week.

Now the team turns its attention to the bigger challenge: reaching 80% OEE. This is a Type 2 problem. There is no breakdown, no deviation — the machine is running exactly as it always has. But “as it always has” is no longer good enough. The team forms a Kobetsu Kaizen project group, maps chronic losses across the OEE pillars, applies more detailed analysis tools, experiments with new changeover sequences, and over four months defines and validates a new operating standard that consistently delivers 81% OEE. The new standard is documented, trained, and audited.

Same line. Same team. Two different types of problems — and two completely different problem-solving journeys.

Key Takeaways

• Type 1 problems are about restoring an existing standard — they require reactive and critical thinking, and success means returning to a known, defined level of performance.
• Type 2 problems are about raising the standard — they require creative thinking and result in a new, higher baseline that the organization must then maintain and protect.
• Correct classification is the first act of structured problem solving — applying the wrong approach wastes resources and delays real improvement.
• Both types follow structured methodologies, but the tools, timelines, and team compositions differ significantly between them — Type 1 tends to be faster and team-focused, while Type 2 projects are longer-term and often require expert involvement.
• In Kobetsu Kaizen, standards are living documents — Type 1 defends them, Type 2 evolves them, and both activities are essential to a healthy continuous improvement culture.