The Gap Model: Standards, Actual Conditions, and the Birth of a Problem

Learning Objectives

• Define what constitutes a “problem” within the Lean and Kobetsu Kaizen framework using the Gap Model.
• Identify the three core components of the Gap Model: Standard, Actual Condition, and the Gap itself.
• Explain why a clearly defined standard is the prerequisite for recognizing any problem.
• Apply the Gap Model to real production scenarios to frame problems precisely before analysis begins.
• Distinguish between a vague complaint and a properly structured problem statement grounded in measurable data.

It is Monday morning at a stamping line. The shift supervisor walks the floor and notices the operator looks frustrated — parts are piling up at the downstream station, the line has stopped twice already, and someone has scrawled “machine acting up again” on the whiteboard. Everyone agrees something is wrong. But when the plant manager asks, “What exactly is the problem?”, the answers are different depending on who is speaking: the operator says the machine is unreliable, the quality engineer says the reject rate is high, and the maintenance technician says the tooling is worn. Three people, three different problems — or are they all pointing at the same underlying gap nobody has clearly defined yet? This is precisely where structured problem solving must begin: not with jumping to causes or countermeasures, but with understanding what a problem actually is and how to frame it with precision.

What Is a Problem? The Lean Definition

In everyday language, we use the word “problem” loosely to describe discomfort, inconvenience, or anything that feels off. In Lean thinking — and specifically within the Kobetsu Kaizen methodology — the word carries a precise, operational meaning. A problem is not a feeling. It is not an opinion. A problem is a measurable gap between a defined standard and the actual condition observed in the gemba.

This distinction matters enormously. Without a standard, there is no baseline against which reality can be compared. And without that comparison, there is no problem — only noise. The Lean principle of working from the gemba, where the work is done and the value is created, reinforces this: real problems are visible and measurable on the shop floor, not constructed in a conference room based on intuition.

The Kobetsu Kaizen approach, designed for middle-to-large-sized chronic losses requiring detailed expert-team analysis, places particular emphasis on this first act of problem framing. Before any root cause analysis tool — whether a 5x Why, a fishbone diagram, or a Pareto chart — is applied, the team must establish a rigorous and shared understanding of what the problem is. Step 2 of the Kobetsu Kaizen Board explicitly calls this out as Problem Representation: understand the current situation. Step 3 follows with target setting. The sequence is intentional and non-negotiable.

The Gap Model: Standards, Actual Conditions, and the Space Between

The Gap Model is the conceptual engine behind Lean problem identification. It has three components, each of which must be made explicit before structured problem solving can proceed.

1. The Standard (Specified Condition)

A standard is the defined, expected level of performance. It might be expressed as an OEE target, a cycle time, a defect rate per million parts, a safety incident frequency, or a delivery schedule adherence percentage. In the Kobetsu Kaizen framework, standards are often tied directly to the 16 major losses of machines and plants — the systemic categories that erode Overall Equipment Effectiveness (OEE).

The critical point is that a standard must be explicit, written, and measurable. A general expectation — “the machine should run well” — is not a standard. A standard reads: “Line 4 shall achieve a minimum OEE of 78% across a rolling four-week period.” Without this specificity, the gap cannot be quantified, and the problem cannot be framed.

2. The Actual Condition

The actual condition is what is really happening, observed directly and captured with data. This is where the Lean principle of speaking with data becomes essential. As illustrated in the Kobetsu Kaizen Board methodology, tools such as tally charts, frequency tables, flow diagrams, and Pareto diagrams are used precisely at this stage — not to find causes, but to accurately describe reality. The questions to answer are: What is the problem? Where does the emphasis lie? Who experiences it? How often does it occur?

This step demands discipline. Teams are often tempted to skip directly to countermeasures. The 5W1H analysis (Who, What, Where, When, Why, How) provides a structured framework to ensure the actual condition is described completely before the team moves forward.

3. The Gap

The gap is the arithmetic and strategic difference between the standard and the actual condition. It is the problem — stated precisely, framed in measurable terms, and bounded in scope. A well-formed gap statement might read: “Line 4 OEE averaged 61% over the last four weeks against a target of 78%, representing a 17-percentage-point gap driven primarily by unplanned downtime events of more than 10 minutes.”

This formulation does something powerful: it transforms a vague complaint into a structured problem that can be analyzed, prioritized, and ultimately resolved through countermeasures. It also sets the foundation for Step 3 of the Kobetsu Kaizen Board — target setting — where goals are defined using SMART criteria: Self-influenced, Measurable, Attractive, Realistic, and Time-limited, always oriented toward zero losses.

Practical Example: Fenwick Automotive Components

Fenwick Automotive Components is a mid-sized tier-2 supplier producing precision brackets for passenger vehicles. The plant manager at their northern facility noticed an increase in customer complaints about late deliveries. The production team launched a Kobetsu Kaizen project on their main press line.

Before any analysis began, the team gathered at the Kaizen Board to apply the Gap Model. First, they confirmed the standard: the press line was designed and scheduled to meet a delivery adherence target of 97% on-time fulfillment. This was documented in the production planning system and aligned with the customer contract.

Next, they captured the actual condition. Using a tally chart and a Pareto diagram over a six-week observation window, the team discovered that on-time delivery was running at 81%. Breakdowns in the hydraulic system of the press accounted for 58% of all lost production hours.

The gap was now clearly defined: a 16-percentage-point gap in on-time delivery, primarily attributed to unplanned hydraulic press stoppages averaging 3.2 hours per occurrence, occurring on average 2.4 times per week.

With this gap model in place, the team could set a SMART target — reduce hydraulic stoppages by 80% within 12 weeks — and move confidently into root cause analysis using the 5x Why method. The problem was no longer “the press is unreliable.” It was a precisely scoped, data-backed gap between standard and reality. That precision made all subsequent steps faster, more focused, and far more effective.

Key Takeaways

• A problem in Lean is always a gap: the measurable difference between a defined standard and the observed actual condition in the gemba.
• No standard means no problem: without an explicit, quantified baseline, there is nothing against which reality can be compared, and structured problem solving cannot begin.
• The actual condition must be captured with data: tools like tally charts, Pareto diagrams, and 5W1H analysis ensure the current reality is described accurately and completely before causes are explored.
• Gap framing precedes all analysis: in the Kobetsu Kaizen 8-step structure, Steps 1 through 3 — problem selection, problem representation, and target setting — must be completed rigorously before moving to cause analysis in Steps 4 and 5.
• A well-framed gap drives SMART targets: quantifying the gap enables the team to set goals that