5.2 Flowcharts, Swimlane Diagrams & Process Value Analysis

5.2 Flowcharts, Swimlane Diagrams & Process Value Analysis

Executive Principle: While a SIPOC establishes the high-level boundary of a project, improvement teams cannot diagnose root causes of variation, defects, and lead-time delays without drilling into operational execution. Detailed process flowcharts, cross-functional swimlane diagrams, and spaghetti diagrams expose the handoffs, decision branches, idle queues, and physical transit paths where process friction occurs. In turn, Value-Added Process Analysis provides the quantitative filter to separate genuine customer value from organizational waste.

Process mapping is both a visual communication tool and an analytical diagnostic discipline. In Six Sigma, a process map is not merely a static illustration; it is a dynamic model that reveals how work flows, where value is added, where defects are introduced, and where time is lost. A Green Belt must master standard flowcharting conventions, understand the three tiers of process mapping granularity, and evaluate every task against rigorous value-added criteria.

---

The Three Levels of Process Mapping Granularity

A common pitfall in continuous improvement is failing to align the detail of a process map with the project's analytical objective. Six Sigma recognizes three hierarchical mapping tiers:

                    The Three-Tier Process Mapping Hierarchy

   Level 1: Macro / Executive (SIPOC) ────────▶ 30,000-ft View (4 - 7 core blocks)
            │
            ▼
   Level 2: Cross-Functional (Swimlane) ──────▶ Operational handoffs & decisions
            │
            ▼
   Level 3: Micro / Task-Level Flowchart ─────▶ Step-by-step SOPs & keystrokes

Each block in a Level 1 SIPOC process column typically unpacks into 5 to 15 operational steps on a Level 2 process flowchart. By maintaining this strict hierarchy, the Green Belt prevents team members from getting lost in minutiae before the overarching architecture is validated.

---

Standard ANSI / ISO Flowchart Symbols

To ensure unambiguous interpretation across global organizations, process flowcharts adhere to standardized geometric conventions established by the American National Standards Institute (ANSI) and the International Organization for Standardization (ISO).

Critical Rules for Decision Diamonds

On Six Sigma certification exams, decision symbols are subject to strict syntax rules:

1. Mutually Exclusive Exits: Outbound paths must be labeled clearly (e.g., Yes/No, Pass/Fail, Approved/Rejected). A decision diamond should never have a single ambiguous outbound flowline.
2. No Dead Ends: Every path leaving a decision diamond must eventually terminate in an end oval or loop back to an upstream process step.
3. Rework Loops: When an evaluation results in a "Fail" or "Rework" condition, the arrow loops backward to an earlier operational step. These loops immediately highlight rework waste and hidden factory operations.

---

Swimlane (Cross-Functional / Deployment) Flowcharts

A Swimlane flowchart (also known as a Deployment Map or Cross-Functional Process Map) organizes activities into horizontal rows or vertical columns assigned to specific departments, functional roles, or IT systems.

                  Cross-Functional Swimlane Flowchart Architecture

  LANE: Role / Dept   │ Activities & Handoffs
  ────────────────────┼─────────────────────────────────────────────────────────────
  Customer            │  [Submit Order] ───────────────────────────────────────────┐
                      │                                                            │
  Sales Department    │                                ┌──▶ [Verify Credit] ───────┼──┐
                      │                                │       │ (Pass)            │  │
  Warehouse / Ops     │                                │       ▼                   │  │
                      │                                │    [Pick & Pack] ◀────────┘  │
  Finance / Billing   │                                │       │                      │
                      │                                │       ▼                      │
                      │                                └── [Issue Invoice] ◀───────────┘

Why Swimlanes are Critical in Six Sigma

Traditional linear flowcharts show what is done, but they fail to show who does it. In modern enterprises, processes rarely fail because individual workers do not know how to do their tasks; processes fail in the handoffs between departments—often referred to as "the white space between the boxes."

Swimlane flowcharts explicitly illuminate:

