Lesson 3: Populating the KK Board with Data — Making Your Problem Statement Objective and Measurable

Opening: When Numbers Sit on a Whiteboard Without Telling a Story

Imagine walking into a production meeting at a mid-sized automotive components plant. The shift supervisor points to a handwritten number on the whiteboard: “OEE: 67%.” Everyone nods. Nobody moves. The number is there, but it isn’t doing any work. There is no clear problem statement, no baseline, no target, and no owner. The Kobetsu Kaizen board on the wall is half-filled with sticky notes and rough sketches. This is one of the most common failure modes in continuous improvement: data is present, but it has not been transformed into a structured, objective, and measurable problem statement. Populating your KK board correctly — using real operational data — is the discipline that separates reactive firefighting from genuine, sustained problem solving. This lesson shows you exactly how to do it.

Step 1 and Step 2 of the KK Board — From Loss Identification to Problem Representation

The Kobetsu Kaizen board follows a structured sequence of steps. The first two steps — Problem Selection and Problem Representation — are where operational data must be anchored firmly. Getting these two steps right determines the quality of everything that follows.

Step 1: Selecting the Right Problem Using Loss Data

Kobetsu Kaizen is designed to tackle focused, individual improvements — typically middle-sized to larger problems that require structured, detailed analysis by an expert team. The starting point is always one of the 16 losses framework, which categorizes all operational waste into eight main equipment losses (including breakdowns, set-up losses, minor stoppages, reduced speed, and defect/rework losses), five process losses, and losses related to energy, materials, and tooling.

Your operational data — OEE breakdowns, downtime logs, scrap reports, production tracking systems — maps directly onto this 16-losses structure. Before you write a single word on the KK board, pull data for a meaningful period (a minimum of three months is the standard reference horizon used in practice) and ask: Which loss category is consuming the most capacity, cost, or quality performance? Tools like Pareto diagrams are essential here. They let you rank losses by frequency or by impact, so you focus the team’s effort where the data says it matters most — not where gut feeling points.

The output of Step 1 is not a vague complaint. It is a specific loss category tied to a specific machine, line, or process area, supported by ranked data. For example: “Minor stoppages on Line 4 account for 38% of all unplanned downtime in the past 13 weeks.”

Step 2: Representing the Problem — Making It Objective and Measurable

Step 2 is where most teams underperform. The instruction is deceptively simple: understand the current situation. In practice, this means translating raw data into a visual, factual, and unambiguous representation of the problem as it actually exists — not as people remember it, not as it was six months ago.

The KK methodology requires you to speak with data. This means populating the board with graphical representations of your key performance indicators. Trend charts, tally charts, and Pareto diagrams are your primary tools at this stage. A tally chart, for instance, helps you capture problem occurrence frequency in a systematic way — useful both for problem concern and for identifying surface-level causes. A flow diagram can reveal where in the process the loss is actually occurring, preventing the team from solving the wrong location.

The problem statement itself must meet the SMART criteria: it must be Self-influenced (the team can impact it), Measurable (you can quantify the current state and track change), Attractive (meaningful to the business), Realistic (achievable within scope), and Time-limited (with a defined improvement horizon). A well-formed problem statement supported by data might read: “The average minor stoppage frequency on Line 4 is 14 occurrences per shift, resulting in 52 minutes of lost production daily, measured over 13 weeks.” This is objective, quantified, and leaves no room for interpretation.

Step 3: Setting Targets — Orienting Toward Zero

Once the current situation is clearly represented with data, Step 3 requires the team to set a goal. The Kobetsu Kaizen philosophy is explicit about orientation: the target is always zero — zero breakdowns, zero defects, zero accidents. This is not naive idealism; it is a strategic anchor that prevents teams from accepting chronic losses as normal.

In practice, setting a SMART target means defining the gap between your current measurable baseline and your improvement goal, with a clear timeline. If minor stoppages currently run at 14 per shift, a realistic intermediate target might be 4 per shift within 90 days — reducing losses by more than 70% — while the long-term orientation remains zero. The target must be written on the board, visible to everyone, and directly traceable back to the same metric used to describe the current state. This creates the discipline of comparing original and present conditions, which is the foundation of the Check step in the PDCA cycle embedded in the KK board structure.

When performing cost-benefit analysis — a key component of justifying KK projects — the target also anchors the financial case. By quantifying the loss in terms of production loss, man-hours, material waste, or energy, and then projecting the value of closing the gap, teams can present a clear business rationale for resource investment.

Practical Example: Meridian Plastics — Turning Downtime Data into a KK Board Entry

Meridian Plastics is a fictional injection molding manufacturer producing components for the white goods sector. Their production team had been struggling with what operators called “random stoppages” on Injection Press 7. The maintenance log was full of short entries: “Machine stopped — restarted,” with no duration or cause recorded consistently.

The KK facilitator introduced a tally chart for two weeks. Operators logged every stoppage by category: material jam, sensor fault, temperature deviation, operator intervention, and other. After 10 working days, the data revealed that 61% of all stoppages fell into the “material jam” category, averaging 3.2 minutes each and occurring 11 times per shift. A Pareto diagram made this instantly visible on the KK board.

The problem statement was now written with precision: “Material jams on Press 7 cause an average of 35 minutes of unplanned downtime per shift (11 occurrences × 3.2 min), representing 7.3% of available production time, based on a 10-day measurement period.” The SMART target was set at fewer than 2 occurrences per shift within 60 days, maintaining the zero-loss orientation as the long-term goal.

With this structured, data-populated board, the team could move confidently into root cause analysis using 5W1H analysis and the N5W method, selecting tools from the KK toolbox that matched the nature of the problem — in this case, a combination of a fishbone diagram and a 5-Why sequence focused on material handling and feeder design. The board was no longer a collection of opinions; it was a living record of facts.

Key Takeaways

• Anchor your KK board to the 16 losses framework. Use at least three months of operational data and a Pareto diagram to identify and prioritize which loss category deserves focused attention before writing anything on the board.
• A problem statement is only valid when it is measurable. Include the specific metric, the current baseline value, the measurement period, and the business impact. Vague descriptions lead to unfocused analysis and wasted team effort.
• Apply SMART criteria to both the problem description and the target. The goal must be self-influenced, measurable, attractive, realistic, and time-bound — with zero loss as the permanent orientation.
• Choose