Lesson 3: Process Mapping in KK Activities: Using Flow Diagrams to Expose Hidden Causes

When the Problem Hides in Plain Sight

Imagine a production line at a mid-sized automotive components plant. The team has been battling a recurring defect in a welding station for three months. They’ve replaced tooling, retrained operators, and tightened inspection criteria — yet the defect rate stubbornly refuses to drop below 4%. The root cause seems elusive. Then, during a Kobetsu Kaizen (KK) activity, a team leader decides to walk the entire process and sketch a flow diagram from raw material receipt to final inspection. Within an hour, something becomes visible that no inspection report had ever captured: a rework loop between two stations that nobody had formally documented, introducing inconsistent material orientation before the weld. The problem wasn’t at the weld. It was three steps upstream. Process mapping had done what data alone could not — it made the invisible, visible.

What Is Process Mapping and Why Does It Matter in KK Activities?

Process mapping is one of the core visual tools in the Kobetsu Kaizen Toolbox. Its primary purpose is to provide a structured, step-by-step representation of how work actually flows through a system — not how it should flow according to the standard operating procedure written two years ago, but how it really flows today, on the shop floor, under real conditions.

In the KK framework, process mapping is applied primarily in two critical phases: Step 2 (Problem Representation — understanding the current situation) and Step 4 (Root Cause Analysis). As shown in the Kobetsu Kaizen Board methodology, the flow diagram is a key tool for both exposing the problem concern and identifying the problem cause. This dual role makes it uniquely powerful among the 7 Quality Tools.

The fundamental question process mapping answers is: Who does what, in what sequence, and with what lead time and operating time? A well-constructed process map captures:

• Process steps: Each distinct activity in the sequence, from beginning to end
• Responsible parties: Who performs each step (person, role, or department)
• Turn-around times: The elapsed time between steps, including waiting and queuing
• Operating times: The actual hands-on time required for each activity
• Process costs: Where quantifiable, the cost associated with each step
• Decision points and loops: Rework loops, approval gates, or exception paths that deviate from the standard flow

It is precisely these loops and deviations — often undocumented and underestimated — that become the primary targets of a KK improvement activity. A process map transforms a vague complaint (“there are quality problems at the welding station”) into a concrete, shared picture of reality that the entire team can analyze together. This aligns directly with the Lean principle of Genchi Genbutsu — go and see for yourself — and supports the KK imperative to speak with data.

How to Build and Use a Flow Diagram in a KK Activity

Building an effective process map for a KK activity is not a desk exercise. It requires going to the Gemba — the actual place where work happens — and observing firsthand. Here is a structured approach aligned with KK methodology:

1. Define the boundaries: Clearly establish the beginning and end points of the process you are mapping. Scope creep is a common trap. In a KK activity focused on a specific loss or defect, the boundaries should encompass the full range of steps where the problem could originate — often wider than initially assumed.
2. Select knowledgeable participants: Involve experienced associates who know the work process intimately. As emphasized in process mapping best practices, these individuals can guide data collection and identify informal steps that never appear in written procedures.
3. Walk the process — don’t assume it: Start from the customer end (internal or external) and move upstream. Observe each step, ask questions, and collect factual data: times, frequencies, handoffs, waiting periods.
4. Map the actual state, not the ideal state: Record what you see, including rework loops, workarounds, and unofficial steps. These are precisely the areas where waste and hidden causes reside.
5. Annotate with facts and data: Add turn-around times, operating times, and any available cost or quality data to each step. This transforms the map from a simple flowchart into a quantified diagnostic tool.
6. Identify improvement potentials: Once the map is complete, use it as the foundation for a 5x Why Analysis or Fishbone Diagram to drill deeper into specific problem areas revealed by the map.

A key insight from KK practice is the distinction between turn-around time (total elapsed time, including waiting) and operating time (actual value-adding work time). In many processes, the ratio between these two figures is startling. A process with a total turn-around time of 11 days but only 10.5 minutes of actual operating time tells you immediately that the real problem lies not in the work itself, but in the flow — in queues, approvals, handoffs, and idle time. Process mapping makes this ratio visible and undeniable.

Practical Case Study: Mechatec Industries

Mechatec Industries is a fictional mid-sized manufacturer of precision hydraulic valves supplying Tier-1 automotive customers. Their KK team was tasked with reducing the lead time for a critical valve subassembly from 8 days to under 3 days — a customer-driven target tied to a new just-in-time delivery contract.

The team began by mapping the current state process from raw material staging through final pressure testing and packaging. The process involved four people across three departments: Ms. Meier in machining, Ms. Schulz in assembly, Mr. Miller in quality control, and Mr. Bauer in packaging and dispatch. When the team walked the process and collected data, the map revealed the following:

• Total turn-around time: 11 days (vs. the 3-day target)
• Total operating time: 10.5 minutes
• A rework loop between assembly (Ms. Schulz) and quality control (Mr. Miller) that occurred on approximately 30% of units and added an average of 2 full days of delay per occurrence
• A 6-day waiting period between machining completion and assembly start, caused by a batch transfer policy that held parts until a minimum lot size was accumulated

Without the process map, the team would likely have focused on the 10.5 minutes of operating time — trying to speed up individual tasks. Instead, the map made it immediately clear that the 11 days were almost entirely composed of waiting, batching, and rework. The KK team used the map as the input for a focused 5x Why Analysis on the rework loop, discovering that a dimensional tolerance on an upstream machining step was borderline — passing first inspection but failing under final pressure test conditions. A targeted countermeasure was implemented within two weeks, eliminating the rework loop and reducing lead time to 2.8 days.

Key Takeaways

• Process mapping is a diagnostic tool, not just a documentation tool. In KK activities, it serves both to represent the problem situation (Step 2) and to identify root causes (Step 4) by making the actual flow of work visible and quantifiable.
• Always map the actual state from the Gemba. Informal rework loops, undocumented handoffs, and unofficial workarounds — the very sources of hidden losses — only become visible when you observe and record what truly happens, not what the procedure says should happen.
• Turn-around time vs. operating time is a critical diagnostic ratio. A large gap between these two figures immediately signals that waste is embedded in the flow — in waiting, batching, or rework — rather than in the individual