Comprehensive Study Notes: Lean Six Sigma (LSS)

UNIT 1 Overview of Six Sigma

What is Six Sigma?

Six Sigma is a quality management approach and statistical methodology
used to improve business processes by minimizing variability and defects. It
focuses on delivering products and services that meet or exceed customer
expectations by ensuring processes are as close to perfection as possible.
The name "Six Sigma" refers to a statistical term. In statistics, sigma (σ)
represents standard deviation, which measures variability in a process. A
process that is operating at Six Sigma quality produces only 3.4 defects per
million opportunities (DPMO).

Objectives of Six Sigma:

• To eliminate defects and errors in processes.

• To reduce variability and improve consistency.
• To enhance customer satisfaction by delivering quality.
• To increase productivity and reduce costs.
• To create a culture of continuous improvement.

Key Concepts:

• Defect: Anything that doesn’t meet customer expectations.

• Process: Any repetitive task or operation performed to deliver a
product or service.
• Variation: Inconsistency in process outputs that leads to defects.

Key Metrics in Six Sigma:

1. Defects per Unit (DPU)

2. Defects per Million Opportunities (DPMO)
3. Sigma Level – A measure of process capability.
 Example:
Suppose a mobile phone manufacturing unit produces 1,000 phones in a day.
If 5 phones are returned due to battery issues, the defect rate is 5/1000 =
0.5%. Six Sigma aims to reduce such defects significantly by identifying and
eliminating root causes.

2⃣ History and Timeline of Lean and Six Sigma

Origin of Lean:
Lean originated from the Toyota Production System (TPS) in post-World War II
Japan. It was developed by Taiichi Ohno and Eiji Toyoda to optimize
production, minimize waste, and deliver maximum value to customers with
fewer resources.

Origin of Six Sigma:

Six Sigma was introduced by Bill Smith at Motorola in 1986. Motorola aimed
to improve product quality and reduce manufacturing defects. The concept
was later adopted and popularized by General Electric (GE) under Jack Welch
in the 1990s.

Timeline Summary:

Year Event

1940s–1950s Toyota develops Lean concepts through TPS

1986 Motorola develops Six Sigma methodology

1995 GE implements Six Sigma company-wide

2000s Lean and Six Sigma begin to merge (LSS)

2010–present LSS is used across all industries (healthcare, finance, retail, IT)
3⃣ Significance of Lean Six Sigma in Digital Transformation

What is Digital Transformation?

Digital Transformation (DX) refers to integrating digital technologies into all

business areas, resulting in fundamental changes in operations and value
delivery. It involves tools like:
• Artificial Intelligence (AI)
• Machine Learning (ML)
• Internet of Things (IoT)
• Cloud Computing
• Automation and Robotics
• Big Data Analytics

How LSS supports DX:

1. Improves Process Efficiency Before Automation

You can’t automate a bad process. LSS helps first fix and streamline the
process, and then digital tools are applied.

Example: A bank uses LSS to reduce customer service delays before

applying chatbot automation.
2. Data-Driven Decision Making
Six Sigma emphasizes making decisions based on quantitative data. This
aligns with digital transformation, where big data is a key resource.

Example: A logistics firm uses Six Sigma to analyze delivery delays and
machine learning to predict future bottlenecks.
3. Eliminates Waste with Technology
Lean principles like waste elimination can be enhanced using digital tools. IoT
sensors, dashboards, and real-time monitoring help detect and reduce waste
instantly.
 Example: In smart manufacturing, Lean helps map wasteful steps and
sensors automate their removal.
4. Enhances Customer Experience
LSS ensures digital transformation efforts stay aligned with customer needs.
The “Voice of Customer (VoC)” tool is critical here.

Example: E-commerce companies use LSS to redesign mobile apps based

on user feedback and behavior.
5. Sustainability
Lean emphasizes minimal resource use. With digital tools, businesses can
track energy usage, emissions, and optimize resources—supporting
sustainability goals.

4⃣ Industry Success Story – General Electric (GE)

Background:

In 1995, GE adopted Six Sigma across all its businesses. Jack Welch, the CEO,
made Six Sigma training mandatory and promoted it as a core part of GE’s
culture.

Implementation:

• GE trained thousands of employees at all levels:

o Green Belts (project-level)
o Black Belts (full-time quality experts)
o Master Black Belts (mentors/trainers)
• Projects used the DMAIC framework.
• Six Sigma was used in finance, HR, engineering, customer service, and
more.

Results:
• Saved $10–12 billion over 5 years.
 • Increased productivity, efficiency, and market competitiveness.
• Enhanced customer loyalty through quality and consistency.

Healthcare Example:

