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.
• Distinguish between a standard (specified condition) and an actual condition on the shop floor.
• Explain how the gap between standard and actual condition gives birth to a problem worth solving.
• Apply the Gap Model to identify and frame real problems in a production environment.
• Recognize why a problem cannot exist — or be solved — without a clearly defined standard.

It is 6:45 on a Monday morning. The line supervisor at a mid-size automotive components plant walks onto the floor and notices that one of the assembly stations has been producing slightly oversized parts since the end of the previous shift. Operators have been compensating manually, adjusting fixtures by feel, and the output looks acceptable to the naked eye. No alarm has been raised. No ticket has been written. To most people on the floor, there is no problem — the line is running and parts are shipping. But there is a problem, and it has been invisible for one specific reason: nobody paused to ask, “What is the standard here, and are we meeting it?” This is precisely the situation the Gap Model is designed to prevent — and to resolve.

What Is a Problem, Really? The Lean Definition

In everyday language, people use the word “problem” loosely. A problem might mean an argument, a delay, a breakdown, or simply something that feels uncomfortable. In a Lean and Kobetsu Kaizen context, however, the definition is precise and operational: a problem is the gap between a defined standard (the specified condition) and the actual condition being observed.

This definition has profound implications. It means that without a standard, there can be no problem — only noise, opinion, and frustration. A standard might be a cycle time target, a defect rate, an OEE threshold, a safety protocol, or a delivery frequency. Once that standard exists and is understood, any deviation from it immediately becomes a problem that demands structured attention.

This is the foundation of structured problem solving in Kobetsu Kaizen. As outlined in the Kaizen Board methodology, Step 1 — Problem Selection — asks the essential question: “Which problem should we work on?” But you can only answer that question meaningfully if you first know what your standards are, and where reality falls short of them. The gap between specified condition and actual condition is not just a starting point — it is the very definition of the problem itself.

It is worth noting that in the Kobetsu Kaizen framework, problems are not random events to be patched. They are chronic losses — recurring, measurable deviations that accumulate over time and erode performance across quality, cost, delivery, safety, and motivation (QCDSM). Recognizing this changes how plant managers and team leaders approach their daily work: instead of firefighting, they learn to see, frame, and attack the root causes of persistent gaps.

The Gap Model: Anatomy of a Problem

The Gap Model can be visualized simply: at the top sits the standard — the target, the norm, the specified condition that defines what “good” looks like. At the bottom sits the actual condition — the measurable reality of what is happening right now. The vertical distance between these two levels is the gap, and the gap is the problem.

This model is embedded throughout the Kobetsu Kaizen process. In Step 2 — Problem Representation — the task is explicitly to understand the current situation: What is the problem? Where does the emphasis lie? Who experiences it? How frequently does it occur? These questions cannot be answered without first anchoring the analysis to a standard. The comparison of specified condition with actual condition is the compass that orients all subsequent analysis.

Three elements define the Gap Model in practice:

• The Standard (Specified Condition): A quantified, agreed-upon target. This could be a process parameter, a quality spec, an output rate, or a safety rule. Without this, the gap cannot be measured.
• The Actual Condition: What is currently being observed and measured at the gemba — the place where the work is done and value is created. Data, not assumptions, define this level.
• The Gap: The quantified difference between standard and actual. This gap drives Step 3 — Set Targets — where the team defines what “zero gap” would look like and sets SMART goals: Specific, Measurable, Attractive, Realistic, and Time-limited.

A critical insight from this model is directional: the gap always points downward from standard to reality. This means the standard is aspirational — it represents the designed intent of the process. In Kobetsu Kaizen, targets are oriented toward zero: zero errors, zero defects, zero accidents. This “orientation on zero” is not idealism; it is the logical consequence of taking the Gap Model seriously. If a standard exists, any deviation is unacceptable by definition, and the goal is always to close the gap completely.

Practical Example: Identifying the Gap at Prestige Stampings S.r.l.

Consider Prestige Stampings S.r.l., a fictional manufacturer of metal brackets for the white goods industry. Their press line has a documented OEE standard of 78%. Over the past three months, actual OEE has averaged 61%. The gap is 17 percentage points — and it is consistent, not a one-off event. This makes it a chronic loss, exactly the type of problem that Kobetsu Kaizen is designed to address.

The team leader, following the Kaizen Board methodology, begins Step 2 by documenting the actual condition with data: tally charts showing breakdown frequency, a Pareto diagram identifying that 65% of downtime comes from two specific failure modes, and a process flow diagram highlighting where micro-stoppages cluster. None of this analysis would be meaningful without the 78% OEE standard as the reference point. The standard makes the gap visible. The gap makes the problem real.

In Step 3, the team sets a SMART target: reach 74% OEE within 90 days by eliminating the two dominant failure modes. This target does not emerge from guesswork — it emerges directly from the gap analysis. The distance between 61% and 78% defines the improvement space. The team is now working on a real problem, framed correctly, with a measurable goal and a clear baseline.

Without applying the Gap Model, this situation might have been described vaguely as “the press line isn’t performing well.” With it, the problem becomes: “OEE on Press Line 3 is running at 61% against a standard of 78%, representing a 17-point gap driven primarily by two recurring failure modes.” That is a problem statement a team can act on.

Key Takeaways

• No standard, no problem: In Lean thinking, a problem only exists when there is a defined standard to deviate from. Establishing clear standards is the prerequisite for all structured problem solving.
• The gap is the problem: The measurable distance between the specified condition and the actual condition is the precise, actionable definition of a problem in the Kobetsu Kaizen framework.
• Data defines the actual condition: Opinions and impressions are not enough. The Gap Model requires real, observable data collected at the gemba to establish where reality truly stands.
• Targets are born from the gap: SMART goals in Step 3 of the Kaizen Board process are not arbitrary. They are derived directly from the size and nature of the gap, always oriented toward closing it to zero.
• Chronic losses demand structured framing: Kobetsu Kaizen targets persistent, recurring deviations — not one-time events. Correctly framing the gap transforms firefighting into structured, root-cause-driven improvement.