• Departmental Handoffs: Every time a flowline crosses a lane boundary, work is handed off from one group to another. Handoffs introduce communication breakdowns, queue delays, and loss of accountability.
• Bottlenecks and Stagnation: If multiple lines enter a specific lane (e.g., Legal or Quality Assurance) but few exit, that functional unit is an operational bottleneck.
• Redundant Roles & Approvals: Swimlanes expose redundant handoffs where work bounces back and forth between two departments (e.g., Engineering and Drafting) repeatedly.
• System vs. Human Interfaces: Dedicating a swimlane to an Enterprise Resource Planning (ERP) system highlights manual data entry points where human operators re-key data already stored in another database.

---

Spaghetti Diagrams: Physical Movement & Layout Analysis

While flowcharts map the logical sequence of work, a Spaghetti Diagram maps the physical flow of people, materials, equipment, or paperwork across a physical facility.

Definition and Construction Protocol

1. Obtain a Scaled Floor Plan: Secure an accurate architectural layout of the work environment (e.g., factory shop floor, warehouse, clinic, or office suite).
2. Conduct a Gemba Walk: Physically observe the operator, material batch, or paperwork sample as it moves through the entire process.
3. Trace Every Movement: Draw a continuous line tracking every single step, footstep, retrieval, and transit path taken during the observation period. Do not straighten lines or assume shortest paths.
4. Quantify Distance and Time: Use a measuring wheel, pedometer, or digital floor scale to calculate the total cumulative distance traveled (e.g., feet, meters, or miles per shift).

                    Spaghetti Diagram Layout Visualization

     ┌───────────────────────────────────────────────────────────────┐
     │ [Raw Material Storage]                 [Finished Goods Dock]  │
     │         │                                        ▲            │
     │         │       ┌─────────────────┐              │            │
     │         └──────▶│ Lathe Station 1 │────────┐     │            │
     │                 └─────────────────┘        │     │            │
     │                                            ▼     │            │
     │                 ┌─────────────────┐     ┌──────────────┐      │
     │         ┌──────▶│ Milling Station │────▶│ Quality QA   │      │
     │         │       └─────────────────┘     └──────────────┘      │
     │         │                                        │            │
     │         └────────────────────────────────────────┘            │
     │          (Excessive crisscrossing indicates motion waste)     │
     └───────────────────────────────────────────────────────────────┘

Practical Diagnostic Value

A completed spaghetti diagram typically resembles a plate of tangled spaghetti—hence the name. It provides undeniable visual evidence of:

• Motion Waste: Operators walking miles per day to fetch common tools, forms, or supplies.
• Transportation Waste: Work-in-process (WIP) crisscrossing the facility multiple times between sequential operations.
• Safety & Collision Hazards: High-traffic intersections where forklifts, carts, and pedestrians intersect.
• Layout Redesign Opportunities: Justifying the transition from a traditional functional/departmental layout to a U-shaped manufacturing cell where sequential steps are co-located.

---

Process Value Analysis: The Three Categories of Work

Creating process flowcharts is only an intermediate step; the ultimate diagnostic goal is to interrogate every single activity on that map. In Lean Six Sigma, every task is systematically categorized into Value-Added (VA), Business Non-Value-Added (BNVA), or Non-Value-Added (NVA) work.

                    The Three Operational Work Categories

        ┌─────────────────────────────────────────────────────────────┐
        │                      TOTAL WORK STEPS                       │
        └──────────────────────────────┬──────────────────────────────┘
                                       │
         ┌─────────────────────────────┼─────────────────────────────┐
         ▼                             ▼                             ▼
  ┌──────────────┐              ┌──────────────┐              ┌──────────────┐
  │ Value-Added  │              │ Business NVA │              │   Pure NVA   │
  │     (VA)     │              │ (BNVA/Type I)│              │(Type II Muda)│
  ├──────────────┤              ├──────────────┤              ├──────────────┤
  │ Meets all 3  │              │ Required by  │              │ Fails value  │
  │ criteria     │              │ law/policy;  │              │ test; no     │
  │ (Customer    │              │ no customer  │              │ regulatory   │
  │ pays, alters │              │ value        │              │ requirement  │
  │ state, RFT)  │              │              │              │              │
  ├──────────────┤              ├──────────────┤              ├──────────────┤
  │   MAXIMIZE   │              │   MINIMIZE   │              │  ELIMINATE   │
  └──────────────┘              └──────────────┘              └──────────────┘