A hospital applied LSS to reduce ER wait times from 90 minutes to 25 minutes

by analyzing patient flow and reallocating staff.

Retail Example:
Amazon uses Lean Six Sigma for warehouse management—optimizing shelf
placement, packaging lines, and order fulfillment to deliver faster.

5⃣ Overview of DMAIC Framework

The DMAIC framework is the core problem-solving methodology used in Six
Sigma projects.

Phase Description Tools & Techniques

D– Identify the problem, define Project Charter, SIPOC

Define the goal, and understand diagram, Voice of Customer
customer requirements (VoC)

M– Collect data on the current Process Mapping, Data

Measure process to identify the Collection Plan, Control
baseline performance Charts

A– Identify root causes of the Fishbone Diagram, Pareto

Analyze problem Chart, 5 Whys
I– Develop and implement Brainstorming, Pilot Testing,
Improve solutions to eliminate root DOE
causes

C– Maintain improvements and Control Plan, Standard

Control prevent regression Operating Procedures (SOPs),
Monitoring Systems
 Real-Life DMAIC Example – Restaurant Service Delay:
DMAIC Example Implementation
Phase

Define Customers complain of long wait times during lunch rush.

Target: reduce to under 10 minutes.

Measure Measure actual wait times over a week. Current average =

18 minutes.

Analyze Root cause: order queue bottlenecks due to one cashier and
slow kitchen prep.

Improve Hire second cashier, pre-prepare popular lunch items, and

digitize order entry.

Control Set up weekly monitoring of service time and customer

feedback.

6⃣ Exercises Simulation Part 1: Overview

What is a Simulation?
A simulation in LSS is a practical, real-world case scenario where learners
apply LSS concepts to solve a business problem. It helps build understanding
and skills in a controlled environment.

Learning Objectives:
• Apply the DMAIC framework to a real problem.
• Use LSS tools like flow charts, Pareto charts, and cause-effect diagrams.
• Understand team roles in LSS (e.g., Green Belt, Sponsor, Champion).
• Practice decision-making based on data.

Example Simulation Scenario:

Scenario: A clothing retailer experiences delayed order shipments and rising
customer complaints.
Simulation Approach Using DMAIC:
• Define: Identify that delivery time exceeds promised time by 3 days.
• Measure: Collect data on warehouse processing time, shipping errors,
and order volumes.
• Analyze: Discover bottlenecks in the packaging department and
inventory mismatches.
• Improve: Streamline the packing station and implement barcode-based
inventory tracking.
• Control: Track daily delivery timelines and automate reorder levels for
inventory.

Conclusion

Lean Six Sigma is a powerful blend of two methodologies:

• Lean focuses on speed, simplicity, and eliminating waste.
• Six Sigma emphasizes precision, data, and reducing variability.
Together, they create a robust system for driving operational excellence,
improving quality, and enabling businesses to adapt to the digital age.
Understanding and practicing the DMAIC framework through real-world
problems and simulations helps develop strong analytical, decision-making,
and leadership skills.
Unit 2 Lean Six Sigma – Define Phase (Comprehensive Notes)

1. What is the Define Phase?

The Define Phase is the first stage of the DMAIC (Define-Measure-Analyze-

Improve-Control) methodology used in Lean Six Sigma. It sets the foundation
for the entire project by defining the problem, setting the goals, and
establishing the scope and timeline.

Objective of the Define Phase:

• Understand and articulate the business problem

• Align the project with customer needs and organizational goals
• Create a Project Charter
• Identify key stakeholders
• Capture the Voice of the Customer (VOC) and Voice of the Business
(VOB)

2. Stakeholder Map

Who is a Stakeholder?
A stakeholder is anyone who has an interest or is affected by the project. This
includes:
• Customers
• Employees
• Managers
• Vendors
• Regulatory bodies
• Shareholders

Purpose of a Stakeholder Map:

A Stakeholder Map helps identify:
• Who is affected by the project
• Their level of influence
• Their level of interest
• How to communicate with them effectively

Power vs Interest Grid:

This grid classifies stakeholders into four categories:

Stakeholder Type Description Example

High Power, High Must be managed closely CEO, Project

Interest Sponsor

High Power, Low Keep satisfied Finance Director

Interest

Low Power, High Keep informed Frontline staff

Interest

Low Power, Low Interest Monitor with minimal Admin staff

effort

Example:

In a project to improve online customer service:

• High Power, High Interest: Operations Manager
• Low Power, High Interest: Call center agents
• High Power, Low Interest: Legal Department
• Low Power, Low Interest: IT maintenance team

3. Stakeholder Requirement Assessment

