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

When the Problem Hides in Plain Sight

Picture this: a production line at a mid-sized automotive components plant has been struggling with recurring defects on a welded sub-assembly. The team has held meetings, replaced tooling, and retrained operators — yet the reject rate stubbornly hovers above 4%. The root cause remains elusive because nobody has ever sat down and drawn exactly what happens between the moment raw material enters the cell and the moment a finished part moves downstream. Everyone assumes they know the process. In reality, each person knows only their own slice of it. This is precisely the scenario where a Process Mapping session, embedded within a Kobetsu Kaizen (KK) activity, transforms confusion into clarity — and exposes the hidden causes that data tables and verbal reports simply cannot reveal.

What Is Process Mapping and Why Does It Belong in Your KK Toolkit?

Process Mapping — sometimes called a Flow Diagram or Process Diagram — is one of the seven classic quality tools and occupies a defined role in structured problem-solving. Within the Kobetsu Kaizen Board framework, it is listed as a primary tool for both problem concern (Step 2: understanding the current situation) and problem cause analysis (Step 4: root cause investigation). This dual function makes it uniquely powerful: it first helps the team see what is happening, and then helps them understand why it is happening.

A Flow Diagram is a visual representation of a process sequence — every step, every decision point, every handoff between people, machines, or departments. Unlike a verbal description or a simple checklist, it forces the team to agree on a single shared reality. When you map a process together with the people who actually perform it, inconsistencies, loops, redundancies, and gaps become immediately visible. These are the hiding places of waste and defects.

In the context of KK activities, process mapping is not a bureaucratic exercise. It is a structured GEMBA-based conversation. The best maps are built on the shop floor, with operators, team leaders, and engineers standing at the actual workstation — observing, questioning, and recording. As the KB materials remind us: “Select experienced associates who know the work process, and can lead the data collection process. Start at the customer end and then go upstream. Observe and take notes on each step. Ask questions and collect data where possible.” This upstream-to-downstream discipline ensures nothing is assumed and nothing is skipped.

How to Build and Read a Process Map in KK Problem Solving

A practical KK process map captures more than just process steps. It integrates the following layers of information alongside each step:

• Who performs the step — individual, role, or department responsible
• Operating time — the actual hands-on time required to execute the step
• Turn-around time (lead time) — total elapsed time including waiting, queuing, and transport
• Process costs — where known, the resource cost associated with each step
• Decision points and loops — rework loops, inspection gates, approval cycles, and exception paths

The KB materials illustrate this clearly with a multi-person process example: Ms. Meier, Ms. Schulz, Mr. Miller, and Mr. Bauer each own a step, with individual operating times of 3, 5, and 2.5 minutes and turn-around times of 5, 6, and 4 days respectively. When summed, the total operating time is only 10.5 minutes — but the total lead time is 11 days. That gap is a direct indicator of waste: waiting, batching, unnecessary handoffs, or approval delays hidden within the white spaces between process boxes.

This is a critical insight for plant managers and team leaders: the ratio between operating time and lead time tells you where to look for root causes. A tiny operating time buried inside a large lead time almost always signals systemic problems — unclear responsibilities, missing standards, information bottlenecks, or inventory accumulation. The process map makes this visible at a glance.

Once the current-state map is complete, the team applies analytical overlays. Two of the most powerful are:

1. 5x Why Analysis on specific steps — identify which step produces the defect or deviation, then drill down with repeated “why” questioning anchored to that specific point in the flow
2. Rework and loop identification — trace every path where work travels backward (corrections, re-inspections, re-approvals) and quantify the frequency and cost of each loop

Both analyses are significantly more focused and productive when performed on a completed process map, because the team can point to an exact location and say: “The problem originates here, between step 3 and step 4, not somewhere vague in the process.”

Practical Case Study: Electra Components GmbH

Electra Components GmbH, a fictional manufacturer of electrical junction boxes, was experiencing chronic delivery delays on a key customer order. On-time delivery had fallen to 71% over three consecutive months. Initial data from Pareto analysis showed that 60% of delays originated in the “final assembly and testing” area. However, repeated 5x Why sessions with operators produced inconsistent answers because the team was describing different versions of the same process.

During a two-day KK activity, the team facilitated a detailed process mapping session directly on the assembly floor. They followed the part from incoming inspection through sub-assembly, wiring, housing closure, electrical testing, labeling, and final packaging — involving seven different operators and two shift supervisors. Each step was documented with owner, operating time, and turn-around time.

The map revealed three critical findings that had never been formally acknowledged:

• A rework loop between the wiring step and the electrical test step was consuming an average of 1.8 additional days per batch, triggered by an inconsistent wire routing standard that existed in two conflicting versions
• The labeling step was performed by a single operator with no backup, creating a bottleneck every time that person was absent — adding up to 0.5 days of average delay per order
• The total operating time across all steps was 22 minutes, but the total lead time was 9 days — a ratio of more than 500:1, confirming that the process was dominated by waiting and queuing, not by actual work

With the map as the foundation, the team launched targeted countermeasures: standardizing the wire routing procedure (resolving the conflicting documents), cross-training a second operator for labeling, and implementing a visual pull signal between sub-assembly and final assembly to eliminate batch queuing. Within six weeks, on-time delivery improved to 91%. The process map did not solve the problem — but it showed exactly where the problem was hiding.

Key Takeaways

• Process Mapping is a dual-function KK tool — it supports both understanding the current situation (Step 2) and identifying root causes (Step 4) on the Kobetsu Kaizen Board.
• Build the map at the GEMBA, with the people who actually do the work, observing the actual process — not in a conference room based on assumptions.
• Capture time data at every step: operating time and turn-around time. The gap between the two is your roadmap to hidden waste and systemic causes.
• Rework loops and decision branches are the most important features to identify — they represent process instability and are frequent hosts of recurring defects and delays.
• Combine the process map with 5x Why and Pareto analysis for maximum analytical power: use the map to locate the problem, then use root-cause tools to explain it.