1. Value-Added (VA) Activities

An activity is classified as Value-Added (VA) if and only if it satisfies all three of the following non-negotiable criteria:

1. Customer Willingness to Pay: The end customer recognizes the value of the step and is willing to pay for it. If the activity were listed as an itemized fee on their invoice, the customer would accept it without objection.
2. Physical / State Transformation: The activity must transform the form, fit, function, or informational state of the deliverable toward customer specifications. Moving a component, filing a record, or copying data from one screen to another does not transform it.
3. Done Right the First Time (RFT): The step must be executed correctly on its initial attempt. Any effort spent correcting defects, repairing mistakes, re-entering missing data, or polishing burrs fails this criterion immediately.

2. Business Non-Value-Added (BNVA / Type I Muda)

Business Non-Value-Added (BNVA) steps—also known as necessary waste or Type I Muda—are activities that fail the customer value test, but are strictly necessary under current legal, regulatory, health, safety, accounting, or contractual constraints.

• Why they exist: External government statutes (e.g., FDA batch documentation, OSHA safety checklists, SEC financial disclosures, HIPAA compliance logs, Sarbanes-Oxley audit trails) or current institutional governance.
• Customer perspective: If given the choice, the customer would not pay for these activities, but the business cannot legally or responsibly operate without them.
• Operational mandate: Minimize, streamline, and automate. Satisfy the compliance requirement with the lowest possible expenditure of labor and cycle time.

3. Non-Value-Added (NVA / Type II Muda)

Non-Value-Added (NVA) steps—known as pure waste or Type II Muda—are activities that consume time, space, materials, or capital without creating customer value and without being required by any law or regulatory body.

• Examples: Waiting in queues, batch sorting, staging inventory, multiple management sign-offs on low-risk transactions, re-keying data between disparate software tools, expediting orders, and inspecting output to screen out upstream defects.
• Operational mandate: Eliminate immediately. Remove these steps from the process without replacing them.

---

Cross-Industry Value Classification Matrix

The following table illustrates how operational activities across manufacturing, healthcare, and financial services are categorized:

---

Process Cycle Efficiency (PCE)

A critical quantitative metric derived from Value-Added Process Analysis is Process Cycle Efficiency (PCE), sometimes called Flow Efficiency.

The Mathematical Formulation

Process Cycle Efficiency measures the proportion of total lead time that is actually spent transforming the product or service in a manner the customer values:

\text{PCE} = \left( \frac{\text{Total Value-Added Time (VAT)}}{\text{Total Process Lead Time (PLT)}} \right) \times 100\%$$$$\text{Where:}$$$$\text{VAT} = \sum \text{Duration of all Value-Added (VA) steps}$$$$\text{PLT} = \text{Total elapsed clock time from process start trigger to final deliverable handover}

[!NOTE] Lead Time vs. Touch Time: Process Lead Time (PLT) is the total clock time experienced by the product or customer from beginning to end (including all waiting, transit, and queue times). Value-Added Time (VAT) is strictly the active touch time during which value is being added.

Benchmark Realities

• Unoptimized Traditional Workflows: Most unoptimized administrative, transactional, and service processes operate at a PCE of less than 5% (often between 0.5% and 3%). In manufacturing, batch-and-queue systems typically exhibit a PCE under 10%.
• World-Class Lean Operations: A Lean Six Sigma optimized process typically achieves a PCE of 20% to 40% in transactional or high-mix environments, and above 50% in dedicated continuous-flow manufacturing cells.

---

Worked Computational Example: Commercial Mortgage Underwriting