Purpose:
To determine the expectations, concerns, and requirements of each
stakeholder. This ensures the project meets the real needs of the people it
affects.

🛠 Tools Used:
• Interviews
• Questionnaires
• Focus groups
• Brainstorming sessions

Output:
A list of stakeholder-specific requirements that must be considered in the
project plan.

Example:
In a hospital project to reduce patient wait time:
• Patients want faster service and comfort.
• Doctors want optimized schedules.
• Admin wants cost-effective changes.
4. Customized Communication Plan – Explained with Example

What is it?
A plan that outlines how you will communicate with each stakeholder
throughout the project.

Elements of a Communication Plan:

Element Explanation Example

Stakeholder Who needs updates Operations Head

Message What info is needed Weekly progress

Frequency How often Every Friday

Channel How you’ll communicate Email, Slack

Owner Who is responsible Project Manager

Real-Life Example (University):

If you are improving the admission process:

• Send weekly updates to the Dean via email
• Conduct bi-weekly calls with the IT team
• Provide monthly reports to the finance department
This ensures everyone is aligned and avoids last-minute surprises.

5. Capturing VOC and VOB – Explained Thoroughly

VOC (Voice of the Customer):

What customers are saying—their needs, wants, expectations, and
complaints.

VOB (Voice of the Business):

What the organization needs—like efficiency, profit, or compliance.

Real-Life Example (Banking):

You’re improving ATM services:

• VOC: “ATM should not be out of cash,” “It should work 24x7”
• VOB: “Reduce maintenance cost,” “Ensure security compliance”
The key is to balance VOC and VOB while designing your solution.

6. VOC Analysis Tools – Detailed with Examples

6.1 Affinity Diagram
Used when you have a lot of feedback and want to find themes.

Example:

Feedback from customers:

• “The website crashes often.”
• “Too many steps at checkout.”
• “Difficult to find support.”

➡ Group into category: “Poor User Experience”

This helps identify the real problems.

6.2 Kano Model

Helps prioritize features based on how they affect customer satisfaction.

Category Description Example

Must-Have Basic need Mobile app loads properly

Performance More is better Faster delivery time

Delighter Unexpected feature Free gift with order

Indifferent No effect Logo color

Reverse Negative effect Too many push notifications

This helps in prioritizing improvements.

7. Project Charter – Step-by-Step with Example

What is it?
A Project Charter is a formal document that defines:
• The problem
• The goal
 • Scope
• Timeline
• Team
• Business value

Example: Reducing Late Deliveries in E-commerce

Element Content

Title Reduce Late Deliveries

Problem 30% of orders are delivered late in Mumbai

Goal Reduce late deliveries to under 5% in 3 months

Scope Only Mumbai deliveries

Out of Scope International and COD orders

Team Logistics Manager, Data Analyst

Timeline May–July

Metrics Reduce from 30% → 5%

Business Case Improve customer satisfaction, reduce refunds

This document is shared with management for approval.

8. Reflection-Based Peer Discussion – Detailed

What is it?

Team members come together after completing the Define phase to:
• Share insights
• Highlight what worked or didn’t
• Learn from others’ experiences

Questions Discussed:
• Did we define the problem well?
 • Did we involve the right stakeholders?
• Did we understand the VOC and VOB clearly?
• Were there any conflicting goals?
These discussions improve team learning and collaboration.

9. Simulation Part 2: Create a Project Charter – Practical Example

Let’s say you’re in a simulated project to fix student complaints at a
university.

Scenario:

• 40% of students complain about delay in receiving marksheets.

Steps:

1. Identify stakeholders: Students, Admin, Exam Cell

2. Capture VOC: “I didn’t get my marksheet,” “Delay in updates”
3. Capture VOB: “Improve student satisfaction score”
4. Analyze VOC: Group issues under “Process Delay”
5. Create a Project Charter:

Element Example

Title Reduce Marksheet Delays

Problem 40% students get marksheets 2 weeks late

Goal Bring this to <5% in 3 months

Scope Final-year students

Team Registrar, IT, Faculty

Timeline June–August

Benefit Better student feedback, faster compliance

Unit 3

MEASURE PHASE: In-depth Detailed Explanation

The Measure Phase is the second phase in the DMAIC framework (Define,
Measure, Analyze, Improve, Control) in Lean Six Sigma. This phase is focused
on understanding the current state of the process, collecting data, and setting
a baseline to measure improvements against.

1. Process Capability – Variable Data

What is Process Capability?

Process capability refers to the ability of a process to produce products or

services that meet customer specifications consistently. It indicates whether
the process is in control and can produce goods or services within the defined
specification limits (upper and lower).
Variable Data is continuous, measurable data. It includes metrics like weight,
height, temperature, pressure, etc. This type of data is more detailed than
attribute data (which is categorical like "pass" or "fail") and allows for greater
analysis of process performance.

