11.3 Implementation Planning & Change Management (ADKAR)

11.3 Implementation Planning & Change Management (ADKAR)

Quick Summary: A technically flawless solution validated in a pilot study will fail during enterprise rollout if the organization neglects the operational logistics of implementation planning and the human dynamics of organizational change. Research across industrial engineering and management science confirms that up to 70% of organizational change initiatives fail not due to technical or statistical flaws, but due to unaddressed employee resistance and cultural friction. To achieve sustainable transformation, Six Sigma Green Belts employ structured project execution tools—the Work Breakdown Structure (WBS), Critical Path Gantt Charts, and RACI Accountability Matrices—paired with individual and organizational change models: the Prosci ADKAR Model, John Kotter's 8-Step Model, and Kurt Lewin's Change Framework.

---

The Architecture of Full-Scale Implementation Planning

Transitioning from a bounded pilot study to full-scale enterprise rollout introduces exponential operational complexity. While a pilot involves a single cooperative cell or shift, enterprise implementation impacts multiple shifts, disparate geographic facilities, diverse management cultures, and shared enterprise IT infrastructure.

                  The Implementation Architecture

   PILOT SUCCESS ────▶ WORK BREAKDOWN ────▶ CRITICAL PATH ────▶ RACI MATRIX
   Verified on Y       STRUCTURE (WBS)      GANTT CHART         ACCOUNTABILITY
   & De-risked         Decomposes tasks     Maps dependencies   Single 'A' per
                       down to work pkgs    & float/slack       activity
                                                                    │
      ┌─────────────────────────────────────────────────────────────┘
      ▼
   CHANGE MANAGEMENT DUAL-ENGINE
   ┌───────────────────────────────────┬───────────────────────────────────┐
   │ ORGANIZATIONAL MOVEMENT (KOTTER)  │ INDIVIDUAL PSYCHOLOGY (ADKAR)     │
   │ • Establish Urgency               │ • Awareness (Why change?)         │
   │ • Build Guiding Coalition         │ • Desire (What's in it for me?)   │
   │ • Empower Broad-Based Action      │ • Knowledge (Training / SOPs)     │
   │ • Anchor in Culture               │ • Ability (Hands-on coaching)     │
   │                                   │ • Reinforcement (KPI audits)      │
   └───────────────────────────────────┴───────────────────────────────────┘

An effective implementation plan must answer five foundational operational questions:

1. What specific activities are required? (Defined by the Work Breakdown Structure)
2. In what sequence must they occur, and where is the schedule risk? (Mapped via Critical Path Gantt Charts)
3. Who holds decision authority and task execution? (Governed by the RACI Matrix)
4. How will human stakeholders be prepared and supported? (Driven by the ADKAR Model)
5. How will operational readiness be verified prior to Go-Live? (Audited via Competency Matrices)

---

Work Breakdown Structure (WBS) & Project Scheduling

The Work Breakdown Structure (WBS) is a hierarchical decomposition of the total scope of work required to implement the improvement solution. In Six Sigma, the WBS translates abstract recommendations into discrete, assignable Work Packages.

                   Hierarchical WBS Decomposition

                     1.0 PACKAGING LINE IMPROVEMENT
                                    │
         ┌──────────────────────────┴──────────────────────────┐
         ▼                                                     ▼
   1.1 TOOLING & HARDWARE                                1.2 OPERATIONAL READINESS
   ┌─────┴────────────────────┐                          ┌─────┴────────────────────┐
   ▼                          ▼                          ▼                          ▼
1.1.1 Fabricate            1.1.2 Install              1.2.1 Draft &            1.2.2 Deliver
Locating Pins              Vision Sensor              Approve SOPs             Operator Training
(Work Package)             (Work Package)             (Work Package)           (Work Package)

The 100% Rule of WBS

A foundational project management rule dictates that the WBS must encompass 100% of the work defined by the project scope and capture all deliverables—including internal Six Sigma management deliverables (e.g., tollgate binders, control plan drafting, and sign-offs). The sum of the work at child levels must equal exactly 100% of the work at the parent level.

Critical Path Method (CPM) & Gantt Charts

Once work packages are decomposed, the Green Belt sequences them into a chronological Gantt Chart, identifying task dependencies and computing the Critical Path:

• Critical Path: The longest continuous sequence of dependent activities through the project network that determines the earliest possible project completion date. Activities on the critical path possess zero float (slack); a one-day delay on any critical path task delays the entire enterprise rollout by one day.
• Float (Slack Time): The amount of time an activity can be delayed without delaying the overall project completion date: $\text{Total Float} = \text{Late Start (LS)} - \text{Early Start (ES)} = \text{Late Finish (LF)} - \text{Early Finish (EF)}$

Managing float allows the project leader to dynamically shift engineering and training resources from non-critical tasks to critical path bottlenecks.

---

Responsibility Assignment: The RACI Matrix

Role ambiguity is a primary catalyst of project breakdown during implementation. When tasks stall, managers often discover that multiple individuals assumed someone else was responsible. To establish unambiguous operational governance, Six Sigma teams construct a RACI Matrix:

                           The RACI Definitions

  R ─── RESPONSIBLE  ──▶ The 'Doer': Person who completes the physical task
  A ─── ACCOUNTABLE  ──▶ The 'Owner': Person with ultimate veto/decision authority
  C ─── CONSULTED    ──▶ The 'Expert': Two-way communication; provides key input
  I ─── INFORMED     ──▶ The 'Stakeholder': One-way update; kept notified of status

Worked Example: RACI Implementation Matrix for a Vision Inspection Rollout

Notice that each activity has exactly one Accountable (A) leader, ensuring clear decision ownership.

---

The Human Psychology of Resistance to Change

Technical professionals often operate under the naive assumption that because a solution is statistically validated and mathematically superior, employees will welcome it enthusiastically. In reality, human beings do not resist technical solutions—they resist the loss of control, familiarity, and competence that change brings.

                     The Four Root Causes of Resistance

   FEAR OF JOB LOSS               LOSS OF AUTONOMY               COMPETENCE ANXIETY             COMFORT WITH HABIT
  ┌─────────────────────┐       ┌─────────────────────┐       ┌─────────────────────┐       ┌─────────────────────┐
  │ 'Will automation    │       │ 'Standard work feels│       │ 'I am an expert at  │       │ 'We have always     │
  │ eliminate my shift  │       │ like micromanagement│       │ legacy software;    │       │ done it this way;   │
  │ or reduce overtime?'│       │ and surveillance.'  │       │ will I look foolish?'│      │ why fix it now?'    │
  └─────────────────────┘       └─────────────────────┘       └─────────────────────┘       └─────────────────────┘

1. Fear of Obsolescence or Job Elimination: Frontline operators fear that cycle-time reductions or automation will eliminate their jobs or slash overtime pay. Countermeasure: Leadership must provide upfront guarantees that productivity gains will lead to redeployment and upskilling, not layoffs.
2. Loss of Autonomy and Status: Craftsmen and senior operators often perceive Standard Work as an insulting reduction of their personal craftsmanship into robotic, repetitive tasks. Countermeasure: Involve senior operators directly in drafting the standard work instructions.
3. Competence Anxiety (Fear of Looking Incompetent): Workers who are masters of legacy mechanical systems feel intense anxiety when confronted with touchscreens, PLCs, or optical sensors. Countermeasure: Safe, low-stakes training environments with patient peer coaching.
4. Inertia and Cynicism from Past Failed Initiatives: Employees have witnessed corporate "programs of the month" fade away. Countermeasure: Consistent executive sponsorship, quick-win celebration, and visible leadership presence at the Gemba.

---

The Prosci ADKAR Model for Individual Change

While traditional project management focuses on technical installation, change management focuses on human adoption. Developed by Jeff Hiatt after studying change patterns across hundreds of organizations, the Prosci ADKAR Model establishes that organizational change succeeds only when each individual employee successfully traverses five sequential psychological milestones:

                     The Prosci ADKAR Progression

      A ─── AWARENESS       ──▶ Understanding the business need for change
      D ─── DESIRE          ──▶ Personal choice to support & engage in change
      K ─── KNOWLEDGE       ──▶ Training on how to execute the new standard
      A ─── ABILITY         ──▶ Demonstrated proficiency & physical execution
      R ─── REINFORCEMENT   ──▶ Sustaining new behaviors; preventing backsliding

The Five Dimensions of ADKAR

1. Awareness (Of the Need for Change)

• Core Question: "Why do we need to change, why now, and what happens if we stay the same?"
• Workers cannot support a solution if they believe the current process is operating adequately. The Green Belt must share compelling data: rising customer defect complaints, lost market share, or escalating scrap costs that threaten plant competitiveness.

2. Desire (To Support and Participate)

• Core Question: "What's In It For Me?" (WIIFM)
• Awareness of a problem does not automatically generate a desire to fix it. Desire represents an individual's personal decision to engage. It is shaped by addressing personal concerns, demonstrating how the solution eliminates daily frustrations, and aligning incentives.

3. Knowledge (Of How to Change)

• Core Question: "What exact procedural steps, operating parameters, and software commands must I know?"
• Delivered through structured education: classroom instruction, video modules, and Visual Standard Operating Procedures. Knowledge explains what to do and how to do it.

4. Ability (To Implement Required Skills and Behaviors)

• Core Question: "Can I demonstrate consistent, high-quality execution under real-world takt time?"
• Critical Distinction: Knowledge $\ne$ Ability. Reading an SOP binder or passing a written multiple-choice test (Knowledge) does not mean an operator can execute the procedure at line speed without errors (Ability). Ability requires hands-on physical practice, simulation, ergonomic tuning, and immediate coaching.

5. Reinforcement (To Sustain the Change)

• Core Question: "How do we prevent employees from slipping back into comfortable legacy habits?"
• Sustained through positive recognition, visual performance dashboards, supervisor Layered Process Audits (LPAs), and aligning performance reviews with adherence to standard work.

Diagnosing the "Barrier Point" in ADKAR

The ADKAR model is strictly sequential. If an individual stalls on one dimension, attempting to push downstream dimensions is futile:

                 ADKAR Barrier Point Diagnostic Framework

   EMPLOYEE PROFILE: Awareness=5 | Desire=1 | Knowledge=4 | Ability=3 | Reinforcement=4
                                       │
                                       ▼
                        BARRIER POINT: DESIRE (Score < 3)
   MANAGEMENT MISTAKE: Sending the employee to more classroom training (Knowledge).
   CORRECT ACTION:     Engage in 1-on-1 coaching to uncover personal objections, fears,
                       and misalignment of incentives (WIIFM).

• When an employee has a Desire barrier, sending them to more training (Knowledge) generates resentment.
• When an employee has an Ability barrier, providing more lectures does not help; they require hands-on physical practice with a qualified mentor.

---

Comparative Change Models: ADKAR vs. Kotter vs. Lewin

Six Sigma Green Belts integrate three complementary change models to address both individual and organizational transformation:

                    Synthesis of Leading Change Models

      KURT LEWIN                    JOHN KOTTER                       PROSCI ADKAR
   (Systemic State)           (Enterprise Acceleration)         (Individual Psychological)
  ┌─────────────────┐       ┌─────────────────────────────┐       ┌─────────────────┐
  │                 │       │ 1. Establish Urgency        │       │                 │
  │ 1. UNFREEZE     │ ────▶ │ 2. Build Guiding Coalition  │ ────▶ │ 1. AWARENESS    │
  │                 │       │ 3. Form Strategic Vision    │       │ 2. DESIRE       │
  │                 │       │ 4. Enlist Volunteer Army    │       │                 │
  ├─────────────────┤       ├─────────────────────────────┤       ├─────────────────┤
  │                 │       │ 5. Enable Action (Roadblocks│       │ 3. KNOWLEDGE    │
  │ 2. CHANGE       │ ────▶ │ 6. Generate Short-Term Wins │ ────▶ │ 4. ABILITY      │
  │                 │       │ 7. Sustain Acceleration     │       │                 │
  ├─────────────────┤       ├─────────────────────────────┤       ├─────────────────┤
  │ 3. REFREEZE     │ ────▶ │ 8. Institute Change         │ ────▶ │ 5. REINFORCEMENT│
  └─────────────────┘       └─────────────────────────────┘       └─────────────────┘

---

Operational Readiness & Workforce Training Plans

A solution cannot be deployed enterprise-wide until the workforce demonstrates verifiable operational competence. Standard training approaches (such as unstructured peer "shadowing" or circulating a memo) guarantee high defect rates.

The TWI Job Instruction Framework

Originating in World War II and perfected within Lean manufacturing, the Training Within Industry (TWI) Job Instruction framework provides a four-step pedagogical protocol:

1. Step 1: Prepare the Learner: Put the operator at ease, state the job, ascertain current knowledge, and generate interest/Desire.
2. Step 2: Present the Operation: Tell, show, and illustrate one important step at a time. Emphasize Key Points (safety warnings, quality touchpoints, physical feel) and explain the reasons why.
3. Step 3: Try Out Performance: Have the learner do the job; correct errors immediately. Have the learner repeat the job while explaining the steps, key points, and reasons until mastery is evident.
4. Step 4: Follow Up: Put the operator on their own; designate whom they go to for help; check progress frequently; taper off coaching.

The ILUO Competency Tracking Matrix

Organizations manage operational readiness using a visual ILUO Matrix displayed at the workstation:

• 'I' (Trainee): Understands theoretical principles and safety rules; cannot operate independently.
• 'L' (Supervised Learner): Executes task under direct mentor observation.
• 'U' (Autonomous Operator): Operates independently to standard work and takt time with zero defects.
• 'O' (Certified Master / Trainer): Deep procedural mastery; capable of auditing and training others.

                      The ILUO Competency Progression

        'I'                   'L'                   'U'                   'O'
     ┌─────────┐           ┌─────────┐           ┌─────────┐           ┌─────────┐
     │    │    │           │    │    │           │  │   │  │           │  ┌───┐  │
     │    │    │           │    │    │           │  │   │  │           │  │   │  │
     │    │    │           │    └─── │           │  └───┘  │           │  └───┘  │
     └─────────┘           └─────────┘           └─────────┘           └─────────┘
      Trainee:              Capable:             Independent:           Teacher:
     Understands           Executes with         Operates to takt      Master trainer;
     principles            assistance            consistently          audits process

---

Critical Exam Traps to Avoid

• Trap 1: Multiple 'A's in a RACI Matrix — An exam question showing two individuals assigned 'A' (Accountable) for a single activity represents a severe governance flaw. Exactly one person must be Accountable.
• Trap 2: Confusing Knowledge with Ability in ADKAR — Providing an employee with an SOP binder or classroom lecture builds Knowledge. Demonstrating execution at production takt time requires Ability, developed through hands-on coaching and practice.
• Trap 3: Misdiagnosing an ADKAR Barrier Point — If an employee understands how to do a job (Knowledge = 5) but refuses to do it because they fear losing overtime, the barrier point is Desire, not Knowledge. Additional training will only increase resistance.
• Trap 4: Treating Change Management as a Post-Implementation Activity — Effective change management starts in the Define phase by establishing urgency and building a coalition. Leaving change management until after the solution is engineered guarantees active pushback.