A Six Sigma project team maps an end-to-end commercial loan approval process. The total Process Lead Time (PLT) from initial customer submission to final commitment letter is 10 business days (80.0 working hours).

A time study of the operational steps reveals the following time breakdown across the 8 sequential activities:

Calculations:

• Total Lead Time (PLT): $0.5 + 32.0 + 2.5 + 24.0 + 1.0 + 16.0 + 1.5 + 2.5 = \mathbf{80.0\text{ hours}}$
• Total Value-Added Time (VAT): Step 3 (2.5 hrs) + Step 7 (1.5 hrs) = $\mathbf{4.0\text{ hours}}$
• Total BNVA Time: Step 1 (0.5 hrs) + Step 5 (1.0 hr) = $\mathbf{1.5\text{ hours}}$
• Total NVA Time: Step 2 (32.0 hrs) + Step 4 (24.0 hrs) + Step 6 (16.0 hrs) + Step 8 (2.5 hrs) = $\mathbf{74.5\text{ hours}}$

$\text{PCE} = \left( \frac{4.0\text{ hours}}{80.0\text{ hours}} \right) \times 100\% = 0.05 \times 100\% = \mathbf{5.0\%}$

Interpretation: Out of 80 hours of total turnaround time, only 4.0 hours (5.0%) represent genuine value creation. Over 93% of the time is pure waste ($74.5 / 80 = 93.1%$). An inexperienced manager might push analysts to "underwrite faster" during Step 3, but even if analysts cut underwriting time in half (saving 1.25 hours), total lead time only drops from 80.0 to 78.75 hours. The real breakthrough lies in targeting the 72 hours of queue time in Steps 2, 4, and 6.

---

Rules for Flowcharting the Real "As-Is" Current State

The most destructive mistake a Green Belt can make during process mapping is documenting the idealized process rather than the actual process.

The Three Versions of Every Process

1. What Management Thinks Happens: The clean, optimized procedure documented in corporate policy manuals and executive slide decks.
2. What Is Supposed to Happen: The formal Standard Operating Procedure (SOP) written by industrial engineers three years ago.
3. What Actually Happens: The messy, improvisational reality occurring on the floor, complete with workarounds, tribal knowledge, and undocumented fixes.

Core Mapping Mandates

• Walk the Gemba: Never draw a process map in a conference room from memory. The Green Belt and team must walk the physical floor (the Gemba) and observe the process in real time.
• Involve Front-Line Operators: Front-line workers who execute the work daily must construct and validate the map. Management or engineering assumptions are frequently incorrect.
• Expose the "Hidden Factory": The hidden factory consists of all the off-book, undocumented rework, manual error-correction, second-checking, and private spreadsheet tracking employees do to compensate for a defective system. If operators spend 30 minutes every morning re-formatting data in Excel, that activity must be on the map!
• Never Map the "To-Be" State in Define: The Define phase is strictly about understanding and bounding the current "As-Is" state. Designing the "To-Be" future state takes place in the Improve phase after root causes have been statistically verified in Analyze.

---

Critical Exam Traps & Conceptual Distinctions

• Trap 1: The Inspection Fallacy: Believing that quality inspection is Value-Added because "it protects the customer from receiving defects." Inspection does not transform the product; it merely checks whether an earlier step failed. Inspection is Non-Value-Added (pure waste) or at best Business Non-Value-Added if mandated by safety regulations. Quality must be built into the process, not inspected in.
• Trap 2: The "Boss Ordered It" Fallacy: Assuming an activity is Value-Added because an executive, manager, or department head mandated it. Internal corporate politics or management preferences do not define value—only the ultimate paying customer defines value.
• Trap 3: The Rework Illusion: Believing that repairing a broken part or correcting a flawed loan file is Value-Added because "without rework, the customer cannot get the product." Rework directly violates criterion 3 (Done Right the First Time). It is 100% pure waste (Muda).
• Trap 4: Confusing Activity with Value: Equating high labor effort, complex mathematical calculations, or specialized skills with value creation. If the customer does not care about or benefit from that effort, it is non-value-added.