Key Concepts:
• Cp (Process Capability Index) measures the capability of a process,
assuming it is centered.
• Cpk (Process Capability Index with Centering Consideration) measures
the capability while accounting for how centered the process is within
the specification limits.

Cp and Cpk Formulae:

• Cp (Process Capability Index) is calculated as:

o USL = Upper Specification Limit

 o LSL = Lower Specification Limit
o σ = Standard Deviation
• Cpk (Process Capability Index with Centering Consideration) takes into
account the mean (μ) of the process and calculates the distance
between the mean and the closest specification limit:

A higher Cp or Cpk value indicates a more capable process. For example, a Cp

or Cpk of 1.33 or higher is typically considered a good process performance.

Real-Life Example:
Let’s say you are working at a company that manufactures high-precision ball
bearings used in machinery. The diameter of the bearing needs to be within
50mm ± 0.5mm.

2. Introduction to the Analyze Phase

 What is the Analyze Phase?
The Analyze Phase follows the Measure Phase and is where you start
investigating the root causes of the problem. In this phase, data collected
during the Measure Phase is used to identify and validate potential causes of
variation or defects.

Key Concepts:
The goal in the Analyze Phase is to move from the current state (defined in
Measure) to the root causes of any problems:
• Fishbone Diagram (Ishikawa) is used to explore all potential causes of
problems.
• 5 Whys is a technique to drill down to the root cause by repeatedly
asking why.
• Hypothesis Testing is used to check assumptions or theories using data.

Real-Life Example:
In a clothing manufacturing company, if there are frequent defects in
stitching, the Analyze Phase could reveal that the root causes include:
• Operator error: Some workers are not trained properly.
• Inadequate machinery: The sewing machines frequently malfunction.
• Supply chain issues: Substandard fabric is causing stitching problems.
By identifying these root causes, the team can propose targeted
improvements.

3. Introduction to Data Visualization

What is Data Visualization?

Data Visualization is the graphical representation of data that helps
stakeholders quickly understand complex data sets. It transforms raw data
into charts, graphs, and plots that are easier to interpret, enabling better
decision-making.
 Why is Data Visualization Important?
Effective data visualization enables the identification of patterns, trends, and
outliers in the data. It helps in:
• Spotting trends over time (e.g., sales performance or defect rates).
• Identifying bottlenecks and variability in processes.
• Communicating insights clearly to stakeholders.

Types of Data Visualization:

• Histograms: Used to understand the distribution of data points (e.g.,
variation in defect rates over time).
• Control Charts: Used for tracking process stability over time.
• Box Plots: Useful for showing data spread and detecting outliers.
• Pareto Charts: Based on the 80/20 rule, showing which causes are
responsible for the most significant problems.

Real-Life Example:
In a restaurant, a manager might use a Pareto Chart to visualize customer
complaints. If 80% of complaints are about slow service and the other 20%
are about incorrect orders, the focus should be on speeding up service rather
than changing the menu.

4. Identifying VA (Value-Added) and NVA (Non-Value Added) Activities

What is Value-Added (VA)?

Value-Added (VA) activities are those that:

1. Transform the product or service in a way that adds value.
2. The customer is willing to pay for these activities.

What is Non-Value Added (NVA)?

Non-Value Added (NVA) activities are those that:

 1. Do not transform the product or service in a way that the customer
would pay for.
2. Typically represent waste and should be eliminated or minimized.

Why is Identifying VA and NVA Important?

The goal in Lean Six Sigma is to maximize value-added activities and minimize
non-value-added activities to increase efficiency and reduce waste.

Real-Life Example:

In a call center:
• VA activity: Resolving a customer query in the first call.
• NVA activity: Putting the customer on hold while searching for
information, as this delays the resolution and doesn’t add value.

5. Value Stream Mapping (VSM)

What is Value Stream Mapping?

Value Stream Mapping (VSM) is a tool used to visually represent the flow of
materials and information required to deliver a product or service. It maps
out the entire process from start to finish, highlighting both value-added (VA)
and non-value-added (NVA) activities.

Why is Value Stream Mapping Important?

VSM helps identify inefficiencies in the process, such as bottlenecks, delays,
and waste. It provides a clear visualization of where improvement
opportunities exist.

Real-Life Example:

In a software development process, VSM can show how information flows:

1. Customer request → Requirements analysis → Design → Development
→ Testing → Deployment
The VSM can highlight areas where delays occur, such as waiting for feedback
during the testing phase.

6. Minitab Exercises – Using Minitab for Data Analysis

6.1 Test of Normality

A Test of Normality checks if the data follows a normal distribution (bell
curve). Many statistical methods in Six Sigma assume data is normal, so this
test is essential for determining the type of analysis to use.
In Minitab, go to Stat → Basic Statistics → Normality Test. It provides a p-
value, which tells you if your data can be assumed to be normally distributed.

Real-Life Example:
For a production line, you might want to test if the time between machine
breakdowns follows a normal distribution. If it does, you can proceed with
parametric tests; otherwise, you may need non-parametric methods.

6.2 Histograms
A Histogram helps visualize the distribution of data. It divides data into bins
or intervals and displays the frequency of data points in each bin.

Real-Life Example:
For a delivery company, you might create a histogram of delivery times to
understand the spread of delivery durations and identify whether most
deliveries occur within the targeted time frame (e.g., 2-3 hours).

6.3 Gage R&R (Repeatability and Reproducibility)

Gage R&R is a method to assess the reliability of your measurement system
by checking:
• Repeatability: Whether the same person gets consistent results when
measuring the same part.
 • Reproducibility: Whether different people get consistent results when
measuring the same part.
In Minitab, go to Stat → Quality Tools → Gage Study → Gage R&R to perform
the analysis.

Real-Life Example:

If a team is measuring the thickness of steel plates, Gage R&R can check if the
measurement system is accurate and consistent. Variations in measurements
may indicate problems with the instrument or the measurement process.

7. Simulation Part 3 – DPMO / Cp-Cpk

What is DPMO?
DPMO (Defects Per Million Opportunities) is a metric used to assess the
defect rate in a process, especially when there are multiple defect
opportunities per unit.
The formula for calculating DPMO is:

Real-Life Example:
In a quality control process, if a production line produces 10,000 units, and
there are 100 defects (where each unit can have 5 potential defects), the
DPMO can be calculated.

Cp and Cpk in Simulation:

Using tools like Minitab, you can simulate Cp and Cpk values to assess how
stable and capable your process is and to plan for necessary improvements.

Summary of Key Concepts from the Measure Phase:

 Concept Purpose Tools/Methods

Process Measure if a process meets Cp, Cpk

Capability specifications

Data Visualize data patterns and Histograms, Box Plots,

Visualization trends Control Charts

VA and NVA Identify value-added and Value Stream Mapping

wasteful activities (VSM)

Gage R&R Ensure accuracy of Gage R&R (Minitab)

measurement system

DPMO Measure defects in the Formula, Simulation

process

Simulation Part 3: DPMO/Cp-Cpk

DPMO (Defects Per Million Opportunities)

DPMO is a critical metric used to measure the quality of a process in Six Sigma.
It calculates the number of defects in a process per one million opportunities
for defects, which helps evaluate the overall effectiveness of the process.
Formula for DPMO:

Where:
• Defects are the number of defects identified in the process.
• Units produced are the total number of items or outputs produced.
• Opportunities per unit refer to the possible points in each unit where a
defect could occur.

Purpose of DPMO:
 • DPMO helps assess how much variation or defects exist in a process
relative to the number of opportunities.
• It provides insight into process performance, where a lower DPMO
signifies higher process quality.

Real-Life Example:

Consider a smartphone manufacturer producing 100,000 units a month. Each

unit has three potential defect opportunities (screen, camera, battery issues).
If 500 defects are found across all the units, you can calculate the DPMO as
follows:

\
This means the manufacturer has 1,667 defects per million opportunities,
which can help them assess process quality and target improvements.

Cp and Cpk
Cp and Cpk are both process capability indices used to measure how well a
process is performing relative to its specification limits. These indices help
determine whether a process can meet customer specifications consistently.
1. Cp (Process Capability Index)
Cp measures the spread of the process relative to the specification limits,
assuming that the process is centered.
The formula for Cp is:
Where:
• USL: Upper Specification Limit
• LSL: Lower Specification Limit
• σ: Standard deviation of the process.
• μ: Process mean (average).

Real-Life Example:
Imagine a steel rod manufacturer with a target diameter of 50 mm and a
specification range of 49.5 mm to 50.5 mm. The process has a standard
deviation of 0.1 mm and a mean of

UNIT 4 Analyze Phase

The Analyze Phase in Six Sigma focuses on identifying the root causes of the
problems defined in the Define Phase. The goal is to analyze data collected in
the Measure Phase to uncover the underlying factors causing process defects
or inefficiencies. By doing so, you can make informed decisions to improve the
process in the next phases.

Objectives of the Analyze Phase:

1. Examine the data collected in the Measure Phase to identify variations
and causes of defects.
2. Use statistical and visualization tools to identify trends, correlations,
and patterns in the data.
3. Perform root cause analysis to identify the main causes contributing to
process inefficiencies or defects.
4. Test hypotheses related to the problems identified in the Define phase
using various statistical methods.
 Tools Used in the Analyze Phase

1. Cause & Effect Diagram (Fishbone Diagram)

A Cause and Effect Diagram (also called the Ishikawa diagram) is used to
visualize the potential causes of a problem and categorize them in a structured
manner. It looks like the bones of a fish, where the "spine" represents the
problem and the "bones" represent categories of potential causes.
Categories of Causes:
• Man: Human errors or lack of training.
• Machine: Equipment or machine malfunctions.
• Method: Process flaws or outdated procedures.
• Material: Issues with raw materials or supply chain.
• Measurement: Issues with data collection or measurement techniques.
• Environment: Environmental conditions such as temperature or
humidity.

Real-Life Example:
If a manufacturing company faces frequent defects in products, the Cause and
Effect Diagram could reveal:
• Man: Operators are not properly trained.
• Machine: Machines are outdated and require maintenance.
• Material: Suppliers provide inconsistent raw materials.
• Measurement: The measurement instruments are not calibrated
properly.

2. Pareto Chart (80/20 Rule)

A Pareto Chart is a bar graph that identifies and visualizes the most frequent
causes of problems. According to the Pareto Principle, 80% of the problems
are caused by 20% of the factors.
Steps:
1. Identify all possible problems or causes.
2. Count the frequency of each problem.
3. Create a bar chart showing the frequency of each issue, ordered from
highest to lowest.

Real-Life Example:

A restaurant might use a Pareto Chart to identify customer complaints:

• Slow service (40%)
• Order inaccuracies (25%)
• Rude staff (15%)
This analysis would help the restaurant focus on solving the slow service
problem first, as it contributes the most to customer dissatisfaction.

3. Control Impact Diagram

The Control Impact Diagram helps prioritize inputs (variables) in a process
based on their impact on the output (process performance). Inputs are
classified as:
• Critical to Quality (CTQ): Variables that must be controlled to meet
customer requirements.
• Non-CTQ: Variables that have little to no impact on the quality of the
output.

Real-Life Example:
In a packaging plant, the CTQ might be the temperature of the product, as it
directly affects quality. The Non-CTQ might be the color of the packaging,
which is less important to customers.

4. Principles of Lean
The principles of Lean are designed to minimize waste and maximize customer
value. Lean methodology aims to improve the flow of processes by eliminating
seven types of waste:
1. Overproduction: Producing more than is needed or before it is needed.
2. Waiting: Idle time spent waiting for materials, information, or
equipment.
3. Transport: Unnecessary movement of materials or products.
4. Extra Processing: Doing more work than necessary or over-complicating
the process.
5. Inventory: Holding excessive amounts of work-in-progress or finished
goods.
6. Motion: Excessive movement of workers or machines.
7. Defects: Errors or defects that require rework.

Real-Life Example:
A clothing manufacturer identifies that excessive waiting times are causing
delays in their production line. To reduce waste, they adjust the production
flow to minimize idle time, improving overall efficiency.

5. Test of Mean and Proportion

Test of Mean is used to compare the sample mean to a hypothesized
population mean, while the Test of Proportion compares sample proportions
to a hypothesized proportion.
These tests allow you to assess whether observed data significantly deviates
from a predefined standard.

Real-Life Example:

A company that produces light bulbs hypothesizes that the average lifespan of
a bulb should be 800 hours. Using a Test of Mean, the company tests the
sample to see if the average lifespan is statistically different from 800 hours.
 6. Correlation and Regression
• Correlation measures the strength and direction of a relationship
between two variables. A positive correlation means both variables
increase together, while a negative correlation means as one increases,
the other decreases.
• Regression is used to model the relationship between a dependent
variable and one or more independent variables.

Real-Life Example:

A company analyzing the relationship between advertising spending and sales

might find a positive correlation, suggesting that higher ad spending leads to
higher sales.

7. Introduction to AI and ML
AI (Artificial Intelligence) refers to systems that simulate human intelligence to
perform tasks like learning, reasoning, and problem-solving. Machine Learning
(ML) is a subset of AI that enables systems to learn from data and improve over
time.
• AI in Process Improvement: AI can be used to automate processes,
detect defects, or predict failures in real-time.
• ML in Process Optimization: ML models can analyze historical data to
predict outcomes and optimize process parameters.

Real-Life Example:
A manufacturing company uses AI-powered cameras to detect defects in real-
time on the assembly line. ML models analyze past defect data to predict and
prevent potential future defects.

Minitab Exercises – Cpk, Z-value, Pareto Diagram, Test of Means and

Proportions
 • Cpk in Minitab: Use Minitab to calculate Cpk for process capability
analysis by navigating to Stat → Quality Tools → Capability Analysis.
• Z-value in Minitab: Minitab can compute the Z-value to measure how
many standard deviations a point is from the mean.
• Pareto Diagram in Minitab: To visualize the 80/20 rule, go to Graph →
Pareto Chart in Minitab.
• Test of Means and Proportions in Minitab: Perform hypothesis tests on
the sample data by selecting Stat → Basic Statistics in Minitab.

Simulation Part 4: Root Cause Analysis

Root Cause Analysis (RCA) is a systematic approach to identifying the
underlying causes of problems instead of just addressing their symptoms. Tools
such as the Fishbone Diagram, 5 Whys, and Failure Mode and Effect Analysis
(FMEA) are commonly used in this process.

UNIT 5 Improve Phase

The Improve Phase in Lean Six Sigma is a critical step where the solutions to
the problems identified in the previous phases (Define, Measure, and Analyze)
are implemented. The goal is to find the most efficient, effective, and feasible
solutions to improve the process. This phase focuses on innovation, creativity,
and ensuring that improvements are sustainable. Let’s explore each of the key
concepts in detail:

Introduction to RPA (Robotic Process Automation)

Robotic Process Automation (RPA) is an emerging technology that allows

businesses to automate rule-based and repetitive tasks by using software
robots (bots). RPA mimics the exact steps performed by humans interacting
with systems and applications.
Identifying RPA Opportunities Based on Process Analysis:
• RPA is typically implemented in processes that require manual data
entry, form filling, or information retrieval from different systems.
• By analyzing current workflows, you can identify areas where RPA can
replace repetitive human tasks.
Example: A finance team might use RPA to automatically extract data from
invoices and enter it into accounting systems, saving time and reducing human
error.
Benefits of RPA:
• Increased Efficiency: RPA can complete tasks much faster than humans.
• Accuracy: Since RPA follows exact instructions, it minimizes errors caused
by human oversight.
• Cost Savings: Automating repetitive tasks reduces labor costs and
operational inefficiencies.
• Scalability: RPA can scale quickly to handle increased workloads without
the need to hire additional employees.

Introduction to Brainstorming Techniques

Brainstorming is a group creativity technique that encourages the free flow of
ideas to solve problems. In the Improve Phase, brainstorming techniques are
used to generate ideas for process improvements. Effective brainstorming helps
teams think creatively about potential solutions.
Popular Brainstorming Techniques:
1. Classic Brainstorming: A group of people shares ideas rapidly without
judgment. The key is to encourage quantity over quality, as the initial
goal is to generate many ideas.
o Example: In a marketing department, brainstorming might
generate ideas for new advertising campaigns or ways to improve
social media engagement.
 2. Reverse Brainstorming: Rather than asking how to solve the problem,
ask how to cause or worsen the problem. This can help identify what to
avoid or aspects of the process that need improvement.
o Example: Asking how to increase customer complaints can reveal
bottlenecks in customer service processes.
3. Mind Mapping: This technique visually organizes ideas around a central
concept. It’s useful for identifying connections between different
solutions and processes.
4. Nominal Group Technique: This involves writing down ideas individually
and then discussing them as a group. This technique is particularly useful
for avoiding groupthink.
o Example: A project management team could use this method to
come up with ideas on how to improve project timelines.

Identify Opportunities for Digitization

In the Improve Phase, it is important to identify areas where digitization can

make a substantial impact by improving efficiency, speed, and accuracy.
How to Identify Digitization Opportunities:
1. Review Existing Processes: By mapping out workflows, teams can spot
manual processes that are time-consuming and prone to error.
2. Use Data Analytics: Analytics tools can help identify where bottlenecks
occur and where automation would be beneficial.
3. Engage Stakeholders: Employees who are involved in day-to-day
processes often have insights into what could be automated or digitized.
Example: A logistics company might identify the manual entry of shipping data
as an opportunity for digitization. By integrating barcodes and RFID tags, the
company can automate the process of inventory tracking and reduce errors.

Methods for Prioritizing Solutions

Once a list of potential improvements has been generated, it's important to
prioritize them based on their feasibility, impact, and resource requirements.
Several methods can help in this decision-making process.
Common Methods:
1. Pareto Analysis (80/20 Rule): This method suggests that 80% of the
effects come from 20% of the causes. Prioritize solutions that will have
the most significant impact, focusing on the small number of changes
that will create the largest benefits.
o Example: A customer support team might find that most
complaints are caused by a few recurring issues. By addressing
these issues, the team can reduce complaints significantly.
2. Cost-Benefit Analysis: This analysis involves comparing the costs of
implementing a solution with the expected benefits. This helps identify
which solutions will provide the best return on investment.
o Example: A manufacturing company may analyze whether it’s
better to invest in new machinery or improve training for
employees. If the machinery results in substantial long-term
savings, it might be prioritized.
3. Impact vs. Effort Matrix: Plot the solutions on a matrix, where the Y-axis
represents impact and the X-axis represents effort. This helps in
selecting solutions that offer the most impact with the least amount of
effort.

Introduction to FMEA (Failure Mode and Effect Analysis)

FMEA is a systematic approach to identifying and evaluating potential failure
modes in a process. It helps teams prioritize failures based on their potential
severity, likelihood of occurrence, and detectability.
How FMEA Works:
1. Identify Failure Modes: Look at each step in the process and consider
how things might go wrong.
 o Example: In an automobile manufacturing process, a failure mode
might be a faulty part assembly.
2. Assess the Effects of Each Failure: Evaluate the consequences of each
failure. Could it harm customers or result in lost time or money?
3. Prioritize Failures: Rank the failure modes based on the Risk Priority
Number (RPN), which is calculated by multiplying severity, probability,
and detectability. This helps prioritize which failure modes to address
first.

5S, Kanban, SMED, Spaghetti Chart, Kaizen, Poka Yoke

These are Lean tools used to improve the efficiency and effectiveness of
processes.
1. 5S: A methodology for organizing the workplace to reduce waste and
improve efficiency.
• Sort: Remove unnecessary items from the workplace.
• Set in order: Arrange the necessary items so that they are easy to find
and use.
• Shine: Clean the workspace and equipment regularly.
• Standardize: Set standards for processes and organization.
• Sustain: Regularly audit and maintain the improvements.
2. Kanban: A visual system for managing the flow of tasks or materials. It
helps control inventory levels and ensures that work is completed in the right
order.
3. SMED (Single-Minute Exchange of Dies): This method reduces the time it
takes to switch from one process or product to another, often in
manufacturing. It focuses on minimizing downtime during setup or
changeover.
4. Spaghetti Chart: A tool used to visualize the flow of materials or people in a
process. It helps identify unnecessary movements and bottlenecks.
5. Kaizen: A philosophy of continuous improvement. In a Kaizen culture,
small, incremental improvements are made on a regular basis.
6. Poka Yoke: A mistake-proofing tool designed to prevent errors from
happening. For example, using color-coded parts in an assembly line to
prevent workers from using the wrong components.

Solution Selection Based on IoT/Digital Twin

The integration of IoT (Internet of Things) and Digital Twin technology helps
improve processes by enabling real-time monitoring and simulation.
IoT: Uses sensors and devices to collect data on processes and equipment.
This data can be used to monitor performance and identify areas for
improvement.
Digital Twin: A virtual model of a physical asset, process, or system. A digital
twin allows teams to simulate different scenarios and evaluate the impact of
changes without affecting the actual process.

Force Field Analysis

Force Field Analysis helps visualize the forces that drive or resist change. It’s a
valuable tool for identifying and overcoming obstacles to process
improvement.
Steps:
1. Identify Driving Forces: These are the factors that encourage change,
such as competitive pressure, customer demands, or internal
inefficiencies.
2. Identify Resisting Forces: These are the factors that work against change,
such as resistance from employees, lack of resources, or organizational
inertia.
 3. Plan Interventions: Develop strategies to strengthen driving forces (e.g.,
increasing customer pressure) and reduce resisting forces (e.g.,
addressing employee concerns).

Control Phase

The Control Phase ensures that the improvements made during the Improve
Phase are sustained over time. It involves monitoring the process and ensuring
that any deviations from the desired state are corrected promptly.

Implementing Process and Process Controls

Once the new solutions have been implemented, process controls are put in
place to ensure they are functioning as intended. These controls are designed
to monitor and measure the performance of the new processes.

Control Charts
Control charts are graphical tools used to monitor the stability of processes
over time. They help identify whether a process is in statistical control or if
corrective action is needed.

Change Management
Change Management focuses on ensuring that employees adapt to the new
processes and improvements. This involves training, communication, and
support throughout the transition.

Exercises and Simulations

1. Simulation Part 5: Identification of solution and implementation plan.

2. Simulation Part 6: Process control and monitoring through control charts
to ensure the process continues to meet its performance targets.

These phases work together to ensure that organizations can achieve

sustainable process improvements. The Improve phase focuses on finding
innovative solutions, while the Control phase ensures that those solutions are
maintained effectively over time.
4o mini