six sigma improvement case study

• Onsite training

3,000,000+ delegates

15,000+ clients

1,000+ locations

• KnowledgePass
• Log a ticket

01344203999 Available 24/7

Six Sigma Case Study: Everything You Need to Know

Explore the field of Six Sigma Case Studies in our comprehensive blog. From defining the methodology to real-world applications, our 'Six Sigma Case Study: Everything You Need to Know' blog sheds light on this powerful problem-solving tool. Uncover success stories and learn how Six Sigma can drive efficiency and quality improvements in various industries.

Exclusive 40% OFF

Training Outcomes Within Your Budget!

We ensure quality, budget-alignment, and timely delivery by our expert instructors.

Share this Resource

• Six Sigma Black Belt Upgrade
• Lean Six Sigma Green Belt
• Six Sigma Yellow Belt
• Six Sigma Black Belt
• Lean Six Sigma Black Belt

By analysing such case studies, one can gain insights into the successful application of Six Sigma in various industries and understand its impact on process improvement. Read this blog on Six Sigma Case Study to learn how real-world businesses have achieved remarkable process improvement and cost savings. 

Table of Contents  

1) Understanding Six Sigma Methodology 

2) Six Sigma Case Study 

a) Improving customer service 

b) Improving delivery efficiency 

3) Conclusion 

Understanding Six Sigma Methodology

By applying statistical analysis and data-driven decision-making, Six Sigma helps organisations identify the root cause of problems and implement effective solutions. It emphasises the importance of process standardisation, continuous improvement, and customer satisfaction. With its focus on rigorous measurement and analysis, Six Sigma enables organisations to drive efficiency, reduce waste, and deliver exceptional products and services. The methodology follows a step-by-step process called Define, Measure, Analyse, Improve, and Control (DMAIC). These five phases are briefly explained below: 

a) Define: The project goals and customer requirements are clearly defined in this phase.  

b) Measure: In this phase, data is collected to understand the process's current state and identify improvement areas.  

c) Analyse: This phase focuses on analysing data to determine the root cause of defects or variations.  

d) Improve: This phase involves implementing solutions and making necessary changes to eliminate the identified issues.  

Six Sigma Case Study  

In this section we discuss two Six Sigma Case Study that will help you understand and use it better.  

Case Study 1: Improving customer service  

This Six Sigma Case Study will focus on a telecommunications company facing significant customer service challenges. The issues included long wait times, frequent call transfers, unresolved issues, and many more. The company decided to apply Six Sigma methodologies to enhance customer satisfaction.  

a) Define phase: Using the DMAIC approach, the team began by defining the problem: long wait times and inefficient call handling. They set a goal to reduce average wait time and increase first-call resolution rates.  

b) Measure phase: In this phase, data was collected to analyse call volume, wait times, and reasons for call transfers. This helped identify bottlenecks and areas for improvement.  

c) Analyse phase: During this phase, the team discovered that inadequate training and complex call routing were key contributors to the problems. They also found that certain product issues required better resolution protocols.  

d) Improve phase: In this phase, targeted solutions were introduced and implemented to address these issues. The team revamped the training program, ensuring agents were well-trained and equipped to handle customer inquiries. They simplified call routing and introduced automated prompts for quicker issue resolution.  

e) Control phase: Finally, monitoring systems were established in the control phase to track key metrics and ensure sustained improvements. Regular feedback loops were implemented to identify emerging challenges and make necessary adjustments.  

The results were exceptional. Average wait times were reduced by 40%, and first-call resolution rates increased by 25%. Customer satisfaction scores improved significantly, leading to increased loyalty and positive word-of-mouth.  

This Six Sigma Case Study highlights how Six Sigma methodologies can drive transformative improvements in customer service. By focusing on data analysis, process optimisation, and continuous monitoring, organisations can achieve outstanding outcomes and deliver exceptional customer experiences. 

Understand the in-depth process of Six Sigma with our Six Sigma Yellow Belt Course . Join now!  

Case Study 2: Improving delivery efficiency

a) Define phase: The business used the Voice of the Customer (VoC) tool to understand customer needs and expectations. They identified prompt delivery, correct product selection, and a knowledgeable distribution team as crucial customer requirements. 

b) Measure phase: The team collected data to evaluate the problem of slow delivery. They discovered that their Order Fulfillment Cycle Time (OFCT) was 46% longer than competitors, leading to customer dissatisfaction.  

c) Analyse phase: The team brainstormed potential causes of slow delivery, including accuracy of sales plans, buffer stock issues, vendor delivery performance, and manufacturing schedule delays. They conducted a regression analysis, revealing that inadequate buffer stock for high-demand products was the main issue affecting delivery efficiency.  

d) Improve phase: The distributor implemented a monthly demand review to ensure that in-demand products are readily available. They emphasised ordering and providing customers with the specific products they desired.  

e) Control phase: The team developed plans to monitor sales of the top 20% of bestselling products, avoiding over or under-supply situations. They conducted annual reviews to identify any changes in demand and proactively adjust product offerings.  

By applying Six Sigma Principles , the plumbing product distributor significantly improved its delivery efficiency, addressing the root cause of customer dissatisfaction. Prompt action, data-driven decision-making, and ongoing monitoring allowed them to meet customer expectations, enhance its reputation, and maintain a competitive edge in the industry. This case demonstrates the power of Lean Six Sigma in driving operational excellence and customer-centric improvements. 

Take the next step in your professional development and boost your career by joining our Six Sigma Green Belt course .  

Conclusion  

We hope this blog gives you enough insights into the Six Sigma Case Study. This blog showcased the effectiveness of its methodology in driving transformative improvements. By applying DMAIC and using customer insights and data analysis, organisations have successfully resolved delivery inefficiencies, improving customer satisfaction and operational performance. The blog highlights how Six Sigma can be a powerful framework for organisations seeking excellence and exceptional value. 

Learn the six-sigma methodology to achieve business objectives with our Six Sigma Certification Training today!  

Frequently Asked Questions

Upcoming business improvement resources batches & dates.

Mon 1st Jul 2024

Mon 8th Jul 2024

Mon 15th Jul 2024

Sat 20th Jul 2024, Sun 21st Jul 2024

Mon 22nd Jul 2024

Mon 29th Jul 2024

Mon 5th Aug 2024

Mon 12th Aug 2024

Sat 17th Aug 2024, Sun 18th Aug 2024

Mon 19th Aug 2024

Tue 27th Aug 2024

Mon 2nd Sep 2024

Mon 9th Sep 2024

Sat 14th Sep 2024, Sun 15th Sep 2024

Mon 16th Sep 2024

Mon 23rd Sep 2024

Mon 30th Sep 2024

Mon 7th Oct 2024

Sat 12th Oct 2024, Sun 13th Oct 2024

Mon 14th Oct 2024

Mon 21st Oct 2024

Mon 28th Oct 2024

Mon 4th Nov 2024

Sat 9th Nov 2024, Sun 10th Nov 2024

Mon 11th Nov 2024

Mon 18th Nov 2024

Mon 25th Nov 2024

Mon 2nd Dec 2024

Sat 7th Dec 2024, Sun 8th Dec 2024

Mon 9th Dec 2024

Mon 16th Dec 2024

Mon 6th Jan 2025

Mon 13th Jan 2025

Mon 20th Jan 2025

Mon 27th Jan 2025

Mon 3rd Feb 2025

Mon 10th Feb 2025

Mon 17th Feb 2025

Mon 24th Feb 2025

Mon 3rd Mar 2025

Mon 10th Mar 2025

Mon 17th Mar 2025

Mon 24th Mar 2025

Mon 31st Mar 2025

Mon 7th Apr 2025

Mon 14th Apr 2025

Tue 22nd Apr 2025

Mon 28th Apr 2025

Tue 6th May 2025

Mon 12th May 2025

Mon 19th May 2025

Tue 27th May 2025

Mon 2nd Jun 2025

Mon 9th Jun 2025

Mon 16th Jun 2025

Mon 23rd Jun 2025

Mon 30th Jun 2025

Mon 7th Jul 2025

Mon 14th Jul 2025

Mon 21st Jul 2025

Mon 28th Jul 2025

Mon 4th Aug 2025

Mon 11th Aug 2025

Mon 18th Aug 2025

Tue 26th Aug 2025

Mon 1st Sep 2025

Mon 8th Sep 2025

Mon 15th Sep 2025

Mon 22nd Sep 2025

Mon 29th Sep 2025

Mon 6th Oct 2025

Mon 13th Oct 2025

Mon 20th Oct 2025

Mon 27th Oct 2025

Mon 3rd Nov 2025

Mon 10th Nov 2025

Mon 17th Nov 2025

Mon 24th Nov 2025

Mon 1st Dec 2025

Mon 8th Dec 2025

Mon 15th Dec 2025

Get A Quote

WHO WILL BE FUNDING THE COURSE?

My employer

By submitting your details you agree to be contacted in order to respond to your enquiry

• Business Analysis
• Lean Six Sigma Certification

Share this course

Our biggest spring sale.

We cannot process your enquiry without contacting you, please tick to confirm your consent to us for contacting you about your enquiry.

By submitting your details you agree to be contacted in order to respond to your enquiry.

We may not have the course you’re looking for. If you enquire or give us a call on 01344203999 and speak to our training experts, we may still be able to help with your training requirements.

Or select from our popular topics

• ITIL® Certification
• Scrum Certification
• Change Management Certification
• Business Analysis Courses
• Microsoft Azure Certification
• Microsoft Excel Courses
• Microsoft Project
• Explore more courses

Press esc to close

Fill out your  contact details  below and our training experts will be in touch.

Fill out your   contact details   below

Thank you for your enquiry!

One of our training experts will be in touch shortly to go over your training requirements.

Back to Course Information

Fill out your contact details below so we can get in touch with you regarding your training requirements.

* WHO WILL BE FUNDING THE COURSE?

Preferred Contact Method

No preference

Back to course information

Fill out your  training details  below

Fill out your training details below so we have a better idea of what your training requirements are.

HOW MANY DELEGATES NEED TRAINING?

HOW DO YOU WANT THE COURSE DELIVERED?

Online Instructor-led

Online Self-paced

WHEN WOULD YOU LIKE TO TAKE THIS COURSE?

Next 2 - 4 months

WHAT IS YOUR REASON FOR ENQUIRING?

Looking for some information

Looking for a discount

I want to book but have questions

One of our training experts will be in touch shortly to go overy your training requirements.

Your privacy & cookies!

Like many websites we use cookies. We care about your data and experience, so to give you the best possible experience using our site, we store a very limited amount of your data. Continuing to use this site or clicking “Accept & close” means that you agree to our use of cookies. Learn more about our privacy policy and cookie policy cookie policy .

We use cookies that are essential for our site to work. Please visit our cookie policy for more information. To accept all cookies click 'Accept & close'.

• Our Courses
• About DCM Learning
• Training Resources
• Inhouse Training

Lean Six Sigma Project Examples | 17 Full Case Studies

Ready to begin your first Lean Six Sigma project? Looking for examples for inspiration or reference to get you started? Here are some project storyboards from different industries and from home. Remember, Lean Six Sigma can help you with more than just work!

• Reducing Underwriting Resubmits by Over 20%  

Governments

• A Call to Change: Pioneering Lean Six Sigma at Los Angeles County  
• Can Lean Six Sigma Be Applied in County Government?  
• How the City of San Antonio Increased Payments for Street Maintenance Using Lean Six Sigma  
• Reducing Bid Tab Creation Cycle Time by 22%  
• Reducing Cycle Time for Natural Disaster Response by 50%  

Manufacturing

• Increasing First Run Parts From 60% to 90% With Lean Six Sigma  
• Reducing Bent/Scratched/Damaged (BSD) Scrap for Building Envelopes  
• Reducing Lead Time in Customer Replacement Part Orders by 41%  
• Reducing Learning Curve Ramp for Temp Employees by 2 Weeks  
• Reducing Purchase Order Lead Time by 33% Using Lean Six Sigma  
• Herding Cats Using Lean Six Sigma: How to Plan for and Manage the Chaos of Parallel Processes  
• Lean Six Sigma Increases Daily Meat Production by 25%  
• Lean Six Sigma Helps Feed People In Need 45% Faster  
• Accelerating Lean Productivity With Immersive Collaboration  
• Reducing Incorrect Router Installations by 60% for Call One  
• Reducing Software Bug Fix Lead Time From 25 to 15 Days  

Lean Reviews: Stories from Our Customers

Over the past 2 years, over 2,000 learners (2,197 to be exact) have come to DCM to learn more about lean and get certified.  Read (and watch) their reviews to see how our courses have helped them achieve their career goals.

Inhouse Tailored Training for Your Team

We provide training programs that are developed by industry, for industry. Our range of programs can be delivered in a way that suits the needs of your business to offer your employees learning that is accessible and flexible.

We add value to your business by providing specialised, flexible and scalable training that meets your training needs. As your workforce grows and evolves, our globally certified and industry-validated learning solutions can assess, train and qualify your employees. For more information on how we can help please visit the in-house training page .

Membership, Stay Connected. Stay Relevant.

Completing a program is a point-in-time exercise that delivers huge value, but there is a next step to maintaining the currency of your skills in the ever-evolving professional world.

Membership is the next step .

A unique platform, membership is designed to ensure that you are in tune and up-to-date with the latest tools, trends and developments. Being a member provides just-in-time training and continuous professional development, and an exclusive and evolving content library informed by subject matter experts and industry leaders.

Unlock your full learning potential with our free DCM membership! Join our community and access exclusive resources to boost your educational journey.

Thanks for signing up. Here are some training courses for you to explore.

By clicking “Start Learning”, you agree to automatically become a DCM member at no additional cost, unless already a member. You have the option to opt out at any time.

Free Bitesize Courses

We have over 100 free courses available to explore, all created by expert trainers, packed full of practical exercises and real-world examples.

Make sure you Safeguard Your Training Investment . DCM offer courses accredited by:

Course Categories

*Add your email and we will send you the full course directory to review at a time that suits you.

Open Your Brochure

Just to let you know, we are offering €200 credit for the course when you become a member with DCM.

We are very proud of our advisory team in DCM Learning. If you have any questions at all please feel free to ask our team. They will be more than happy to help.

We value your privacy and we will only get in touch about upcoming courses or events that are available to members.

It's so simple... We'll send you the €200 credit and access to the exclusive members area with a full list of the free courses.

By clicking “Get Your Voucher”, you agree to our terms and privacy policy .

Top Six Sigma Case Study 2024

Home Blog Quality Top Six Sigma Case Study 2024

Six Sigma is an array of methods and resources for enhancing corporate operations. When Bill Smith was an engineer at Motorola, he introduced it in 1986 to find and eliminate mistakes and defects, reduce variance, and improve quality and efficiency. Six Sigma was first used in manufacturing as a quality control tool. When long-term defect levels are less than 3.4 defects per million opportunities ( DPMO ), Six Sigma quality is reached.

Six Sigma case study   offers a glimpse into how various companies have harnessed the five distinct phases: defining, measuring, analyzing, improving, and controlling, principles of Six Sigma to overcome challenges, streamline processes, and improve across diverse industries.

What Are Six Sigma Case Studies, and Why Are They Important?

Six Sigma case studies examples   show how Six Sigma techniques have been used in businesses to solve issues or enhance operations. For practitioners and companies pondering enforcing Six Sigma concepts, these case studies are an invaluable resource to learn the advantages and efficacy of Six Sigma adoption.

Here are the reasons why six sigma case study is important:

Success Illustration: Case studies demonstrate how Six Sigma projects generate tangible advantages like better productivity, fewer defects, and more customer satisfaction while providing unambiguous evidence of their efficacy.

Learning Opportunities:  They deliver vital insights to use Six Sigma tools and processes realistically and allow others to learn from successful approaches and avoid common errors.

ROI Demonstration:  Case studies provide quantitative data to show the return on investment from Six Sigma projects, which helps justify resources and get support for future initiatives.

Promoting Adoption:  They cultivate a continuous improvement culture and show how Six Sigma concepts can be used in different situations and sectors, which encourages other businesses to embrace the methodology.

Become a Six Sigma Certified Professional and lead process improvement teams to success. Learn how to streamline processes and drive organizational growth in any industry. Join our Lean 6 Sigma training courses and transform your career trajectory with valuable skills and industry recognition.

Six Sigma Case Studies

Let us discuss some real-world case study on six sigma   examples of successful Six Sigma undertakings through case studies:

1. Six Sigma Success: Catalent Pharma Solutions

Do you know how Six Sigma techniques turned things around for Catalent Pharma Solutions?

Six Sigma methodologies, initially presented by Motorola in 1986 and prominently used by General Electric during CEO Jack Welch's leadership, are essential for enhancing customer contentment via defect minimization. Catalent Pharma Solutions, a top pharmaceutical development business, employed Six Sigma to address high mistake rates in its Zydis product line. By applying statistical analysis and automation, training employees to various belt levels, and implementing Six Sigma procedures, Catalent was able to maintain product batches and boost production. This case study illustrates how Six Sigma approaches are beneficial for businesses across all industries as they can improve processes, prevent losses, and aid in cost reduction.

2. TDLR's Record Management: A Six Sigma Success Story

The Texas Department of Licensing and Regulation (TDLR) faced escalating costs due to the storage of records, prompting a Six Sigma initiative led by Alaric Robertson. By implementing Six Sigma methodologies, process mapping, and systematic review, TDLR successfully reduced storage costs and streamlined record management processes. With a team effort and strategic changes, TDLR has achieved significant cost savings and improved efficiency. The project also led to the establishment of a robust records management department within TDLR.

3. Six Sigma Environmental Success: Baxter Manufacturing

Baxter Manufacturing utilized Six Sigma principles to enhance its environmental performance and aim for greater efficiency. Through the implementation of Lean manufacturing and accurate data collection, Baxter reduced waste generation while doubling revenue and maintaining waste levels. With a cross-functional team trained in Six Sigma, the company achieved significant water and cost savings without major investments in technology. It led to promotions for team leaders and showcased the effectiveness of Six Sigma in improving environmental sustainability.

4. Aerospace Manufacturer Boosts Efficiency With Six Sigma

Have you heard about how Six Sigma principles transformed an aerospace parts manufacturer? Here is the 6 Sigma case study   for aerospace parts manufacturer

A small aerospace parts manufacturer used Six Sigma to cut machining cycle time, reducing costs. Key engineers obtained Six Sigma certification and led the project, involving management and operators. Using DMAIC, they analyzed data, identified root causes, and implemented lean solutions. The process yielded a 46% reduction in cycle time and an 80% decrease in variation, enhanced productivity and profitability. The case highlights how Six Sigma principles can benefit businesses of all sizes and emphasizes the importance of training for successful implementation.

Enroll in the  Lean Six Sigma Green Belt certification online training to advance your career! Gain expertise in process improvement and organizational transformation with expert-led training and real-world case studies. Start now to become a certified professional in quality management.

5. Ford Motors: Driving Success

This is a   case study on Six Sigma  i ncorporated by Ford Motors to streamline processes, improve quality, significantly reduce costs, and reduce environmental impact. Initially met with skepticism, Ford's implementation overcame challenges, achieving remarkable results: $2.19 billion in waste reduction, $1 billion in savings, and a five-point increase in customer satisfaction. Ford's Consumer-driven Six Sigma initiative set a benchmark in the automotive industry and proved the efficacy of data-driven problem-solving. Despite obstacles, Ford's Six Sigma exemplifies transformative success in process improvement and customer satisfaction enhancement.

6. 3M's Pollution Prevention Six Sigma Success

Have you checked out how 3M tackled pollution with Six Sigma? It's pretty remarkable. 3M leveraged Six Sigma to pioneer pollution prevention, saving $1 billion and averting 2.6 million pounds of pollutants over 31 years. With 55,000 employees trained and 45,000 Lean Six Sigma projects completed, they focused on waste reduction and energy efficiency. Results included a 61% decrease in volatile air emissions and a 64% reduction in EPA Toxic Release Inventory. Surpassing goals, they doubled Pollution Prevention Pays projects and showcased Six Sigma's prowess in cost-saving measures.

7. Microsoft Sigma Story Lean Six Sigma

By using Lean Six Sigma case studies, Microsoft increased customer interactions and profitability through waste removal and process optimization. They concentrated on improving the quality of the current process and reducing problems by utilizing the DMAIC technique. Eight areas were the focus of waste elimination: motion, inventory, non-value-added procedures, waiting periods, overproduction, defects, and underutilized staff talent. Microsoft streamlined processes and encouraged innovation, which allowed them to maintain productivity and client satisfaction even as technology changed.

8. Xerox's Lean Six Sigma Success Story Six Sigma

It is another important case study of the Six Sigma project. When Xerox implemented Lean Six Sigma in 2003, the organization underwent a significant transformation. They reduced variance and eliminated waste as they painstakingly optimized internal operations. It improved their operational effectiveness and raised the caliber of their goods and services. Through extensive training programs for staff members, Xerox enabled its employees to spearhead projects aimed at improving different departments and functions. The organization saw significant improvements in customer satisfaction and service performance.

9. A Green Belt Project Six Sigma Case Study

It is one of the best examples of a Six Sigma case study. Anne Cesarone's Green Belt project successfully reduced router configuration time by 16 minutes, a remarkable 55% improvement. Anne maintained router inventory, made improvements to documentation and configuration files, and started router requests sooner by resolving last-minute requests and setup mistakes. The initiative resulted in less router programming time from 29 to 13 minutes, an increase in router order lead time of 11 days, and a 60% drop in incorrect configurations. These raised customer happiness and increased operational effectiveness while proving the benefits of process improvement initiatives.

10. Improving Street Maintenance Payments with Lean Six Sigma

Jessica Shirley-Saenz, a Black Belt at the City of San Antonio, used Lean Six Sigma to address delays in street maintenance payments Lean Six Sigma case study examples. Contractors were experiencing extended payment times, risking project delays and city infrastructure integrity. Root causes included payment rejections and delayed invoicing. By implementing quantity tolerance thresholds, centralizing documentation processes, and updating payment workflows, monthly payment requests increased from 97 to 116. Rejected payments decreased from 17 to 12, reducing the rejection percentage from 58% to 42%, saving $6.6 million.

 Six Sigma's effectiveness spans industries, from healthcare to technology. Case studies demonstrate its ability to optimize processes and improve outcomes. From healthcare facilities streamlining patient care to tech companies enhancing software development, Six Sigma offers adaptable solutions for diverse challenges. These real-world examples illustrate how its methodologies drive efficiency, quality, and customer satisfaction. Professionals can learn valuable lessons from using Six Sigma in healthcare studies, identify strategies to overcome obstacles and facilitate continuous improvement. Organizations can emulate best practices and implement similar initiatives to achieve measurable results by studying successful implementations.

Ready to enhance your skills and advance your career with Six Sigma certification? Join our comprehensive KnowledgeHut's best lean Six Sigma courses to master Six Sigma principles and methodologies. Become a sought-after professional in IT, Manufacturing, Healthcare, Finance, and more industries. Enroll now to accelerate your career growth!

Frequently Asked Questions (FAQs)

Six Sigma case studies are available in various formats and places, such as books, academic journals, professional publications, and Internet sites. Many companies that have effectively adopted Six Sigma publish their case studies on their websites or at industry exhibitions and conferences.

Six Sigma case studies provide insightful information on how businesses have addressed certain issues, enhanced procedures, and produced noticeable outcomes. Professionals gain knowledge about best practices, prevalent errors to avoid, and creative problem-solving methods in several industries and circumstances.

Professionals can share their Six Sigma case studies through industry forums, professional networking platforms, blogs, and social media. They can submit their case studies to publications or at conferences and workshops to reach a wider audience within the Six Sigma community.

Shivender Sharma

Shivendra Sharma, an accomplished author of the international bestseller 'Being Yogi,' is a multifaceted professional. With an MBA in HR and a Lean Six Sigma Master Black Belt, he boasts 15 years of experience in business and digital transformation, strategy consulting, and process improvement. As a member of the Technical Committee of the International Association of Six Sigma Certification (IASSC), he has led multi-million dollar savings through organization-wide transformation projects. Shivendra's expertise lies in deploying Lean and Six Sigma tools across global stakeholders in EMEA, North America, and APAC, achieving remarkable business results. 

Avail your free 1:1 mentorship session.

Something went wrong

Upcoming Quality Management Batches & Dates

• Certified ScrumMaster
• PMI-ACP Exam Prep
• Leading SAFe® 6.0 Certification
• SAFe Scrum Master
• Certified Scrum Product Owner (CSPO)
• SAFe for Teams
• Agile Scrum Foundation
• AgilePM Foundation and Practitioner Certification
• Agile Scrum Master (ASM)
• Kanban Training
• Scrum Fundamentals
• PMP Certification
• Project Management Fundamentals
• CAPM Exam Prep
• Change Management Foundation and Practitioner Certification
• PRINCE2 Foundation & Practitioner Certification (7th Edition)
• PRINCE2 Agile Foundation & Practitioner Certification
• Business Analysis Foundation and Practitioner Certification
• Microsoft Project Training
• JIRA Certification Training
• Lean Project Management
• ITIL 4 Foundation
• VeriSM™ Foundation
• SIAM Foundation
• SIAM Professional
• 7 QC Tools Training
• Minitab Essentials
• Lean Six Sigma Yellow Belt
• Six Sigma Awareness
• Lean Six Sigma Green Belt
• Design for Six Sigma
• Lean Six Sigma Black Belt
• Lean Fundamentals
• Value Stream Mapping
• Quality by Design
• Quality Function Deployment
• BPM and Six Sigma
• RCA through Six Sigma
• DevOps Foundation
• DevOps Master
• DevOps Professional
• Continuous Delivery Architecture
• COBIT 5 Certification
• Corporate Group Training
• 1-to-1 Training
• Join as a Trainer

• Top Blogs on Quality Management

Real-Life Examples of Six Sigma Implementation – Six Sigma Examples/ Use Cases

Six Sigma is a creative and flexible  series of methodologies aimed at improving organizational process quality and effectiveness. This blog on Six Sigma examples will explain a few use cases of Six Sigma methodology. Business today requires companies to be operational at maximum efficiency and effectiveness. The competitive markets mean everyone is looking to distinguish themselves and offer better products and services. A sustainable way to introduce better business practices is by changing your approach fundamentally. 

Companies are built to achieve corporate goals. The methods to achieve them are plenty and streamlined by management for incorporation. The concepts of optimization, minimizing waste, and maximizing productivity are strongly incorporated into the foundation of Lean and Six Sigma principles. 

These business models are conceptual and can be adapted to any industry or business environment. All you need is a guided professional and a willingness to convert your better business practices into the best possible. In this article, let us explore some Six Sigma examples and success stories.

What is Six Sigma?

The definition of Six Sigma has been under much debate. It can be broadly classified into four concepts:

A Philosophy  – Six Sigma is a school of thought that views workflows and activities as processes that can be expounded, quantified, analyzed, bettered, and monitored. It states an input is required to produce an output. Therefore, exercising control over the input gives you a firm hand in managing output. It is sometimes expressed in the equation  y=f(x)  where  x  stands for the input and  y  for the output. 

A Set of Tools –  Six Sigma comprises controls such as qualitative techniques and quantitative tools used to improve business capabilities internally. Six Sigma tools include SPC (statistical process control), FMEA (failure mode and effects analysis), and control charts. Professionals who deal with Six Sigma explain that tools are continually evolving and are not set in stone. 

A Methodology –  Six Sigma is considered to be a derivative of the DMAIC approach . DMAIC is a data-centric improvement method that operates cyclically. It revolves around Defining, Measuring, Analyzing, Improving, and Controlling. This principle drives Six Sigma users to begin by understanding the existing problem and implementing long term solutions. 

A Metric –  When assessing Six Sigma as a metric, it is defined as 3.4 defects per million opportunities.

Six Sigma, in its simplest form, reduces the possibility of variation in production. The objective is to have a firm grasp on the production process. Lean Six Sigma is a term often associated with Six Sigma. Lean methods are used to minimize wastage during production; this includes time and resources spent on processes that do not directly contribute to better output from activities. Lean Six Sigma is a philosophy that brings together waste minimization and production optimization. It improves customer satisfaction by removing unnecessary processes and waste, creating better workflows, faster output, and possibly a competitive advantage. To attest to the importance of Six Sigma, in the next section of this article, let us explore some Six Sigma examples.

Implementing Six Sigma 

Six Sigma can be implemented in a number of strategies, however there are two baseline options provided to all organizations looking to make the transition;

Introducing Six Sigma Training

Organizations can introduce a fundamental revamp across the organization through a Six Sigma program. Expose employees to better practices and conditioning by introducing the fundamentals and allowing a professional to understand what Six Sigma is and what it helps with. It is important to note that it is mostly an information transfer that happens during Six Sigma training . It is up to the business to adopt the methods to the organization and its practices. 

Introducing Six Sigma Infrastructure 

Creating a Six Sigma infrastructure can be quickly moved along by introducing certified professionals into your organization. Often called “Black Belts”, they move into your business for a period of four weeks to four months and begin teaching your business how to adapt the strategies to your activities. Creating the infrastructure creates a firm guideline to make changes to operations and corporate culture. 

Now let us look into some interesting Six Sigma examples and success stories.

Six Sigma Examples

There are several organizations across various industries that have adopted Six Sigma practices to great success . High profile clients include;

General Electric

The American multinational was struggling to improve overall product quality and service even with the best professionals onboarded. After running a six sigma method trial, the company was able to introduce better-streamlining measures into product assurance. As a result, revenue increased. 

This Indian based technology behemoth was the industry frontrunner for consumer goods. However, their customer service was less than satisfactory. Enter Six Sigma. Over time the methods were used to neutralize threats and create a better experience for clients. 

We all know and love the technology giant that gave us Windows and Office. A contributing factor to the success behind their service and products is Six Sigma. The industry leader has made it no secret that Six Sigma methods have enabled better back-end processes and, as a result, better user experience. It acts as a case in point for companies looking to transition into Six Sigma practices. 

The telecommunications company was one of the first to implement six sigma methods. As a trial, the company implemented Six Sigma to assess the impact on improving product quality and streamlining the transition between services to revenue. The positive results created better company-wide performance and permanent incorporation. 

Boeing   Airlines

One of the world’s largest aerospace companies was having issues with air fans within the engines. Unable to pinpoint the exact problem, a group of experts were called in to investigate. They deduced the problem stemmed from FOD (foreign object damage). Upon more in-depth inspection using Six Sigma methods , they could trace the problem to a more fundamental manufacturing issue causing electrical issues along with the FOD. 

Practically, the application for six sigma methods can be seen across any organization attempting to create better output. Introducing better control measures for various parts of the production process helps produce desirable results. 

Final Thoughts

The beauty of Six Sigma methods lies in their ability to adapt to different environments. The increased efficiency and effectiveness are tangible in the success stories of industry giants implementing Six Sigma to success. Add to the real-life Six Sigma examples of by introducing skilled professionals or the Six Sigma infrastructure to your organization. 

The enterprises usually divide their workforce depending on the hierarchy to get their employees trained in different  Lean Six Sigma training programs  in Yellow Belt, Green Belt, Black Belt, Master Black Belt, and Six Sigma Champion. To get a better understanding of which Lean Six Sigma course benefits the most for you or the team, check out some of the popular courses below to get a comprehensive understanding of the same: 

Lean Six Sigma Yellow Belt Certification Training

Lean Six Sigma Green Belt Certification Training

Lean Six Sigma Black Belt Certification Training

Lean Fundamentals Certification Training

Lean IT Certification Training

RCA Through Six Sigma Certification Training

7QC Tools Certification Training

Value Stream Mapping Certification Training

RELATED ARTICLES MORE FROM AUTHOR

What is Cost of Poor Quality (COPQ)?

Top 6 Quality Management Trends to Follow in 2024

What is the Plan Do Check Act (PDCA) Cycle?

Leave a reply.

Save my name, email, and website in this browser for the next time I comment.

• 14,513 Likes
• 444 Followers
• 99,200 Subscribers
• 2,170 Followers

Related Articles

An Ultimate Guide to Project Management Career Prospects

What Are Some Popular Root Cause Analysis Methods?

Tips for Staying Organized and On Track as a Project Manager

Top 10 Agile Strengths – Key for Enterprise Performance

A Comprehensive Guide to Building a Cybersecurity Strategy

Popular posts.

The Project Management Life Cycle Explained

Roles and Responsibilities of a Quality Control Inspector

7 Cs of Effective Communication with Example

Top 5 Factors for Project Success

Quality Analyst Job Role and Responsibilities- Explained!

Suggested posts.

• 7 Cs of Effective Communication with Examples
• Project Management Lifecycle
• Project Success Factors
• Quality Control Inspector Job Description
• Risk Management Examples
• QA Manager Job Description
• Quality Management Team Roles and Responsibilities
• Risk Management Tools & Techniques
• Quality Analyst Job Description
• What is Business Value
• Who are Project Stakeholders
• Importance of Project Management
• What is Project Management
• Project Management Skills
• Project Manager Job Description
• Agile Project Manager Interview Questions
• Risk and Compliance Manager Job Description
• Risk Management Process
• Project Scope Management
• Healthcare Project Manager Job Description
• Six Sigma Project Examples
• Risk Analysis Methods
• ITIL Service Lifecycle
• Risk Manager Job Description

POPULAR CATEGORIES

• Best Project Management Blogs 265
• Top Agile Blog Posts 158
• Top Blogs on Quality Management 126
• Latest IT Service Management Blogs 108
• Trending Articles on DevOps 65
• Popular Blogs on IT Security and Governance 55
• Top Blogs on Professional Development 33
• Top Infographics Collection 8

Download E-book Blog

Thank You for submitting your enquiry. One of our training consultants will get in touch with you shortly.

50+ Training and Certification Programs - Upskill Today Learn more about our training programs.

Shopping Cart

Learning path

• Lean Six Sigma White Belt (EN)
• Lean Six Sigma Yellow Belt (EN)
• Lean Six Sigma Green Belt (EN)
• Lean Six Sigma Black Belt (EN)

Quick links

• Get Certified

Get In Touch

• [email protected]
• Book a call

Follow Social Media

There was a problem reporting this post.

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

• See blocked member's posts
• Mention this member in posts
• Invite this member to groups
• Message this member
• Add this member as a connection

Please note: This action will also remove this member from your connections and send a report to the site admin. Please allow a few minutes for this process to complete.

Take advantage of your time, International Six Sigma Inc. offers both Instructor-led Live Virtual classes as well as Online Self-Paced training . Enroll Today!

Six Sigma in Action: A Case Study at 3M

Introduction to 3m.

3M is the world’s 3 rd most innovative technology company that strives to create groundbreaking products. The goal of 3M is simple – create products that make positive differences in everyone’s lives. Six Sigma specializes management strategy method that has evolved and modernized since its origin in 1986. It focuses on proactively deterring issues that will arise in production and corporate operations. Like many companies have begun to do, 3M acquired the Six Sigma management strategy and has revolutionized its infrastructure. The “World’s Most Ethical Company” is now a leading innovator in technology, energy, and more due to the success of the method. Now, 3M offers an in-depth case study to show exactly how Six Sigma transformed their company.

Implementing Six Sigma

Gaining control of 3M in 2001, James McNerney placed the Six Sigma methodology into the backbone of the company. McNerney’s unique, considerate approach led to a four-year overhaul of the manufacturing and production processes. From eliminating waste to improving productivity, this methodology grew revenue faster than ever and continues to lead innovative technologies.

McNerney grew 3M other enterprises such as Global Souring, 3m Acceleration, eProductivity, and Indirect Cost Control. As a result, 3M began 2005 with over 30,000 employees Six Sigma certified, with a minimum Green Belt training for all technical and sales staff. Combining the Six Sigma methodology with a strong leadership, 3M consistently practices an ever-improving production process with increasing profits to match.

In addition to substantial revenue growth, this methodology continues to bring out massive savings and benefits. The 2003 Annual Report states that operating income was amplified by more than $500,000 in 2002 alone as a result of the Six Sigma initiatives. This figure is substantially larger than earlier predictions, and the forecast continues to remain high for the following year, sitting at $400,000, an estimate which was successfully met as reported by the Prudential Financial Conference in September 2004.

The Results

Alongside considerable financial growth, 3M enjoys significant corporate network growth. 3M’s network continues to expand by collaborating with numerous companies on over 250 projects such as Ford, Estee Lauder, Motorola, Wal-Mart, and Procter & Gamble. Mature, effective Six Sigma programs are easily spotted, sharing their knowledge with customers, suppliers, and other important personnel. Only Six Sigma has the tools necessary to transforming your business, with total process improvements and reducing defects. Six Sigma drives growth, reduces costs, increases revenue, and produces strong business relationships with customers that last a lifetime.

SixSigma.us offers both Live Virtual classes as well as Online Self-Paced training. Most option includes access to the same great Master Black Belt instructors that teach our World Class in-person sessions. Sign-up today!

Checkout Virtual Classroom Training Programs

SixSigma.com offers both Live Virtual classes as well as Online Self-Paced training. Most option includes access to the same great Master Black Belt instructors that teach our World Class in-person sessions. Sign-up today!

No responses / comments so far.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Save my name, email, and website in this browser for the next time I comment.

At home or workplace, we have you covered

Training Options

More than 500 locations

Classroom Training

Learn anytime, anywhere

Online Training

Live instructor-led training

Webinar Training

Customized training programs

On-site Training

Accelerated training programs

Blended Training

For streamlined business plans

Operational Excellence

Exclusive consulting services

Consulting Services

Fully customized programs

Group/Corporate Training

International six sigma inc. accreditation & affiliations.

Email: [email protected] Toll Free in the US: (866) 409-1363

Courses / Training

Improving Lab Performance with Six Sigma

Published: October 17, 2010 by Andrew Harte

Laboratories can be a taxing environment in which to implement Lean and Six Sigma. Labs are not the same as manufacturing – where Lean and Six Sigma got their start – because they typically have more variability in workload, less operational focus, less process reliability and longer task cycle times. However, through creative adaptation of the techniques it is possible for practitioners to deliver significant improvements in cost or speed.

This case study shows how a Lean Six Sigma project at a leading global pharmaceutical company managed to reduce lead times while improving productivity in the company’s quality control testing laboratory using the DMAIC approach.

Defining the goals of a Lean laboratory project may seem like a simple task, but that’s not always the case. The project goals can be the deciding factor in garnering support for the project from top management and from other employees. So the goals of the project should be chosen to mirror those of the business. The laboratory in this case study had goals of reducing the end-to-end cycle time of their products while keeping the cost per unit as low as possible. The goals of the lab’s DMAIC project reflected these overall site goals.

Tools such as Pareto charts and value stream maps are useful in deciding where the focus of a Lean laboratory project should be. A Pareto analysis of the incoming laboratory workload revealed that the majority of the workload (85 to 95 percent) was driven by three products: Products A, B and C (Figure 1).

Product A and C were from the same product family, received mostly the same tests and could be tested together at the same time. While Product B accounted for 19 percent of the sample volume, it did not account for 19 percent of the lab’s workload as it only required two very simple tests; in comparison, Products A and C received nine different tests. The project team decided to focus exclusively on A and C as they accounted for 80 to 90 percent of the lab’s workload and were the main priorities of the site.

The as-is process map revealed that a significant portion of the testing cycle time was spent on approval and release activities carried out after the batches were fully tested. As a result, the project team decided that approval activities would also be within the scope of the project.

During the Measure phase of the project, the team set out to establish valid reliable metrics to monitor progress toward the chosen goals. The lab already had in place metrics on cycle time. A look at the breakdown of cycle times for Product A showed a spread of times centred around 11 to 15 days, which corresponded to the lab’s target cycle time of 15 days. Sixty-six percent of samples either met the 15-day target time or were completed early, while 33 percent of samples were late. The average cycle time was 14.8 days (Figure 2).

Next, the project team considered how resources were used in the lab. It was immediately striking that the bulk of the resources in the lab were occupied by one test: Test x. Every one of sample type A and sample type C required this test and it was not possible to batch samples together; they had to be run individually. Also, the results of this test were required by a separate department in order for that department to proceed with their process. As a result, the laboratory heavily resourced this test with the aim of trying to test every sample every day. This was an inefficient tactic, as it resulted in variable numbers of samples being tested each day. For instance, five analysts might test 12 samples on one day and only test 4 the following day – representing a 67 percent drop in productivity from one day to the next. A strategy was required that would be consistently productive without adversely affecting cycle times. To do this, it would be necessary to control the number of samples tested each day.

The Analyze phase of the project looked at all the available data to determine the best way to move toward the desired goals of the project. The project team found that:

• Each day the lab received between 1 and 17 samples, resulting in an average of 7 per day.
• Weekly the lab received between 25 and 45 samples, resulting in an average of 36 per week.
• The weekly incoming workload was much less volatile than the daily pattern (coefficient of variance 0.2 versus 0.6).

Therefore, although it was impossible to predict how many samples would arrive on a given day, it was possible to say with reasonable certainty that over the week the lab would receive approximately 36 samples. It was clear that it would be possible to have some level of control over the number of samples tested if a weekly testing pattern was developed due to the smaller weekly variation. Next, the team determined the time needed to complete each test (or takt rate). The number of samples for each test would be different as Product C received some tests that product A did not (for example, Ccntent uniformity) and vice versa. .

Having analyzed and reviewed all of the data, the team decided on a clear strategy. The lab would run:

• A fixed, weekly repeating pattern of tests (known as a rhythm wheel ).
• Tests at the weekly average (i.e., the weekly takt rate).
• Every test every week.
• Tests of samples in first-in/first-out (FIFO) order.

In reality, the team had to pick a figure slightly above the average test number in order to cope with the expected weekly volatility, deliver acceptable lead times and account for failures/repeat testing. It was obvious that to follow this strategy some tests would have to be run more often. To ensure that productivity would not suffer, the team decided to reduce capacity for some tests (e.g. Test x) in order to reallocate those resources to increase capacity for other tests. Because a batch is only as fast as its slowest test, the end result would be to create more uniform overall cycle times for each of the tests.

To improve productivity and ensure consistent results, the team developed standard work for each of the testing roles. The team set about identifying:

• The optimum number of samples for one analyst to test in one shift.
• The best order in which to perform test activities.
• Any improvements that could be made to the process.
• Long periods of inactive time that could be used to run other short tests.
• How many times to run the test each week.

Because the new pattern – the rhythm wheel – controls what tests occur each day, it removes much of the unpredictability and volatility that individual analysts experience in day-to-day testing. This provides consistent results, thus ensuring both productivity and shorter lead times.

There was, however, concern over what effect the rhythm wheel would have on lead times for Test x. The team agreed that they would model the outcome for this test before any changes were made. Using data from the previous six months of testing, the model showed that 49 percent of samples would have been tested the day they arrived, 31 percent the next day and the remainder after two days. This was deemed acceptable by all affected process owners.

Advantages of a rhythm wheel:

• It was more productive than the old system, requiring only 40 full-time equivalent (FTE) shifts versus 54 FTE – a 26 percent improvement.
• It removed the uncertainty around the equipment capacity and avoided equipment conflicts.
• It removed a lot of the stress and scrambling from the daily testing routine for the analysts.
• Every test was run every week to ensure consistent and short lead times.

To address the issue of the long approval and release activity wait times, as identified in Define, the process was reengineered to remove this delay by operating to the laboratory’s testing takt rate and reviewing every batch every day.

Once all the changes were implemented, average cycle times fell from 15 to 8 days. The overall laboratory headcount was reduced from 20 testing analysts to 15, a 25 percent productivity improvement.

The Control phase was initiated to ensure that the lead time and productivity gains established from the project would not be lost or eroded over time. To ensure that analysts knew exactly what was expected of them, the team designed set roles which clearly showed:

• The activities required for the test role.
• The best order in which to complete them.
• Clear break targets.

The set roles were successful at sustaining the productivity within the laboratory.

The key performance indicators for the process were printed and posted weekly to show exactly how the lab’s cycle time was performing. There was a definite morale boost to the lab to see the lab performance consistently ahead of its targets. Before the project, 66 percent of samples were tested inside the 15-day target time. After the project was completed, the target was changed to 10 days, and all samples were consistently tested within the target time, with an average lead time of 8 days. This translated to an annualized 3.9-fold return on investment for the project.

About the Author

Andrew Harte

From the Lean Six Sigma Briefcase

Operations case study, six sigma quality improvement project – part i, get away from the ordinals, look at the cardinals..

I magine the Bay Area division of a US multinationa l running $4-billion annual revenue. The site has roughly 700 people in R&D and on-market product engineering, production, manufacturing engineering, quality, supply chain management, finance, and ancillary functions. Production does final assembly and test for 6 product families, the largest of which (called PUMA ) produces around 50,000 units a year. Division revenue is around $800-million.

     A training company was engaged to provide Six Sigma education across the product families, including theory and application training and a set of six sigma quality improvement projects. The site leadership team (SLT) selected 30 people from relevant functions to participate in a 40-hour class on site, followed by 6 projects to be completed by teams of 5 people per team. The teams and projects were assigned by the SLT before the class started.

     The expectation was that each project team would define, plan, and execute their six sigma quality improvement project, with periodic consultation with the trainer, and complete their project within 6 months. The reward to team members for successful completion was a Six Sigma Green Belt .

     The PUMA manufacturing line was the subject of one of the more important projects, since its production performance over the past 2-3 years had plateaued at a quality level and cost that were not meeting the site’s objectives. The site operating procedure had each business unit report quality as measured by overall process yield in a meeting held every month. A set of standard reports used data that was uploaded to the Factory Information System (FIS) at the completion of each test or inspection operation and compiled reports by month for each product line, in the form of bar graphs showing overall yield and the top 3 failure modes identified for each product for the month. A standard report had an 8-month running record of yield, and the Top 3 failure summary for the current month.

      The PUMA Six Sigma team included a senior process engineer as leader , a PUMA production line technician, a quality engineer, an R&D mechanical engineer, and a buyer from the supply chain organization. None had experience with Six Sigma techniques prior to participating in the 40-hour class. The team encountered some difficult problems from the start due to some data reporting issues, complicated by the model mix within the PUMA family.

     Two months into their six sigma quality improvement project, the team said they were stuck; the team leader asked me to review what they had been doing and advise them on how to proceed. I worked with the team for 6 weeks, helping to revise their project plan and delve deeper into the production data to turn the data into actionable information . Here, I’m summarizing what I found and what the team changed in order (ultimately) to succeed.

O ne of the most important Six Sigma quality improvement tools is the framework, or methodology, referred to by the acronym DMAIC . The ‘D’ in DMAIC is ‘Define.’ As a result of my review, the first recommendation was to re-do their Problem Definition, which was written as:

     “Improve the overall PUMA process yield for the top 3 failure modes.”

     This is actually not a problem definition, but rather is a broad, non-specific desired end result, with the problem implied. For several weeks they had been trying to improve production yield by tracking Top 3 failure modes by week using the format of the standardized monthly report. But every week they found a different “Top 3.” Sometimes the same 3 failure modes appeared but in a different order. Sometimes new modes would occur once and not again, or not often. Because of the unclear problem statement, the PUMA Green Belt team was running in endless circles.

     They (now “we”) needed to get away from the ordinals (1 st , 2 nd , 3 rd , etc.) and look at the cardinals (7%, 5%, 2%, etc.).

     With this new insight, the team rewrote the Problem Definition as:

     “The ‘ PUMA-Wireless’ process failure rates for failure modes FM A , FM B , and FM C  are too high.”

Depiction of the 6Sigma framework for process improvement referred to as ‘DMAIC.’ 

T his properly defines a problem, not a future state. Also, it focuses on the highest volume configuration of PUMA, the wireless model, which comprised 69% of annual production, rather than conflating all 5 PUMA models. (The others are PUMA-Standalone, PUMA3-Wireless, PUMA-Europe and PUMA3-Europe. The models all had differences in mechanisms, AC power, electronics, software, networking, and process flows). Thirdly, it focuses on the 3 most prevalent failure modes seen during recent months as a baseline, instead of chasing the changes in failures that occur day-by-day due to common cause process variation .

     And very deliberately, it shifts focus to the actual number of events per failure mode and the percentage of total production for each one – the cardinal numbers – so that meaningful reductions can be made and measured (The ‘M’ in DMAIC).

     After some discussion and debate, the clarified Problem Definition led into the Project Objective statement, which was:

     “Reduce the PUMA-Wireless failure rates of FM A , FM B , and FM C  by 50% from current levels.”

     At the time, the 4-month average failure rates for these three failure modes were:

     FM A: 7.3%  –> New objective: 3.6%      FM B: 5.2%  –> New objective: 2.6%      FM C: 2.7%  –> New objective: 1.3% Total 15.2% yield loss for these 3 failure modes combined. Thus, the objective is 7.6% or lower combined failure rate for the 3 failure modes. (The overall yield loss for all failure modes, was 22.1%.)

     Granted, we’d actually like the failure rate to be zero, or perhaps at most the Six Sigma objective of 3.4 DPM (defects per million). However, there’s no magic wand. A 50% failure rate reduction is high enough to be meaningful, but not so high it can’t be achieved in a reasonable time frame.

     Achieving this project objective, improving the PUMA-Wireless yield by 7.6%, would be a very good first step.

Simplified Pareto chart of the PUMA failures observed over the 4 months prior to the project inception. The historical data established the baseline for the improvement project.

T he next step in the Six Sigma DMAIC approach, the ‘A’ word, is to Analyze the measured data in a methodical way. We started by creating Ishikawa (fishbone) diagrams for the 3 failure modes – FM A, FM B, and FM C – so that possible causes (and eventually root causes) could be identified. Fishbone diagrams are developed in the manner of brainstorming – identify possible causes that may contribute to the observed failure and record them on the diagram, with the goal being to cite as many contributors as possible, to be evaluated later.

     Note: It’s a common mistake, when brainstorming, to discard an idea prematurely. For example, someone says “that couldn’t happen” and you don’t record it. Record the idea and keep going until all the team’s ideas are on the chart, then consider which ones are highest probability.      What we are after in creating the fishbone is to identify the defects as specifically as possible that could lead to the observed failure mode. The failure mode is not the defect, it is a symptom or pointer to the underlying defect. To eliminate the failure mode, the cause of the defect must be removed or reduced from the product/process.      Typically, a fishbone diagram will identify 15 to 20 possible defects which are then evaluated as to their likelihood of occurrence and of being a cause of the observed failures. 

Six Sigma Quality Improvement Project – Part II

Turning Data into Actionable Information.

T he failure identified as Failure Mode A was related to the flow rate accuracy of a small electro-mechanical pump that is a key sub-assembly of the PUMA product. The fishbone diagram the team constructed had 15 possible causes across the 6 categories selected. [See Sidebar]

     After several hours of discussion, including review of the part and assembly drawings, and three hours on the production floor, the team concluded there were two potential contributors to the observed failure. Remember that it’s possible in many cases for a test failure in a complex system to occur because two or more anomalies happen together.

     In the case of Failure Mode A, one probable cause was a mechanical component (part number 29475) whose specification tolerance was too wide based on its use in the pump; the parts consistently measured within the drawing specification, but the tolerance needed to be tightened in order to reduce the incidence of failure.

     The second probable contributor was related to a custom gage used for measuring and inspecting the fit of 3 pieces after torquing the fasteners during the assembly process. The assembly area actually had 4 theoretically identical gages used for the purpose. The process engineer on the team carefully inspected all of them against the required design dimensions, and found that one of the 4 was slightly smaller in 2 linear dimensions than the others (by less than 0.4 mm), and had one angular dimension that was incorrect as well.

     The following Corrective Actions (CA) were implemented (the “I” in DMAIC) in order to mitigate the probable root causes.

CA #1. Reduce the variation in the part no. 29475 critical dimensions, first by screening parts in stock using a Request for Deviation (RFD), and then by creating a permanent Engineering Change (EC) to tighten the part tolerance. The EC was provided to the part supplier for implementation, including assigning it a new part number (29476) for configuration control.

     CA #2. Remove the incorrect gage from the process, and then perform a gage repeatability and reproducibility (GR&R) analysis on the remaining 3 gages to ensure that all production technicians could build correct assemblies using the gages. Also, the gages were serialized and each assigned to one of the three stations at which the 3-piece assembly and inspection were performed, to help monitor and control performance. Procedures and training were changed to clarify the usage of the gage, include a check of the gage dimensions in the monthly Preventive Maintenance instruction for the line, and to emphasize the importance of properly recording gage measurement data for each PUMA unit built.

     Failure Mode B was related to electronically “gain matching” the measured outputs of a set of amplifiers on a printed circuit board assembly (PCBA). Using 5-Why Analysis, the team discovered that the measurement method specified and used during PCBA-level testing did not properly correspond to the amplifiers’ use in the system.

     The CA was to implement an EC revising 3 component values on the PCBA (with a new PCBA part number for configuration control), and a corresponding EC to the PCBA test procedure and acceptance limits to correspond more closely with the board’s use in the PUMA product.

     Failure Mode C was a secondary failure mode to the mechanical pump failure (FM A). The fishbone diagram for FM C was nearly identical to that for FM A, and the root causes identified were the same, so no additional CA or PA were needed.

     What was the overall result of the changes implemented?  In the first full month of production after all the changes were cut in, the failure rates for FM A, B, and C changed as follows:

     FM A: Before 7.3%   -> After: 3.2%      FM B: Before 5.2%   -> After: 1.8%      FM C: Before 2.7%   -> After: 1.7%

     The total yield loss after the changes were implemented was 6.7% for these 3 failure modes combined, vs. 15.2% before the project. This represented a 56% reduction in the combined failure rates of Failure Modes A, B, and C, against the project objective of a 50% reduction. Success!

     Additionally, Preventive Actions (PA) were identified to review the other PUMA product configurations regarding their usage of these and similar parts, gages, and PCBAs, to reduce or eliminate the same failure modes on those configurations.

     Finally, what did the team do to control the product and process , following implementation of the changes? (Control is the ‘C’ in DMAIC.) One very obvious change after implementing the CA/PA was that the Top 3 Failure Modes at the next several monthly reviews were completely different. Failure Mode FM A dropped from #1 to #4, and FM B and FM C showed up as the 5th and 7th highest failure modes on the Pareto chart.

     The PUMA production process technician was able to continue monitoring the number and percentage of each failure mode routinely, setting up a simple daily statistical process control (SPC) chart for each of the commonly occurring failures, including a lower control limit based on the average and moving range (Xbar-R chart). By doing so, she was able to determine quickly if an out-of-control condition occurred, and investigate probable causes.

     Setting up the SPC charts constituted the completion of the DMAIC process, and the conclusion of the PUMA Six Sigma project team activity. Ongoing production support was taken over by Process Engineering and Quality, with additional training provided to the production technicians who were closest to the day-to-day process.

      Note: the data required to do the SPC analysis had always been available from the FIS system; once the engineers and technicians knew how to chart it and analyze it properly, they could see when action was needed to maintain control, before the yield “went off a cliff.” This is what is meant by “ turning data into actionable information .”

 Note: The “I” in DMAIC is often stated as “Improve.”  However, whether an implemented change results in an improvement is generally not known until after some quantity of product has been assembled and tested.

Some Final Thoughts

L et’s take a look at the big picture – what did this cost the business, and what was the impact of the changes made? Although this case study takes about twenty minutes to read, the actual project took place over about 4-1/2 months and involved 5 people from 3 different functional units, part-time.

     All told, the work took an estimated 600 person-hours – time the people would otherwise have spent in business-as-usual attempts to fix process problems. Adopting the Six Sigma quality improvement approach started moving the organization away from just “fixing” problems, and toward implementing permanent improvements that resulted from deeper understanding of the product and process. Putting these changes in place required no new capex spending, only a few part and procedural changes with no significant cost impact.

     For their effort, they achieved a production yield increase of 8.5 percentage points, meaning that amount of product no longer needed to go through any failure analysis, rework, and retest. The production labor savings amounted to 1.7 hours per failed PUMA unit. At the PUMA run rate of 50,000 units/year, that meant an annual reduction of 4,250 units requiring re-processing, equating to approximately 7,225 production technician labor hours per year.  

     Without question, this is a substantial cost reduction achievement. Keep in mind the original project objective was yield improvement; cost reduction was a by-product. This is actually not unusual when embarking on Six Sigma initiatives.

     There truly is a “ cost of poor quality ;” cost that is hidden because nobody has to write a check for it, or issue a purchase order, or make a ledger entry for it. Frequently, the biggest reductions in direct cost come from eliminating the root causes of chronic production process failures that result in unnecessary disassembly; analysis; work-in-process (WIP) storage, movement, and tracking; rework; retest; and scrap.

     You are presumably building your business for the long term. Six Sigma quality improvement  is a long term initiative. You will not achieve the Six Sigma defect rate of 3.4 DPMO process performance after one, two, or three projects.

     However, by instilling Six Sigma methods into your people’s “mental toolboxes,” a mindset of continuous improvement builds on itself over time and becomes the natural way of working. As the organizational learning increases over months and years, manufacturing yields go up, product costs go down, and customer satisfaction improves.

     Who doesn’t want that?

Feel free to contact me to discuss  the terminology, processes, or tools described in this report, and how to bring the benefits of Lean Six Sigma to your current project. ~ Dann

Open Access is an initiative that aims to make scientific research freely available to all. To date our community has made over 100 million downloads. It’s based on principles of collaboration, unobstructed discovery, and, most importantly, scientific progression. As PhD students, we found it difficult to access the research we needed, so we decided to create a new Open Access publisher that levels the playing field for scientists across the world. How? By making research easy to access, and puts the academic needs of the researchers before the business interests of publishers.

We are a community of more than 103,000 authors and editors from 3,291 institutions spanning 160 countries, including Nobel Prize winners and some of the world’s most-cited researchers. Publishing on IntechOpen allows authors to earn citations and find new collaborators, meaning more people see your work not only from your own field of study, but from other related fields too.

Brief introduction to this section that descibes Open Access especially from an IntechOpen perspective

Want to get in touch? Contact our London head office or media team here

Our team is growing all the time, so we’re always on the lookout for smart people who want to help us reshape the world of scientific publishing.

Home > Books > Applications of Design for Manufacturing and Assembly

Application of Six Sigma in Semiconductor Manufacturing: A Case Study in Yield Improvement

Submitted: 02 March 2018 Reviewed: 21 August 2018 Published: 03 January 2019

DOI: 10.5772/intechopen.81058

Cite this chapter

There are two ways to cite this chapter:

From the Edited Volume

Applications of Design for Manufacturing and Assembly

Edited by Ancuţa Păcurar

To purchase hard copies of this book, please contact the representative in India: CBS Publishers & Distributors Pvt. Ltd. www.cbspd.com | [email protected]

Chapter metrics overview

2,410 Chapter Downloads

Impact of this chapter

Total Chapter Downloads on intechopen.com

Total Chapter Views on intechopen.com

The purpose of this chapter is to outline systematic implementation of the Six Sigma DMAIC methodology as a case study in solving the problem of poor wafer yields in semiconductor manufacturing. The chapter also describes well-known industry standard business processes to be implemented and benchmarked in a semiconductor wafer fabrication facility to manage defect and yield issues while executing a Six Sigma project. The execution of Six Sigma enabled identification of the key process factors, root cause analysis, desired performance levels, and Cpk improvement opportunities. Implementing multilevel factorial design of experiments (DOE) study revealed critical input parameters on process tools contributing to defect formation. Improvement performed on these process tools resulted in in-line defect reduction and ultimately improving final yields.

• semiconductor manufacturing
• design of experiments (DOE)

Author Information

Prashant reddy gangidi *.

• Independent Scientist, California, USA

*Address all correspondence to: [email protected]

1. Introduction

Six Sigma framework is a continuous improvement strategy that minimizes defects and process variation toward an achievement of 3.4 defects per million opportunities in design, manufacturing, and service-oriented industries [ 1 , 2 , 3 ]. Six Sigma practitioners often lead cross-functional teams in an organization to find and eliminate the causes of the errors, defects, lead, and cycle time delays in business processes. With rapid advancements in computers, artificial intelligence, and automotive vehicles, biomedical imaging semiconductor manufacturers find themselves constantly battling the demanding needs of the industry to sustain Moore’s law and manufacture smaller chips to support next-generation software and hardware products. In order to manufacture nanometer range scale chips, there is a tremendous impetus toward developing advanced process control and measurement system capabilities. Defects become a big challenge in the efforts to reduce feature size in most semiconductor fabs as they negatively impact product yields [ 4 ]. Six Sigma methodology is often neglected in most fabs, and this chapter gives an overview of its importance and how it can be implemented to reduce defects with the help of a general case study. This chapter presents the step-by-step application of the Six Sigma define, measure, analyze, improve, control (DMAIC) approach to eliminate defects in a lithography process of a semiconductor manufacturing organization. This has helped to reduce defects in the process and thereby improve the final probe yields on a critical technology node. During the measure and analyze phases of the project, data were collected from the processes to understand the baseline performance and for validation of causes. These data were studied through various graphical and statistical analyses. Chi-square test, ANOVA, design of experiments (DOE), control charts, fishbone analysis, FMEA, etc. were used to make meaningful and scientifically proven conclusions about the process and the related causes [ 5 ].

2. Six Sigma literature review

The primary methodology of Six Sigma is the application of DMAIC problem-solving steps. A brief explanation for each of the steps involved is as follows:

Define (D): The first stage focuses on analysis of customer identification, feedback, and requirements along with forming the project stakeholder team [ 6 ]. The project team looks at critical to quality (CTQ) and cost of quality (COQ) improvement projects that need to be addressed keeping the end goal of customer satisfaction in mind by defining project scope/problem statement and budget scheduling. It is very critical to define an accurate problem statement along with the scope to ensure the Six Sigma project team will invest all the time, skills, and resources in the right direction.

Measure (M ): This is the data collection phase where types of data, measurement scales, and sampling and collection methods are evaluated. All the initial metrics of the business case are established to measure the problem scale [ 2 , 7 ].

Analyze (A) : Measure and model relationships between variables, hypothesis testing, root cause analysis using cause and effect analysis tools such as fishbone/Ishikawa diagrams, 8D methodology, and 5 Whys analysis [ 2 , 7 ].

Improve (I) : Post root cause analysis, this phase tries to understand optimum levels of factors responsible for causing the problem via design of experiments (DOE), giving insights to determine corrective and preventative actions. This stage involves lean strategies such as the Kaizen Blitz, poka-yoke (mistake-proofing), cycle time reduction, etc. [ 7 , 8 , 9 ].

Control (C) : Primary objective in this last phase is to maintain and sustain control over the process and suggest improvement activities to minimize variation and defects. Statistical process control (SPC), total productive maintenance (TPM), and control plan development are some key tools used in the control phase [ 10 ].

3. Six Sigma application to defect reduction in semiconductor fabrication sites (FABS)

In this section, some business process areas have been identified to focus on benchmarking before considering Six Sigma project execution. Once these business process areas are well established, then only deploying Six Sigma teams would be beneficial to see tangible results. Motorola was one of the pioneers of Six Sigma methodology along with General Electric. Apart from Motorola, no other semiconductor manufacturing company has openly advocated the use of Six Sigma but has definitely inherited a lot of concepts and molded them into different terminologies. A big challenge to Six Sigma implementation is management support, and based on historical success rates of such projects initiated at their respective firms, the management decides to stick to their existing problem-solving methodologies or use some concepts from Six Sigma and other techniques used in industries such as aviation and automotive.

The most important goal for any semiconductor fab is to improve the final product yields [ 4 ]. Yield is directly correlated to contamination, design margin, process, and equipment errors along with fab operators [ 11 ]. Figure 1 referenced from Integrated Circuit Engineering Corp. shows the ranking of top yield loss causing problems across various fabs [ 4 ]. Six Sigma DMAIC methodology can be used as an effective quality and reliability management tool to solve most of these issues, and several literature papers in the form of case studies have been published regarding the same.

Figure 1.

Ranking of yield loss causing problems in fabs.

Sources of random defects could be the equipment, fab personnel, process margins, process chemicals and gases, or cleanroom itself. Data collected from Integrated Circuit Engineering Corp. (ICE) over the last three decades have been shown in Figure 2 .

Figure 2.

Bar chart showing wafer contamination source.

Human and cleanroom sources of contamination have been steadily declining due to advanced training in this field being developed over the years at various universities and corporations along with rapid strides in automation and artificial intelligence that have modernized clean rooms and minimized human contact in handling wafers. Engineers and upper-level management of these fabs must adopt a systematic methodology in resolving yield losses that occur due to process and equipment variations, and in this chapter, some basic business processes have been described that must exist in a fab for it to achieve maximum operational efficiency and produce high-quality chips. Six Sigma DMAIC methodology could then be used as and when required to improve these business processes.

3.1. Contamination and control protocols

Semiconductor processing involves several process fluids and gases, especially in lithography, film/metal deposition, etching, and cleaning steps. These fluids and gases contain impurity elements that can be dangerous to silicon devices [ 4 ]. These elements could be classified as the heavy metals, alkali metals, and light elements. Heavy metals such as Fe, Cu, Ni, Zn, Cr, Au, Hg, and Ag could result in wafer scraps and back end yield fallout due to corrosion in electroplating and metal deposition processing steps. Alkali metals such as Na, K, and Li and light elements like Al, Mg, Ca, C, S, Cl, and F could pose processing problems resulting in defects, which could be yield killing [ 4 ]. These elements also sometimes accumulate along the chambers, handlers, chucks, etc. of various equipment used in fabs resulting in tool downtime which greatly affects production schedules. Moreover, these elements could also pose safety problems to fab personnel. To understand potential risks and sources of these impure elements, a highly cross-functional FMEA team can be deployed to map out all the processes where source chemicals and gases are used along with identifying potential fail modes, severity, occurrence, and detection capabilities. The RPN exercise can be continued to drive improvements at each processing step where such impure elements are likely to occur.

3.2. Defect process mapping and yield management system

Defect density is defined as the total number of defects calculated per unit area on the wafer die [ 4 ]. In order to reduce defect density between processes, engineers need to identify the specific process steps, equipment, input materials, etc. that are the major contributors to the defect density. This involves the construction of a detailed process flow diagram for isolated segments of the process and the use of various problem-solving tools such as using the Six Sigma concepts, cause and effect diagrams, design of experiments, Pareto principles, etc. to tie the total defects measured at the end of the process sequence to the likely sources in the process flow. Most cutting-edge fabs have automated scripts using machine learning principles to have correlation between in-line defects and final yield loss. Advanced data mining software can quickly scan through very large data sets involving integrated circuit parameters, processing parameters, equipment parameters, probe bins, defect metrics, etc. to come up with various models which the Six Sigma team can use to infer meaningful results during the analyze phase of DMAIC. Thus, having a good defect management and yield monitoring system while benchmarking to industry leaders will enable semiconductor fabs to execute Six Sigma projects efficiently while maintaining a competitive edge in the market.

3.3. Role of SPC in defect monitoring

Due to the high number of processing steps and the possibility of defects forming from any source, fabs must have particle monitoring (PMON) charts which are effectively attribute charts that track defects per million opportunities (DPMO) on bare silicon wafers to plot particles coming from the equipment. This helps to isolate defect sources solely coming from process equipment and can be tied with regular total productive maintenance (TPM) cycles in the fab. Process engineering/metrology experts must be able to decide the sampling frequency in this case.

In-line defect metrology teams must be able to skillfully partition the line in placing SPC charts to control defect metrics based on historical learnings. Most fabs that do not have Six Sigma experts on their team usually have a hard time in determining the number of control charts and end up oversampling or undersampling. Attribute charts for key defect metrics that have downstream product yield impact or customer reliability issues should be given the highest priority in establishing control charts.

4. Case study

This section describes a case study wherein Six Sigma DMAIC methodology was used to tackle a probe yield issue due to an in-line defect contamination occurring in a lithography process step.

4.1. Phase 1: Define

This phase of the DMAIC methodology aims to define the scope and goals of the improved project in terms of customer requirements and to develop a process that delivers these requirements. The first step toward solving any problem in the Six Sigma methodology is by formulating a team of people associated with the process [ 12 ]. For the case study in discussion, suspect of in-line process step was not known, and only the critical business impacting factor of yield loss data was known. The initial team comprised of a Certified Six Sigma Black Belt (CSSBB) who were the site quality engineering manager, yield engineering managers, failure analysis engineers, and technicians along with defect metrology engineers. Roles of the team members are shown in the project charter ( Table 1 ). Next, the problem statement addressing CTQ and magnitude of the problem was identified. For a span of 13 weeks, one of the factory’s key products had been failing for bin fallout along the edges of the wafer resulting in a yield loss of 7% for dies. Failure analysis team was contacted to perform extensive cross-sectional analysis of the defect location. Based on the information available to the Six Sigma team at this stage, problem statement was defined as follows:

Table 1.

Project charter.

Problem Statement: Defects occurring on about 25% of wafers around the edge result in bin failure and die loss on specific technology node.

Here, the CTQ metric of die yield loss could directly be correlated to the number of such defects forming during in-line manufacturing that cause poor yields which results in delayed shipments and dissatisfied customers. The Six Sigma team’s next tasks will be outlined in the subsequent sections showing measurement, data analysis, root cause drill down, and corrective action implementation.

4.2. Phase 2: Measure

In this phase, data correlation was conducted to see the correlation between in-line defect counts per wafer to the number of failing dies per wafer at the final probe and percentage of edge die yield loss. Results are shown in Figure 4 .

It is evident from Figure 3 , that the correlation between CTQ metric edge die yield losses to the number of in-line defect counts occurring per wafer is linear with the high R 2 -adjusted value approaching close to 1. Six Sigma project team must reduce in-line defect count to less than 50 defects per wafer to have no die yield fallout at the final probe test.

Figure 3.

Regression plot of (a) number of failing die per wafer at final probe and (b) percentage edge die yield loss per wafer to number of defects per wafer in-line.

4.3. Phase 3: Analyze

The analysis phase consisted of searching through brainstorming rounds, the possible factors that may be affecting the electrical performance of the product. This stage of the Six Sigma process improvement methodology is often termed as Thought Process Mapping [ 13 ] wherein process experts and Six Sigma champions assimilate existing facts and data collected so far and look for initial trends and themes to find clues to go after. The factors that were considered most important were raised as hypotheses and tested by several statistical tests.

Wafer fabrication line is partitioned into three modules—front end of line (FEOL), middle of line (MOL), and back end of line (BEOL)—where each module involves complex steps such as lithography, thin-film depositions, etching, planarization, and diffusion. Inspection sampling plans are strategically placed across several processing steps within these three modules considering cost, cycle time, and wafer throughput times. In this case, the project team was interested to see if there was any in-line defect inspection step that could replicate the defect pattern shown on probe bin wafer map. The project team decided to inspect additional sample wafers through this step and perform failure analysis on the defect locations. More in-line inspection recipes were set up strategically right after metal patterning lithography processes to study defect formation and evolution as the wafers progressed through manufacturing steps.

Through in-line inspections set up across these modules, it was observed that the defect under study was first detected after the metal patterning process. Optical image of the defect was taken along with SEM analysis post BEOL to see defect evolution. This gave an initial indication to the Six Sigma team that metal patterning process and perhaps tool variation in lithography must be analyzed further. There was a need for lithography experts to now help the Six Sigma team in root cause analysis, so lithography process engineering manager, two process engineers, and two process technicians were added to the project team. The project charter was revised to include the new members into the stakeholder team.

Since there is a strong clue of the issue coming from the lithography process area, Six Sigma project team decided to add lithography process experts into the stakeholder team. The project team’s next objective was to brainstorm different failure modes that could be occurring with scanner tools in the lithography step and understand root causes from a scientific perspective. For this, the fishbone analysis was used to list several possible root causes across the six Ms—measurement, materials, method, mother nature/environment, manpower, and machine.

Different tools were used to validate the potential causes listed in the fishbone diagram, and a summary of the tools is listed in Table 2 .

Table 2.

Cause validation plan.

Gemba revealed that there was only one resist supplier to the patterning process, so supplier variation is not a root cause. SEM imaging did not reveal any polymer shearing defects. DOE carried out on resist coating process included a multilevel factorial design where coating speeds were varied from low to high to see if defects could be produced, but it was not the case. Fab contamination studies also showed that particles were well within control and environmental impacts to the formation of in-line defects were negligible. Careful review of all SOPs, manufacturing protocols, preventative maintenance log books, shift pass-downs, etc. did not confirm the validation of any cause. Majority of the effort was then spent in analyzing tool-to-tool variation, which was performed by ANOVA.

For confidentiality purposes, the exact supplier/tool names used in the factory are not mentioned in this chapter. There were three major tools in the factory running this product line, which will be addressed as Tools 1, 2, and 3 for analysis. One-way analysis of variation (ANOVA) of defect metric count with tool set was plotted (see Figure 4 ).

Figure 4.

One-way ANOVA for defect metric by tool set.

Tool 1 mean value was not only above the target defect count value of 50 but was also significantly above Tools 2 and 3, clearly indicating a problem with this tool.

4.3.1. Tool toggle statistical significance

Since there are multiple tool sets and data is non-normal, the Wilcoxon method is used for multiple tool set comparisons [ 14 ]. (α = 0.05). H o : Tool 1 toggle is statistically insignificant; H a : Tool 1 toggle is statistically significant. It is observed that p-value is less than 0.05 when Tool 1 is compared with other two tools as per Figure 5 .

Figure 5.

Nonparametric test data comparison.

Based on Wilcoxon test, reject H o and accept H a . Therefore, Tool 1 toggle is statistically significant and the toggle to defect metric is real. Next, the project team was tasked to look at SPC charts of all critical parameters of all three tools. It was found that the parameter scanner speed and exposure dosage of the immersion hood for Tool 1 were out of control (OOC) and mean value higher than Tools 2 and 3 as per the individuals and moving range (IMR) charts (see Figure 6 ).

Figure 6.

IMR chart comparison for scanner speed and exposure dosage by tool set.

Normal quantile plots for all three tools along with process capability index (Cpk) were calculated as shown in Figure 7 .

Figure 7.

(a) Normal quantile plots for scanner speed and (b) for exposure dosage across three tool sets.

SPC charts and normal quantile plots reveal a significant drift in parameter settings for Tool 1 compared to Tools 2 and 3. SPC charts show very tight distribution of points for Tools 2 and 3, but Tool 1 is not only out of spec but also has high amount of wafer-to-wafer variation for scanner speed and exposure dosage.

Out of all the possible failure modes evaluated and tested, it was confirmed that the source of defect could possibly be coming from Tool 1 metal pattern processing step in lithography area due to significant variation in scanner speed and exposure dosage. The theory behind defect formation due to inaccurate scanner speed and exposure dosage is described below which is a commonly observed phenomenon in the industry [ 14 ].

4.3.2. Defect formation theory

This defect is caused by a bubble forming in the scanner just prior to exposure. Light passing through the air bubble instead of the immersion water causes light refraction which creates a dipole. Attenuation of light can be seen outside of the ring as shown in Figure 8 [ 14 ].

Figure 8.

Light diffraction from bubble surface.

The system setup usually comprises a wafer placed on the scanner’s robotic arm which moves at speeds varying from 1100 to 1400 mm/s per the manufacturer as shown in Figure 9 . The space between wafer and immersion hoods (where the light source is located) is filled with water as an immersion fluid to increase image resolution by a fraction equal to the refractive index of the fluid [ 14 , 15 , 16 ].

Figure 9.

Schematic cross section of an immersion lithographic scanning device [ 17 ].

The scanner speed of the stage should be optimized to increase productivity without creating defects on the substrate by losing droplets [ 17 ]. Immersion liquid level could be a source of a bubble inclusion in the immersion space. Fluid behavior in the region of the recess may cause bubbles to form. This bubble may apply a heat load onto a surface onto which it lands, for example, the wafer surface resulting in poor lithographic imaging performance. If the exposure dosage inside the immersion hood is inadequate, bubbles could be entrapped inside the immersion fluid which is water in this case [ 14 , 15 , 16 , 17 ]. If the scanner moves too fast, the bubble extraction seal (BES) will not have adequate time to suck the bubble out resulting in the bubble being left on the wafer edge. BES extracts the bubbles between the scanner and wafer table.

The Six Sigma project team focused on fixing two main issues here contributing to defect formation—(1) inadequate exposure dosage resulting in air bubble entrapment inside the immersion hood and (2) inadequate scanner speed not giving enough time for BES to suck the bubbles out. Tool 1 settings have drifted significantly from other two tools and has a strong correlation to the high defect counts resulting in yield loss. The next step for the Six Sigma team is to identify optimal tool settings to minimize defect count and have all the three tools operating at these settings. This is discussed in the next phase of Improve.

4.4. Phase 4: Improve

In this phase, optimal tool settings for scanner speed and exposure dosage will be derived using the design of experiments (DOE) full factorial design. Corrective actions addressing the root cause will also be discussed in this section.

Output response is the minimum defect count, while the input factors are scanner speed and tool exposure dosage. Scanner speed values can range from 1000 mm/s to 1400 mm/s per supplier, while the exposure dosage range is from 90 to 100 nC/cm. 16 run DOE table in JMP was created and resulted in prediction profiler obtained after the defect count values for all 16 runs were recorded as shown in Figure 10 . Using the maximum desirability function in JMP, optimum settings were found to be the scanner speed, 1178 mm/s, and exposure dosage, 94.2 nC/cm.

Figure 10.

Prediction profiler indicating optimum tool settings for maximum desirability.

Based on the above findings for scanner speed and exposure dosage, appropriate interim and long-term corrective actions were proposed and implemented.

4.5. Phase 5: Control

This is the final phase of the Six Sigma DMAIC methodology. Some of the questions that arise after the four phases of problem-solving methodology are as follows: How can one control and monitor the tool parameter settings in line? How can one monitor the in-line defect rate at multiple steps? The simple answer is via statistical process control (SPC) charts. Actual SPC charts on proprietary software have not been shown, but data was exported to JMP has been shown in Figure 11(a) and (b) post optimal setting discovery and corrective action implementation across all three tools.

Figure 11.

(a) Individual chart for scanner speed and (b) individual chart for exposure dosage.

It is observed that all three tools have mean values for both the critical parameters very close to the desired settings (1178 mm/s for scanner speed and 94.2 nC/cm for dosage) derived using DOE and have much tighter process control with occasional OOC points which will be addressed real time via the corrective actions implemented. To check process capability post improvements, capability analysis was plotted in JMP ( Figure 12(a) and (b) ).

Figure 12.

(a) Process capability analysis for scanner speed and (b) process capability analysis for exposure dosage for Tool 1.

Binomial chart plots and Cpk values being >1.33 (1.88 for scanner speed and 2.7 for exposure dosage) clearly indicate high process capability and stability for the lithography metal patterning process post-tool setting optimization.

4.5.1. Process FMEA and control plan development

Six Sigma project team decided to implement FMEA process and has appropriate corrective actions in place as part of control plan. Design-related failure modes and improvements were escalated to the tool manufacturer, while the fab focused on process FMEA for the metal patterning process. Figure 13 shows the FMEA template for one of the processing steps in the patterning stage (wafer cleaning) which can be used across FEOL, MOL, and BEOL modules. Most of the corrective actions were implemented over 8 weeks, while some of them were part of continuous improvement activities. This FMEA table should be carried out for other subprocess steps involved in the metal patterning process such as resist application, BARC, etc.

Figure 13.

PFMEA snapshot for wafer cleaning in patterning process.

Clearly, the new tool settings have greatly reduced the number of in-line defects occurring post-pattern processing steps. The line was then released to run production lots after 8 weeks of improve and control phase actions. This concludes the final step of the DMAIC methodology. The final conclusions and tangible improvement results are discussed in the next section.

5. Conclusions

Post DMAIC, as the mean defect count was continuously controlled and monitored below 50, the final probe yield test data also showed a significant reduction in die yield loss to almost 0% (100% yield) post-DMAIC implementation ( Figure 14 ).

Figure 14.

Edge die yield loss graph over 26-week time frame.

It can thus be concluded that DMAIC methodology properly executed under an experienced Six Sigma project team with the support of management is a powerful tool that can reduce process variations and improve product yields, eliminating waste and improving customer satisfaction which ultimately has a significant financial impact on the organization. Six Sigma can be used widely in semiconductor manufacturing environments where there is a tremendous need for defect reduction and tighter process control as the industry advances to smaller technology nodes.

Special note

The author would like to inform the readers that data represented in this paper are not the actual values and closely approximated values have been reported to give an understanding of data analysis, interpretation and application of six sigma methodology.

• 1. Cavanagh RR, Neuman RP, Pande PS. The Six Sigma Way. New York: McGraw-Hill; 2014
• 2. Quality Council of Indiana. CSSBB Primer. West Terre Haute, Ind. Quality Council of Indiana; Vol. 42010. 2014. pp. 125-134
• 3. Gutiérrez H, y De la Vara R. Control Estadístico de Calidad y Seis Sigma. México, D.F: Mc Graw Hill Interamericana Editores, S.A. de C.V; 2004
• 4. Yield and Yield Management. Integrated Circuit Engineering Corp (ICE). Retrieved from http://smithsonianchips.si.edu/ice/cd/CEICM/SECTION3.pdf
• 5. Gijo EV, Scariab J, Antony J. Application of Six Sigma methodology to reduce defects of a grinding process. Quality and Reliability Engineering International. 2011; 27 :1235-1237
• 6. ISO/TS 16949:2009. Quality Management Systems. Geneva: ISO; 2008
• 7. George ML. Lean Six Sigma. New York: McGraw-Hill; 2002
• 8. Breyfogle III. Implementing Six Sigma. 2nd ed. New York: John Wiley & Sons; 2003
• 9. Nakajima S. Introduction to TPM: Total Productive Maintenance. Cambridge, MA: Productivity Press; 1998
• 10. Wise S, Fair D. The Control Chart Dilemma. ASQ, Knoxville, Tennessee, USA: Quality Progress; 1998
• 11. Stapper CH, Rosner RJ. Integrated circuit yield management and yield analysis: Development and implementation. IEEE TSM. 1995; 8 :95-112
• 12. Banuelas R, Antony J, Brace M. An application of Six Sigma to reduce waste. Quality and Reliability Engineering International. 2005; 21 :553
• 13. DeLayne Stroud J. iSixSigma. 2018. Retrieved from https://www.isixsigma.com/implementation/project-selection-tracking/use-thought-map-increase-efficiency/
• 14. Western Electric. Statistical Quality Control Handbook. Indianapolis, IN: AT&T; 1996
• 15. Wei Y. Bubble and Antibubble Defects in 193i Lithography. Bellingham, Washington, USA: SPIE; 2008
• 16. ASML. US Patent (US7199858). Lithographic Apparatus and Device Manufacturing Method. 2007
• 17. Riepen M. Contact Line Dynamics in Immersion Lithography. Netherlands: ASML Research

© 2019 The Author(s). Licensee IntechOpen. This chapter is distributed under the terms of the Creative Commons Attribution 3.0 License , which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

Continue reading from the same book

Edited by Ancuta Carmen Păcurar

Published: 03 January 2019

By Martha Roselia Contreras Valenzuela, Alejandro Dav...

1131 downloads

By Jonathan Becedas and Andrés Caparrós

1539 downloads

By Ruta Miniotaite

1200 downloads

Six Sigma Terms & Definitions

Mastering Six Sigma Continuous Process Improvement

When engineer Bill Smith joined Motorola in 1987 as a senior quality assurance manager, he already had 35 years of experience to his name. He was brought in to help establish a permanent culture change at the company, one with an intense focus on metrics, data collection, and more disciplined statistical approaches to quality control methods. The result was Six Sigma , a set of techniques and tools that improve quality by identifying and removing the causes of defects and minimizing variability.

At the heart of this pursuit lies Continuous Process Improvement (CPI)is essential for achieving ongoing, predictable process results. CPI is derived from the Japanese concept kaizen, a word that means ‘improvement’ or ‘change for better.’ Kaizen originated in Japanese businesses after World War II, most notably at the Toyota automotive company, as a quality assurance discipline for eliminating waste and redundancies (lean manufacturing). With the advent of Six Sigma in the 1980s, Kaizen and continuous process improvement became synonymous, and many companies, including Microsoft, General Electric, and Honeywell, have adopted the practice and enhanced their operational efficiency and product quality. 

CPI is not about making one-time changes or massive overhauls to your business. Instead, it’s really focused on creating ongoing, iterative improvements. This may seem abstract, but as a fundamental Lean Six Sigma concept, it actually requires systematically evaluating and enhancing business processes.

On this page:

Understanding the Six Sigma Methodology

Benefits of implementing six sigma, how to implement six sigma continuous improvement, six sigma case studies, overcoming common six sigma challenges, how to create continuous improvement culture, future trends in six sigma continuous process improvement.

Six Sigma is a data-driven methodology that aims to eliminate defects and inefficiencies in any process. It began as a way to improve quality in manufacturing but is today applied to just about anything in business, whether it’s IT, customer service, or finance. The goal is to reduce errors and defects to near zero, aiming for no more than 3.4 defects per million opportunities. Basically, you use Six Sigma tools to analyze processes, identify what is causing defects or variations in the final product, and remove it.

Professionals trained in Six Sigma use a mix of statistical tools, quality management techniques, and business strategies to achieve these goals. Some of the most commonly used include:

• Statistical Analysis Tools such as control charts, regression analysis, and hypothesis testingfor contextualizing data, identifying trends, and predicting patterns.
• Process Mappin g tools like flowcharts and value stream maps to visualize the process steps and identify areas of waste.
• Root Cause Analysis through the Five Whys and fishbone diagrams to identify the underlying causes of problems.
• Design of Experiments (DOE) : This technique allows for systematic changes to input variables to see their impact on output, helping to identify optimal process settings  settings, and ultimately demonstrating causation.
• Lean Tools, including Just-in-Time (JIT), Kanban systems, and 5S methods, to reduce waste and streamline processes.

At this point, you’re probably wondering what kind of roadmap people following while working on a Six Sigma project. Where does one even begin? How do you know when you’ve finished? That’s where DMAIC comes in. The DMAIC approach is how a Six Sigma project gets its structure It’s an acronym that stands for the five phases of the methodology: Define, Measure, Analyze, Improve, and Control.

Define: This is where you figure out exactly what the problem is, set clear goals and decide what success looks like so everyone involved understands what needs to be achieved.

Measure: Now, you gather data related to the problem so you can understand the current situation and later check how much you’ve improved.

Analyze: Dive into the data to find the root causes of the defects or inefficiencies.

Improve: Come up with solutions and try them out. This might involve changing procedures, modifying workflows, or incorporating new technologies, but the goal is the same: make changes that lead to significant improvements.

Control: After you find a solution that works, this step is about making sure the improvements stick. This involves implementing control systems, continuously monitoring the process, and making adjustments as necessary to maintain the gains. Documentation and training might also be part of this phase to institutionalize the improved process. Whatever the fix is, you need to put rules or checks in place to make sure the process stays improved and doesn’t slip back to the old ways.

Enhanced Quality Control

Using statistical tools to understand and control variation helps companies make fewer mistakes. The fewer mistakes, the higher level of quality in their products and services.

Increased Efficiency

Through process mapping and analysis, inefficiencies such as unnecessary steps, redundancies, and bottlenecks are highlighted and removed, making employees more productive and allowing organizations to do more with less and in a shorter time.

Cost Reduction

Fewer defects mean less waste, rework loops, and lower rates of returns or complaints. The better a process is, the more efficiently you can use resources, including materials, energy, and labor, all of which contribute directly to the bottom line.

Customer Satisfaction

Better quality and reliability in products and services lead to higher customer satisfaction . Satisfied customers are more likely to return and recommend the company to others, which can increase market share and revenue.

Identifying Opportunities for Improvement

Savvy leaders should recognize if an issue is significantly impacting their business. Any problem that impacts costs, revenue, customer satisfaction, or compliance to the point that it’s hampering strategic business goals could be worthy of a Six Sigma project.

Set SMART Goals

Specific: SMART goals require clarity and specificity. In Six Sigma, this means defining the project’s objectives clearly. For example, rather than saying “reduce errors,” a specific goal would be “reduce packaging errors by 30%.”

Measurable : A goal must have a way to measure progress so you can later confirm that the implemented changes have sustained the desired improvement.

Achievable: Six Sigma projects often require changes that are feasible within the constraints of existing resources and technology. Setting achievable goals ensures that the team remains motivated and that the project maintains momentum without becoming discouraged by unreachable standards.

Relevant: The goals should align with broader business objectives, such as increasing efficiency, reducing costs, or improving customer satisfaction.

Time-bound: Setting deadlines helps to prioritize tasks, manage resources effectively, and maintain a rhythm that ensures continuous improvement.

Assemble the Right Team

Six Sigma projects are often complex, requiring diverse skills—from process management and statistical analysis to technical and subject matter expertise. Furthermore, Sigma projects require specific roles, such as project sponsors, Champions, Black Belts, and Green Belts. Each role has distinct responsibilities, with Black Belts often leading the project and Green Belts in support roles. The right personnel gives you a strong leader, deep knowledge of Six Sigma methodologies, and the ability to effectively collaborate.

Case Study #1: Starwood Hotels and Resorts

Starwood Hotels, known for brands like Sheraton and Westin, adopted Six Sigma to enhance guest satisfaction and streamline operations. It struggled with inconsistent customer service that hampered the experience of its guests. Starwood integrated Six Sigma practices with its existing management strategies, training over 1,500 employees as Green Belts to execute projects directly related to improving customer experience,  such as reducing check-in times and improving housekeeping services. As a result, guest satisfaction scores went up, and rooms were made available more quickly between guests for new guests, which increased room availability and revenue.

Case Study #2: Mount Carmel Health Systems

Mount Carmel Health System faced challenges related to patient flow, particularly in the Emergency Department (ED). There were long wait times and unhappy patients until the hospital used the DMAIC to improve the triage process in the ED. Teams of healthcare professionals trained in Six Sigma techniques analyzed the existing processes, measured performance, identified bottlenecks, and implemented targeted interventions. After all was said and done, the triage process reduced patient wait times by approximately 50% by allocating resources based on the severity of incoming cases.

The journey of introducing Six Sigma to a business is often fraught with challenges, such as:

Resistance to Change

One of the most significant barriers to implementing Six Sigma is resistance from employees and sometimes from management. Six Sigma often requires changes in existing processes, roles, and even organizational culture. Employees may fear that the changes could lead to job losses or increased workload. Managers may resist relinquishing control or fear that the new processes will expose inefficiencies within their departments. Overcoming this resistance involves clear communication about the benefits of Six Sigma, involving employees in the change process, and providing adequate training and support.

Lack of Resources

Implementing Six Sigma requires a significant investment in training, tools, and sometimes new personnel. Organizations may struggle with allocating the necessary resources, particularly small to medium-sized enterprises with limited budgets. Additionally, without strong support from senior management, Six Sigma projects can flounder due to lack of priority, funding, or engagement. Ensuring management buy-in and aligning Six Sigma projects with strategic business objectives can help mitigate this issue.

Insufficient Training and Expertise

Six Sigma requires specialized knowledge. Failing to invest in proper training or hiring individuals with the necessary expertise can lead to poorly defined project scopes, incorrect data analysis, and suboptimal solutions. Organizations should ensure that they have adequately trained personnel, such as Green Belts and Black Belts, or consider external consultants if internal expertise is lacking.

Sustaining Improvements

Even when improvements are successfully implemented, maintaining these gains over the long term can be challenging. There can be a tendency for processes to revert to their old ways if there isn’t a strong system for monitoring performance and making adjustments as necessary. Continuous training, regular audits, and a culture that values continuous improvement are crucial to sustaining the benefits of Six Sigma.

The true success of Six Sigma extends beyond initial achievements, lying in the ability to sustain these improvements over time. This sustainability is largely driven by the cultivation of a continuous improvement culture, which emphasizes ongoing training, measurement, and communication with staff.

Training and Development

Six Sigma requires a deep understanding of complex statistical tools and methodologies, as well as a mindset geared towards excellence and efficiency. Training programs keep employees up-to-date with the latest tools and techniques while empowering them to identify areas for improvement and take initiative.

Regular Monitoring and Feedback

Key performance indicators (KPIs) show whether improvements are being sustained and if goals are being met. Conduct regular audits and feedback sessions to reinforce a culture of continuous improvement, maintain momentum, and keep employees focused on quality and efficiency.

Integration with Emerging Technologies

Artificial intelligence (AI), machine learning (ML), and the Internet of Things (IoT) can enhance data collection and analysis, making process improvements more data-driven and precise. For example, IoT devices can monitor manufacturing processes in real time, providing immediate data for analysis. leading to faster and more accurate decision-making.

Adaptation to Changing Business Landscapes

Nearly 40 years after its inception, Six Sigma has proven it is flexible enough to adapt alongside new technologies, shifting market demands, and regulatory environments. Even as the pace of business has quickened, Six Sigma has remained relevant by blending with agile methodologies. This hybrid approach focuses on quicker cycles of improvement, frequent reassessment of goals, and more collaborative project management styles, allowing organizations to be more responsive.

From its roots at Motorola in the late 1980s to its widespread adoption today, Six Sigma has demonstrated a profound ability to drive significant improvements even as dramatic changes in technology, management practices, and regulation have spread across sectors. Companies that continue using it to systematically tackle inefficiencies, reduce errors, and drive quality, will see augmented benefits by integrating modern technologies such as AI and IoT. Creating a culture of continuous improvement in your organization will nurture long-term sustainability and competitive advantage even as industries continue to shift in the digital era.

You May Also Like

What is value stream mapping & how is it used in six sigma.

General Business , Six Sigma Certification & Training , Six Sigma Terms & Definitions

Harnessing the Voice of the Customer in Six Sigma: A Comprehensive Guide

Understanding the six sigma metrics that matter, resource center, six sigma articles (all), six sigma certification & training, lean six sigma, six sigma implementation, six sigma specialized (by industry), six sigma green belts, six sigma black belts, six sigma master black belts, business & career optimization, careers in six sigma, six sigma terms & definitions, six sigma tools & templates (free), six sigma videos, featured articles, understanding six sigma part 1 (video), understanding six sigma part 2 (video), understanding six sigma part 3 (video), why is six sigma so effective, the importance of six sigma training, black, green, yellow... what's the difference, limited time: free white belt certification program, more features.

The History of Six Sigma

Originally developed by Bill Smith at Motorola in 1986, the Six Sigma Training program was created using some of the most innovative quality improvement methods from the preceding six decades. The term “Six Sigma” is derived from a field of statistics known as process capability. The term 6 Sigma refers to the ability of manufacturing processes to produce a very high proportion of output within specification. Processes that operate with “six sigma quality” over the short term are assumed to produce long-term defect levels below 3.4 defects per million opportunities. Six Sigma’s goal is to improve overall processes to that level of quality or better.

Information

• Author Services

Initiatives

You are accessing a machine-readable page. In order to be human-readable, please install an RSS reader.

All articles published by MDPI are made immediately available worldwide under an open access license. No special permission is required to reuse all or part of the article published by MDPI, including figures and tables. For articles published under an open access Creative Common CC BY license, any part of the article may be reused without permission provided that the original article is clearly cited. For more information, please refer to https://www.mdpi.com/openaccess .

Feature papers represent the most advanced research with significant potential for high impact in the field. A Feature Paper should be a substantial original Article that involves several techniques or approaches, provides an outlook for future research directions and describes possible research applications.

Feature papers are submitted upon individual invitation or recommendation by the scientific editors and must receive positive feedback from the reviewers.

Editor’s Choice articles are based on recommendations by the scientific editors of MDPI journals from around the world. Editors select a small number of articles recently published in the journal that they believe will be particularly interesting to readers, or important in the respective research area. The aim is to provide a snapshot of some of the most exciting work published in the various research areas of the journal.

Original Submission Date Received: .

• Active Journals
• Find a Journal
• Proceedings Series
• For Authors
• For Reviewers
• For Editors
• For Librarians
• For Publishers
• For Societies
• For Conference Organizers
• Open Access Policy
• Institutional Open Access Program
• Special Issues Guidelines
• Editorial Process
• Research and Publication Ethics
• Article Processing Charges
• Testimonials
• Preprints.org
• SciProfiles
• Encyclopedia

Article Menu

• Subscribe SciFeed
• Recommended Articles
• Google Scholar
• on Google Scholar
• Table of Contents

Find support for a specific problem in the support section of our website.

Please let us know what you think of our products and services.

Visit our dedicated information section to learn more about MDPI.

JSmol Viewer

Multivariate six sigma: a case study in industry 4.0.

1. Introduction

2. methods and materials, 2.1. six sigma’s dmaic methodology.

• Define: problem selection and benefit analysis.
• Measure: translation of the problem into a measurable form, and measurement of the current situation; refined definition of objectives.
• Analyze: identification of influence factors and causes that determine the critical to quality characteristics’ (CQCs) behavior.
• Improve: design and implementation of adjustments to the process to improve the performance of the CQCs.
• Control: empirical verification of the project’s results and adjustment of the process management and control system in order that improvements are sustainable.

2.2. Latent Variable Models

2.2.1. principal component analysis, 2.2.2. partial least squares regression, 2.3. lvms in batch processes, 2.4. software.

• Multivariate Exploratory Data Analysis (MEDA) Toolbox (for Matlab) [ 28 ] for variable and batch screening, and imputation of missing data within a batch.
• MVBatch Toolbox (for Matlab) [ 29 ] for batch synchronization.
• Aspen ProMV for calibration by using synchronized batch data, and data analysis.
• Minitab for control chart plotting.

3.1. Define

3.2. measure, 3.2.1. available data.

• the averaged values for three process variables ( x 1 to x 3 ) for each batch, measured at point (1) in Figure 3 (i.e., the corresponding reactor);
• amounts ( x 4 to x 7 ) and proportions ( x 8 to x 11 ) of some of the most relevant reactants involved in the reaction, measured at point (2) in Figure 3 (i.e., before being introduced into the reactor);
• four categorical variables indicating whether a batch was produced in the first or second reactor ( x 12 ) and the use or not of an auxiliary piece of equipment ( x 13 ), registered at point (1) in Figure 3 ; and whether an excess of accumulated reactant had been recovered or not ( x 14 ), and whether Premix 1 or Premix 2 had been fed to the reactor for the corresponding batch ( x 15 ), registered at point (2) in Figure 3 ;
• the evolution along the complete duration of each batch for 11 process variables ( x 16 to x 26 ), measured at point (1) in Figure 3 , and;
• information on 10 CQC ( y 1 to y 10 ), including the purity of the product of interest ( y 8 ), measured at point (4) in Figure 3 ; and the measure of the total amount of crude coming out of the process ( y 4 ), and its estimation through mass balance ( y 6 ), measured/registered at point (3) in Figure 3 .

3.2.2. Validation of the Data

3.2.3. quantified initial situation and potential causes of the observed problem, 3.3. analyze, 3.3.1. principal component analysis of the summary variables and cqcs, 3.3.2. partial least squares regression to predict the cqcs from the summary variables, 3.3.3. pls-discriminant analysis to identify differences in batches using premix 1 and premix 2.

• Proceeded, at the latest stages of the batch, faster than those where Premix 1 was fed instead ( x 15 = 0), as seen by the negative values for variable ‘warping’ near the end of the batch duration.
• Presented lower (and decreasing) values for variable x 22 (ingredient flow) at the end of the batch.
• Operated at higher values for variable x 23 (ingredient temperature) at the start of the batch, but lower during the middle part of the batch.

3.4. Improve

3.5. control, 4. discussion, 5. conclusions, author contributions, acknowledgments, conflicts of interest.

• Linderman, K.; Schroeder, R.G.; Zaheer, S.; Choo, A.S. Six Sigma: A goal-theoretic perspective. J. Oper. Manag. 2003 , 21 , 193–203. [ Google Scholar ] [ CrossRef ]
• Grima, P.; Marco-Almagro, L.; Santiago, S.; Tort-Martorell, X. Six Sigma: Hints from practice to overcome difficulties. Total Qual. Manag. Bus. Excell. 2014 , 25 , 198–208. [ Google Scholar ] [ CrossRef ]
• Reis, M.S.; Gins, G. Industrial process monitoring in the big data/industry 4.0 era: From detection, to diagnosis, to prognosis. Processes 2017 , 5 , 35. [ Google Scholar ] [ CrossRef ] [ Green Version ]
• Ferrer, A. Multivariate Statistical Process Control Based on Principal Component Analysis (MSPC-PCA): Some Reflections and a Case Study in an Autobody Assembly Process. Qual. Eng. 2007 , 19 , 311–325. [ Google Scholar ] [ CrossRef ]
• Peruchi, R.S.; Rotela Junior, P.; Brito, T.G.; Paiva, A.P.; Balestrassi, P.P.; Mendes Araujo, L.M. Integrating Multivariate Statistical Analysis Into Six Sigma DMAIC Projects: A Case Study on AISI 52100 Hardened Steel Turning. IEEE Access 2020 , 8 , 34246–34255. [ Google Scholar ] [ CrossRef ]
• Ismail, A.; Mohamed, S.B.; Juahir, H.; Toriman, M.E.; Kassim, A. DMAIC Six Sigma Methodology in Petroleum Hydrocarbon Oil Classification. Int. J. Eng. Technol. 2018 , 7 , 98–106. [ Google Scholar ] [ CrossRef ]
• Jaeckle, C.M.; Macgregor, J.F. Product Design through Multivariate Statistical Analysis of Process Data. AIChE J. 1998 , 44 , 1105–1118. [ Google Scholar ] [ CrossRef ]
• Höskuldsson, A. PLS regression methods. J. Chemom. 1988 , 2 , 581–591. [ Google Scholar ] [ CrossRef ]
• Wold, S.; Sjostrom, M.; Eriksson, L. PLS-Regression—A basic tool of chemometrics. Chemom. Intell. Lab. Syst. 2001 , 58 , 109–130. [ Google Scholar ] [ CrossRef ]
• MacGregor, J.F. Empirical Models for Analyzing “BIG” Data—What’s the Difference? In Proceedings of the 2018 Spring Meeting and 14th Global Congress on Process Safety, Orlando, FL, USA, 22–26 April 2018; AIChE: New York, NY, USA, 2018. [ Google Scholar ]
• García Muñoz, S.; MacGregor, J.F. Big Data: Success Stories in the Process Industries. Chem. Eng. Prog. 2016 , 112 , 36–40. [ Google Scholar ]
• De Mast, J.; Lokkerbol, J. An analysis of the Six Sigma DMAIC method from the perspective of problem solving. Int. J. Prod. Econ. 2012 , 139 , 604–614. [ Google Scholar ] [ CrossRef ]
• Tomba, E.; Facco, P.; Bezzo, F.; Barolo, M. Latent variable modeling to assist the implementation of Quality-by-Design paradigms in pharmaceutical development and manufacturing: A review. Int. J. Pharm. 2013 , 457 , 283–297. [ Google Scholar ] [ CrossRef ] [ PubMed ]
• Wold, S.; Esbensen, K.; Geladi, P. Principal component analysis. Chemom. Intell. Lab. Syst. 1987 , 2 , 37–52. [ Google Scholar ] [ CrossRef ]
• Abdi, H.; Williams, L.J. Principal component analysis. Wiley Interdiscip. Rev. Comput. Stat. 2010 , 2 , 433–459. [ Google Scholar ] [ CrossRef ]
• Bro, R.; Smilde, A.K. Principal component analysis. Anal. Methods 2014 , 6 , 2812–2831. [ Google Scholar ] [ CrossRef ] [ Green Version ]
• Wold, H. Estimation of principal components and related models by iterative least squares. In Multivariate Analysis ; Krishnaiah, P.R., Ed.; Academic Press: New York, NY, USA, 1966; pp. 391–420. [ Google Scholar ]
• Tomba, E.; Barolo, M.; García-Muñoz, S. General Framework for Latent Variable Model Inversion for the Design and Manufacturing of New Products. Ind. Eng. Chem. Res. 2012 , 51 , 12886–12900. [ Google Scholar ] [ CrossRef ]
• Kourti, T.; Macgregor, J.F. Multivariate SPC Methods for Process and Product Monitoring. J. Qual. Technol. 1996 , 28 , 409–428. [ Google Scholar ] [ CrossRef ]
• Geladi, P.; Kowalski, B.R. Partial least-squares regression: A tutorial. Anal. Chim. Acta 1986 , 185 , 1–17. [ Google Scholar ] [ CrossRef ]
• Barker, M.; Rayens, W. Partial least squares for discrimination. J. Chemom. 2003 , 17 , 166–173. [ Google Scholar ] [ CrossRef ]
• Wold, S.; Kettaneh-Wold, N.; MacGregor, J.F.; Dunn, K.G. Batch Process Modeling and MSPC. Compr. Chemom. 2009 , 2 , 163–197. [ Google Scholar ]
• MacGregor, J.F.; Nomikos, P. Multivariate SPC Charts for Batch Monitoring Processes. Technometrics 1995 , 37 , 41–59. [ Google Scholar ]
• Wold, S.; Kettaneh, N.; Fridén, H.; Holmberg, A. Modelling and diagnostics of batch processes and analogous kinetic experiments. Chemom. Intell. Lab. Syst. 1998 , 44 , 331–340. [ Google Scholar ] [ CrossRef ]
• Kourti, T. Abnormal situation detection, three-way data and projection methods; robust data archiving and modeling for industrial applications. Annu. Rev. Control 2003 , 27 II , 131–139. [ Google Scholar ] [ CrossRef ]
• González-Martínez, J.M.; De Noord, O.E.; Ferrer, A. Multisynchro: A novel approach for batch synchronization in scenarios of multiple asynchronisms. J. Chemom. 2014 , 28 , 462–475. [ Google Scholar ]
• Kassidas, A.; MacGregor, J.F.; Taylor, P.A. Synchronization of Batch Trajectories Using Dynamic Time Warping. AIChE J. 1998 , 44 , 864–875. [ Google Scholar ] [ CrossRef ]
• Camacho, J.; Pérez-Villegas, A.; Rodríguez-Gómez, R.A.; Jiménez-Mañas, E. Multivariate Exploratory Data Analysis (MEDA) Toolbox for Matlab. Chemom. Intell. Lab. Syst. 2015 , 143 , 49–57. [ Google Scholar ] [ CrossRef ]
• González-Martínez, J.M.; Camacho, J.; Ferrer, A. MVBatch: A matlab toolbox for batch process modeling and monitoring. Chemom. Intell. Lab. Syst. 2018 , 183 , 122–133. [ Google Scholar ] [ CrossRef ]
• Box, G.E.P.; Hunter, W.G.; Hunter, J.S. Statistics for Experimenters: Design, Discovery and Innovation , 2nd ed.; John Wiley and Sons: Hoboken, NJ, USA, 2005. [ Google Scholar ]

Click here to enlarge figure

Share and Cite

Palací-López, D.; Borràs-Ferrís, J.; da Silva de Oliveria, L.T.; Ferrer, A. Multivariate Six Sigma: A Case Study in Industry 4.0. Processes 2020 , 8 , 1119. https://doi.org/10.3390/pr8091119

Palací-López D, Borràs-Ferrís J, da Silva de Oliveria LT, Ferrer A. Multivariate Six Sigma: A Case Study in Industry 4.0. Processes . 2020; 8(9):1119. https://doi.org/10.3390/pr8091119

Palací-López, Daniel, Joan Borràs-Ferrís, Larissa Thaise da Silva de Oliveria, and Alberto Ferrer. 2020. "Multivariate Six Sigma: A Case Study in Industry 4.0" Processes 8, no. 9: 1119. https://doi.org/10.3390/pr8091119

Article Metrics

Article access statistics, further information, mdpi initiatives, follow mdpi.

Subscribe to receive issue release notifications and newsletters from MDPI journals

Case Study: Six Sigma for Small Business

Six Sigma has proven to work for huge companies like Motorola and GE, which accumulate a lot of waste and redundancy because of their sheer size. But what about smaller organizations? What about local businesses?

What about your company?

Is Six Sigma worthwhile for smaller institutions who don’t have hundred-man teams, or thousand-step processes?

Well, in October 2017, three people asked that same question. They conducted a study, and they published their findings in the Advances of Mechanic Engineering section of  SAGE Journals .

Two of the authors – Murilo Riyuzo Vendrame Takao and Iris Bento da Silva – work in mechanical engineering at the University of São Paulo, in São Carlos Brazil. The other author, Jason Woldt, teaches management classes at the University of Wisconsin-Platteville. They put their heads together to create a comprehensive study on the effects of Six Sigma, as it applied to one specific small-to-medium-sized enterprise…

A plumbing product distribution business.

Spoilers: Six Sigma works.

It has worked for huge businesses like General Electric, and it still works for small- and medium-sized enterprises (SMEs) like your neighborhood lemonade stand.

“This article uses a case study highlighting the implementation of Six Sigma methodology in a North American manufacturer of plumbing products (SME). Each step of the process is properly described, and the results are also presented,” the authors said.

“We conclude that it is possible to identify the improvements and benefits achieved by the implementation of the Six Sigma quality program in an SME environment.”

How did they reach this conclusion? What did they find?

The Six Sigma Difference

They discovered that Six Sigma is different from other quality management programs because of the structured application of its tools and procedures (and, specifically, how those tools integrate with the goals of an organization).

These tools are used to facilitate each step of DMAIC – a project development framework, and a tent-pole of Six Sigma. It stands for…

Define: Figure out the scope and importance of your project, identify the needs of your consumers, and then assemble the team responsible for the project’s execution.

Measure: Pinpoint the problem you’re trying to solve, gather all the data you need, determine priority problems, and establish goals.

Analyze: Discover the cause of the priority problems and figure out where the problems start.

Improve: Propose, evaluate, and implement solutions to priority problems.

Control: Maintain the scope of the long-term goal, monitor performance, and take corrective action to keep on track.

Video: What is Six Sigma?

Levels of Six Sigma

DMAIC works across all levels and scopes of Six Sigma projects and practitioners. And for your reference, Six Sigma features a hierarchy of six components:

White and Yellow Belts: those practitioners who are trained in the basic tools of Six Sigma.

Green Belts: those practitioners dedicated to improvements within a project.

Black Belts: those practitioners who lead projects and train staff.

Master Black Belts: those practitioners who connect the general management of Six Sigma projects to the people responsible for the improvement projects.

Champions: members of the executive committee.

Sponsors: those who promote and define the guidelines for Six Sigma implementation.

The Case Study

There are dozens of tools that can be used during DMAIC, and the research dives into their case study to show a few tools in action.

The case study covers a period of about 18 months, following (as previously mentioned) a plumbing product distributor. The company wasn’t being well-received by its customers, and it endeavored to find out why.

Enter the Define phase. One of the tools they used was called voice of the customer (VoC), which defines the needs and requirements of your customer base. It’s a very important tool for a company that’s not getting a lot of positive reviews. For the case study, VoC showed that customers expected prompt delivery, correct product selection, and a knowledgeable distribution team.

So, with their problem discovered, they ventured into the Analyze phase, where they worked to answer one question – why was their delivery so slow, compared to their competitors? They brainstormed causes, and came up with four potential causes: (1) the accuracy of the sales plans, (2) safety stock issues, (3) vendor delivery performance, and (4) falling behind the manufacturing schedule. They conducted regression analysis on all potential causes, to see which one would cause the most trouble. And they found it. After creating a Pareto diagram , they realized that 74% of their sales came from only 21% of their products – and there wasn’t enough safety stock to get those in-demand products to all the customers who wanted them.

That led to the Improve phase, where they aimed to solve the problem. They started by implementing a monthly demand review, to make sure the in-demand products stayed in-demand, and it wasn’t a one-time fluke. The second measure was to actually order and provide the customers with the products they wanted.

The Control phase was simple. They wanted to make sure their solutions worked for as long as possible, so they created plans to monitor sales on their bestselling 21% of products (to make sure they weren’t exceeding or under-supplying demand). And every year, they’d review how well those products sold; if a product started following out of high demand, they could replace it with a product that was coming into high demand.

The Results

After 18 months with the plumbing product distributor, the researchers came to a confident conclusion.

“This case study illustrates that quality management and its tools should be increasingly adopted regardless of whether they are SMEs or large companies. Thus, in order to achieve competitiveness, the Six Sigma methodology should be much more applied in the SMEs, due to the interrelationship with the stakeholders and limited use of consultancies.”

Using Six Sigma principles , the company in the case study increased their annual sales by $248,034. They reduced delivery time by more than four full days.

The Takeaway

This research is another point in favor of process improvement methodologies. It doesn’t matter how big your company is, how many employees you have, or how much revenue you gross every year.

All. Companies. Have. Processes.

Whether you’re distributing plumbing supplies, making billion-dollar acquisitions, or selling lemonade on the street corner, Six Sigma is absolutely worth looking into.

Home > Learn More About Six Sigma Green Belt > Microsoft Case Study: The Six Sigma Process in 2024 [Updated]

Microsoft Case Study: The Six Sigma Process in 2024 [Updated]

Free Counselling :

IN +91 9899577620

US +1 2093823469

Table of Contents

The power of synergy!

Synergy – the bonus that is achieved when things work together harmoniously- Mark Twain

Microsoft Corporation, the leading developer of personal computer software systems and applications is today a household name worldwide. The company also publishes books and multimedia titles, produces its own line of hybrid tablet computers, offers email services,  sells electronic game systems, computer peripherals,  and portable media players. 

Lean Six Sigma Green Belt Certification Training

45-min online masterclass with skill certification on completion

Mentored By Chetan Bhagat

Access Expires in 24Hrs

Register Now for Free

Upcoming Batches of Six Sigma Green Belt Certificate :-

With their offices throughout the world, research and development center at its corporate headquarters in Redmond Washington, the company also operates research labs in Cambridge, England, Beijing, China, Sadashivnagar, Bangalore, India, Santa Barbara, California  Cambridge, Massachusetts  New York, New York, and Montreal, Canada

Early History 

In 1975  Bill Gates and Paul G. Allen, two young college-going friends from Seattle, converted BASIC, a popular mainframe computer programming language, for use on an early personal computer (PC), the Altair. 

Shortly thereafter, they founded Microsoft, deriving the name from the two words e.g. microcomputer and software, and combining the first words named their company as MICROSOFT.

Truly a star was born by the name MICROSOFT that changed the history of the world.

For the next few years, they refined BASIC and developed other programming languages alongside.

 In 1980 IBM ( International MachinesCorporation) asked Microsoft to produce the essential software, or operating system for its first personal computer, the IBM PC. 

In a dramatic move, Microsoft purchased an operating system from another company, modified it, and renamed it MS-DOS  (Microsoft Disk Operating System). This was yet another turning point in the history of Microsoft. MS-DOS was released with the IBM PC in 1981 which set a trend thereafter and most manufacturers of personal computers licensed MS-DOS as their operating system. 

This generated vast revenues for Microsoft. 

By the early 1990s, it had sold more than 100 million copies of the program and defeated rival operating systems such as CP/M  and IBM OS/2. Microsoft further strengthened its position in operating systems with WINDOWS. The third version of WINDOWS, released in 1990, gained an immense following due to its speed in operating and ease of learning.

A revolution was created with more and more users worldwide used and propagated the Microsoft WINDOWS.

Microsoft started becoming a popular choice against Apple Computer’s Mac.

Simultaneously Microsoft also researched and developed other software e.g.  word -processing and spreadsheet programs which outsmarted old rivals Lotus and WordPerfect in the process.

The march of Microsoft was relentless and Microsoft dramatically expanded its electronic publishing division, which was already created in 1985 and was notable for the success of its multimedia encyclopedia ENCARTA.

MICROSOFT & SIX SIGMA

What is Six Sigma?

Six Sigma is a statistical term that measures how far a given process ( to develop and deliver the product/services) deviates from perfection in bringing the ultimate joy to the customer.

Six Sigma was originally developed by Motorola in 1986  by  Jack Welch who made it a central focus of his business strategy at General Electric in 1995.

Microsoft experience of Six Sigma is an outstanding case study. The secret behind the success of their Sharpe software and products/ services using Six sigma is exemplified by the fact that Microsoft is said to have become the poster child for Six Sigma implementation.

 What is the need for Six Sigma?

Six Sigma seeks to improve the quality of process outputs by identifying and removing the causes of defects (errors) and minimizing variability in manufacturing and business processes. 

The goal is to deliver flawless products/services to the customer/end-user to give him ultimate joy while consuming and give him satisfaction. It also builds a loyal customer base and combats competition. 

Six Sigma also standardizes the production and logistics of the company which has its own benefits.

How does Six Sigma Work?

Six Sigma is defined or implemented by applying DMAIC in an organization.

DMAIC is an acronym for five interconnected phases: Define, Measure, Analyze, Improve, and Control.

D stands for Define.(Define project boundaries ­ the stop and start of the process)

M stands for measure (Measure the performance of the Core Business Process involved.)

A stands for Analyse (Analyze the data collected and process map to determine root causes of defects and opportunities for improvement.)

I stands for Improvement (Identify gaps between current performance and goal performance)

C stands for Control.(Control the improvements to keep the process on the new course.)

What does DMADV  stand for in Six Sigma

DMADV is an abbreviation for;

*Analyze, 

How can it benefit an organization

Since it is a customer-driven concept to bring delight to the customer it improvises the processes involved in developing the product/services in an organization. Each process is micromanaged and the defects are eliminated during each process.

The ultimate result is evolving a quality-oriented product. The entire organization is affected by this quality culture and delivering quality becomes the common language at the organization.

Is Six Sigma successful

 Yes! Six Sigma is extremely successful. Most Fortune 500 companies implement this as the concept itself builds a strong brand image of the company. Consumers are sure of a quality product/services delivered to them. 

Not only that in the case of dissatisfaction the company owns the responsibility by either taking it back or refunding the money according to their policy. The return/refund policy is well defined and the customer is well educated on the policy.

How does Six Sigma work

The Six Sigma work on consciously applying the core principles e.g.

• Always focus on the customer.
• Understand how work really happens.
• Make your processes flow smoothly.
• Reduce waste and concentrate on value.
• Stop defects through removing variation.
• Get buy-in from the team through collaboration.
• Make your efforts systematic and scientific.

Experience of Microsoft  with Six Sigma

While the success of Microsoft arguably leveled off in the mid-90s due to competition with Apple, Microsoft made some dramatic changes. They refocused their strategy for the better, turning operations toward developing consumer and enterprise web-based software solutions.

The mid-90s also ushered the era of the Internet and it was a kind of huge paradigm shift for Information Technology. The marketplace not only offered huge potential for the IT products manufacturers, the challenge to manufacture quantity and quality IT products poised a greater challenge to them.

 Microsoft recognized both the potential and challenge and adopted it to increase efficiency.

Six Sigma was a natural choice for Microsoft to meet the demand challenges.

Microsoft adopted Lean Six Sigma  to enhance its capabilities by

• PROCESS IMPROVEMENT.
• WASTE  ELIMINATION
• CUSTOMER RELATIONS.

Process Improvement 

Process Improvement at Microsoft was implemented by DMAIC for quality improvement and problem reduction for existing processes.

Waste Elimination

Waste elimination is important savings for an organization which ultimately builds the profit for an organization. Process owners are always looking for ways to prevent waste.  Waste is an action or a step in a process that does not add value for the customer virtually, but the elimination of waste adds profit for the organization that can be passed to the customer which can benefit the customer eventually. Lean Six Sigma solutions at Microsoft played a vital role to eliminate the waste.

There are eight major types of waste that were included at Microsoft to raise the efficiency 

• Defects – A defect occurs when a product or service falls short of the customer’s expectations.
• Overproduction – also incur losses by making more products than customers demand. It leads to squandered resources and unnecessary inventory carrying costs. Both of these factors cost money and reduce the profitability of the organization. The long-term cure for overproduction is to implement a pull system that changes production philosophy from made-to-stock to made-to-order. Microsoft tuned this with the needs of the customer and made an easier time with scheduling and forecasting to prevent large inventories.
• Waiting – Although this may seem harmless, it is expensive. Material and employees that sit idle incur losses and add no value which can be passed on to the customer.  This was implemented at Microsoft by eliminating bottlenecks in the production process and improving communications that helped reduce idle time.
• Non-Value Added Processing – Inspecting the product is an important step in the process when the product is made right the first time and subsequently repeated in the process and productions. This is eliminated by applying Lean Six Sigma. Yet another step towards minimizing losses and adding profit to the organization which can build net worth or may be utilized for the benefit of the customer. Microsoft implemented this by Using Value Stream Mapping to analyze processes to find how much value each step gives to give quality products/services to the customer. Evaluating the process and the production every step helped identify wasted effort.
• Transportation and logistics – play an important component in adding cost in making a product/service available to the customer. While in time every time deliverance of product/service enhances the satisfaction of a customer it builds great confidence in the psyche of the customer. Delivery of products with their range and ideal product mix makes lot profitable and easier for the dealer/distributor network and inventory control at retail outlets. Also in house production line and sequence saves costs which can add value to the profit or passing value to the customer. The Lean Six Sigma implementation has enabled these cost savings to Microsoft which has high production and service output.
• Inventory – Inventory build-up occupies space and consumes money. It also encourages other types of waste from overproduction, higher defects and non-value added processing. Eliminating work in progress by reducing gaps in the production process and improving forecasting methods Microsoft reduced the need for inventory at all levels.
• Motion – The production process flow completed with the minimum amount of motion possible helps save energy consumption. Using more motion than is needed is a waste of resources. Online assembly work minimizing motion also helps reduce the cost of production. Machines and work stations floor plans designed to minimize movement have helped ease working at Microsoft productions unit saving cost to add profit to the organization.
• Unused Employee Talent – Human relation development activities have greatly enhanced the work environment and foster Employees to generate new ideas and innovation. Microsoft has encouraged human relation development activities at all workplaces and created a remarkable congenial atmosphere to foster great innovati

Visit The Other Courses:

Six Sigma Green Belt Certification

Six Sigma Black Belt Certification

Six Sigma Master Black Belt Certification

Customer Relations

Microsoft has greatly emphasized its customer relations in their success stories. The company walks the extra mile in not only bringing customer satisfaction but takes it to the next level of customer delight with exclamation mark AHA! by the customers.

Effective customer service management needs to reduce overall costs while increasing overall customer experience and value to the customer. To bring joy to the customers Microsoft has been using the use of lean six sigma as a model for customer service management decisions.

The lean customer service organization

A lean approach to customer service by Microsoft is envisaged by evaluating each process involved in customer care and identifying waste or inefficiencies that add costs to the organization. It eventually involves setting the goal of only 3.4 errors per million customer service opportunities.

This is achieved by eliminating slow or inefficient systems, unorganized resources, or lack of training or missing skills among customer service team members.

The Six Sigma approach to perfect customer service

Microsoft customer service is built on four major customer service core components. It denotes exceptional customer experience using Microsoft products/services.

1. Customer service tasks

This involves Customer service tasks performed on the day-to-day actions and processes that customer care representatives perform for customers each day over a phone or in personal interactions. They are performed with responsive, management, courteous tone, and giving options to the customers.

2. Customer service treatment

Customer service representatives are trained  to Reducing negativity and  encouraging the creation of positive emotions to ensure that the recipe for customer loyalty is mixed with each customer interaction,

3. Customer service metrics

Customer service metrics comprises of 

• getting customer action and customer emotion right,
• adding up to the desired outcome
• increasing customer retention
• increasing overall customer conversion

All in all, does it set a standard that is an advantage that can be used for future customer acquisitions. Getting perfect service metrics means measuring the effect of planning and executed action. 

4.  Customer service training

If the metrics show the desired results from the customer service strategy implemented at Microsoft, it will further ensure that the cycle is perpetuated and perfect training is evolved.

Perfect training will further ensure that existing team members refine their ability to execute the overall service strategy and that new customer service team members quickly gain the necessary vision and develop the abilities to be effective in their actions, emotions, and understand the metrics or deliverables that determine success.

How did Microsoft use Lean Six sigma?

Microsoft used Lean Six Sigma tools like value stream mapping to analyze customer demand and satisfy them This enabled Microsoft to develop their Windows CE OS platform which is compatible with networking noncomputer devices, televisions, and personal digital assistants, etc.

The CE OS platform also paved the way for future successes at Microsoft.

What is Microsoft/Six Sigma in the present days?

Microsoft has always been a reflexive and responsive organization, adapting to emerging technologies and new market opportunities, whether it is through process improvement, waste elimination, or customer relations

Throughout the late 2010s, Six Sigma has helped Microsoft to reorganize their leadership and management structure,  increasing sales for portable devices like smartphones and tablets and setting the benchmark for freshers’ understanding their roles and goals to bring value to their multitude buyers worldwide. 

What is Microsoft After Bill Gates?

In 2000 company cofounder Gates relinquished his role as CEO of Microsoft to Steve Ballmer, whom Gates had met briefly at Harvard University in the 1970s. He handed over the title of chief software architect in 2006 to Ray Ozzie, a chief developer of the computer networking package Lotus Notes in the 1990s. In 2008 Gates left the day-to-day running of the company to Ballmer, Ozzie, and other managers, though he remained as chairman of the board. Ozzie stepped down in 2010, and longtime Microsoft executive Satya Nadella replaced Ballmer as CEO in 2014.

Microsoft has a rich legacy of being a customer-oriented company. The trend set by Bill Gates will continue as the system will always dominate the culture exemplified by him.

Recommended Reads

• Best Six Sigma Course in India
• Best Six Sigma Courses in Bangalore
• Best Six Sigma Black Belt Courses in Delhi
• Best Six Sigma Courses in Chennai
• Six Sigma Black Belt Courses in India
• Six Sigma Certification Costs

Recommended Programs

Ranked No.1 Six Sigma Certification in India | Aligned to IASSC Book of Knowledge | Combining Lean and DMAIC Methodology to Impart Key Skills | Gain Experience of 12+ Projects | Both Classroom and Live Online Options Available

Lean Six Sigma Black Belt Certification Training

Ranked No.1 Six Sigma Black Belt Certification in India | 9361+ Participants Trained | Aligned to IASSC Book of Knowledge (BOK) | Gain Advanced Expertise Over Lean and Six Sigma Methodology| Gain Experience of 12+ Projects | Both Classroom and Live Online Options Available

Lean Six Sigma Master Black Belt Certification

Step-in to a new designation of being Explicit Quality Professional | Get acknowledged as a Lean Six Sigma Evangelist | Connect to the rarest community of worldwide Black Belt specialists | Validate your professional skills in leading intricate projects | Execute Lean methodologies with perfection.

Recommended videos for you

Six Sigma Green Belt Training

Six Sigma Green Belt Training Tutorial

Certified Six Sigma Black Belt Course

Best Six Sigma Black Belt Training

E&ICT IIT Guwahati Best Six Sigma Green Belt Program

Ranks Amongst Top #5 Upskilling Courses of all time in 2021 by India Today

Top 14 Six Sigma Certification in Bangalore: 2024 [Updated]

Top 15+ SAP EHS Training Courses in India: 2024

Related posts.

What Is Six Sigma Certification: Black Belt, Yellow Belt & Reasons to Get Certified

What is the Six Sigma Course & The Benefits?

Quality Circle- Definition, Benefits, and Process

7 Basic QC Tools For Six Sigma Projects in 2024

10 Best Six Sigma Certification Courses in Nigeria

Walmart Case Study: Lean Six Sigma Implementation in 2024

Our Career Advisor will give you a call shortly

Just purchased a course

Type above and press Enter to search. Press Esc to cancel.

Noida Address:

Henry Harvin House, B-12, Sector 6, Noida, Uttar Pradesh 201301

FREE 15min Course Guidance Session:

Lean Six Sigma Training Certification

• Facebook Instagram Twitter LinkedIn YouTube
• (877) 497-4462

What is The Kanban Maturity Model? How Does it Work and More

June 27th, 2024

Businesses relentlessly pursue stronger workflows, market-tuned flexibility, and customer-centric value. The Kanban Maturity Model emerges as a robust compass, steering teams through a step-by-step refinement journey leveraging Kanban principles.

Crafted by lean/agile experts, it offers a full roadmap for weighing current aptitude, pinpointing enhancement avenues, and driving agility plus streamlining through gradual progress.

By progressing across its 7 development tiers, teams progressively master workflow direction, collaboration, transparency, limiting works sprawl, achieving ultimate smooth flow and value output.

Not one-size-fits-all, the framework customizes to every organization’s uniqueness. Still, it provides a well-structured approach to implementing Kanban practices , cultivating change, and a drive for constant upgrading through guidance and refinement.

Overall it ignites an evolutionary journey toward excelling at reactivity, optimization, and delivering customer-driven outcomes through disciplined adaptation and non-stop learning.

Key Highlights

• The Kanban Maturity Model offers a methodical path for companies to check and refine Kanban techniques.
• It outlines 7 development stages — each one expanding on the last — letting teams and businesses constantly evolve workflow mastery.
• Adopting this Model empowers agility, optimized processes, and relentless refinement throughout the business.
• It serves as a detailed map for pinpointing upgrade opportunities, adopting industry best practices, and tracking movement along the Kanban journey.
• By progressing through the Model’s stages, teams can boost teamwork, visualize efforts underway, control simultaneity, and arrange methods for peak fluidity delivering top value.
• Not a one-size-fits-all cure, it still ignites an evolutionary motion toward excelling at flexibility, efficiency and fulfilling ever-changing customer needs through disciplined learning and refinement.
• The Model nurtures optimization through clarity, structure, and benchmark-driven motivation toward advancing up the Kanban aptitude ladder over the long haul.

What is the Kanban Maturity Model?

The Kanban Maturity Model provides a step-by-step framework for weighing Kanban usage aptitude and charting the route toward higher capability.

Crafted by experts in lean/agile practices, this model serves as useful guidance for optimization-minded companies.

At its core, the model recognizes upgrading Kanban demands relentless refinement plus organizational evolution over time.

It lays out progressive stages that let businesses enhance techniques, spark collaborative spirit, and ultimately drive better results.

The model acknowledges every company starts in a different Kanban position, with varied know-how, workflows, and cultural preparedness.

By offering a detailed roadmap, it helps pinpoint current standing, grasp linked challenges/prospects and systematically achieve superior skill levels.

As progress accelerates, businesses can expect perks like better workflow visibility, decreased lead times , stronger teamwork, and increased customer-focused output.

The model advocates a full lifecycle method, addressing Kanban’s technical and cultural/change leadership aspects essential for prosperous usage.

Whether just beginning Kanban work or optimizing existing efforts, this framework cultivates constant progress and business transformation through contextualized mastery.

The Seven Levels of Kanban Maturity Model

The Kanban Maturity Model outlines seven distinct levels that organizations progress through as they adopt and master Kanban practices. Each level builds upon the previous one, helping teams and organizations continuously improve their workflow management and achieve higher levels of business agility.

Level 0 – Visualization

The first step is to visualize the existing workflow and make work items and their progress explicit. Teams create a basic kanban board to represent their process and start tracking work items as they flow through the various stages. This provides transparency and highlights potential bottlenecks or constraints.

Level 1 – Kanban Kickstart  

At this level, teams establish work-in-progress (WIP) limits to prevent overloading the system. They also begin measuring lead times and optimizing for flow efficiency by eliminating sources of waste and non-value-added activities. Basic kanban practices like daily standups are implemented.

Level 2 – Kanban Control  

Teams gain control over their process by actively managing WIP limits, buffers, and replenishment policies. Explicit process policies are defined, and classes of service are introduced to prioritize work streams effectively. Feedback loops and continuous improvement practices take root.

Level 3 – Kanban Manageable  

The focus shifts to quantitative management using methods like cumulative flow diagrams and control charts . Processes become more predictable through active risk management, lead time monitoring, and the elimination of variation . Collaboration across teams and departments increases.

Level 4 – Kanban Improving

At this stage, value stream mapping is leveraged to optimize end-to-end workflow across the entire value stream. Systematic experiments drive process improvements using techniques like A/B testing. The organization aligns strategy with portfolio execution using the cost of delay and other economic frameworks.

Level 5 – Kanban Advancing

Organizational mastery of kanban principles leads to strategic initiatives around leadership development, cultural transformation, and business agility.

Roadmaps for continuous process evolution are established based on a long-term vision. Emphasis is placed on learning, coaching, and developing a sustainable competitive advantage.

Level 6 – Kanban Accomplished  

The pinnacle of kanban maturity is where the organization operates as an adaptive, future-proof enterprise.

Kanban capabilities are deeply embedded into the DNA of the organization, allowing it to thrive amidst volatility through rapid sensing and response mechanisms. A culture of relentless improvement is the new normal.

Implementing the Kanban Maturity Model

Adopting the Kanban Maturity Model is an iterative process that requires commitment, patience, and a willingness to continuously improve. It’s not a one-time event but rather a journey of continuous learning and adaptation. Here are some key steps to successfully implement the Kanban Maturity Model in your organization:

• Assess Your Current State Before embarking on the Kanban journey, it’s crucial to understand your organization’s current maturity level. Conduct a thorough assessment to identify strengths, weaknesses, pain points, and areas for improvement in your workflow processes.
• Establish a Guiding Coalition Change initiatives are more successful when championed by a guiding coalition of influential leaders and subject matter experts. This coalition should comprise representatives from various departments and levels within the organization to ensure buy-in and alignment.
• Create a Roadmap Based on your assessment results, develop a roadmap that outlines the specific steps and milestones for progressing through the Kanban Maturity Model levels. This roadmap should be realistic, measurable, and aligned with your organization’s strategic objectives.
• Provide Training and Coaching Effective implementation of the Kanban Maturity Model requires a deep understanding of its principles, practices, and techniques. Invest in comprehensive training programs and coaching sessions to equip your teams with the necessary knowledge and skills.
• Start with Pilot Projects Rather than attempting a large-scale transformation, start with pilot projects or specific teams to test and refine your Kanban implementation. This approach allows you to learn from experience, make adjustments, and build confidence before scaling across the organization.
• Foster Continuous Improvement The Kanban Maturity Model emphasizes continuous improvement as a core principle. Encourage a culture of experimentation, feedback, and adaptation. Regularly review your progress, identify areas for improvement, and make necessary adjustments to your processes and practices.
• Measure and Celebrate Success Define clear metrics and key performance indicators (KPIs) to track your progress and measure the success of your Kanban implementation. Celebrate milestones and achievements along the way to maintain momentum and reinforce the benefits of the Kanban Maturity Model.
• Sustain the Transformation Organizational transformation is an ongoing process, not a one-time event. Ensure that the Kanban Maturity Model becomes ingrained in your organization’s culture and processes. Provide ongoing support, coaching, and reinforcement to sustain the transformation over the long term.

By following these steps and embracing a mindset of continuous improvement , your organization can successfully navigate the Kanban Maturity Model levels and reap the benefits of increased efficiency, productivity, and business agility.

Kanban Maturity Model Practices and Techniques

Implementing the Kanban maturity model requires adopting a set of key practices and techniques. These allow teams to visualize their workflow, limit work in progress, measure cycle times , and continuously improve. 

Visualizing the Workflow

A fundamental kanban practice is creating a visual representation of the workflow, typically using a kanban board.

The board shows the different stages or steps that work items flow through from initial request to final delivery.

Columns on the board represent each process step like “Requested”, “Analysis”, “Development”, “Testing”, etc. This transparency allows the entire team to see the state and progress of work at any given time.

Limiting Work in Progress (WIP) with Kanban Maturity Model

A key practice is establishing explicit WIP limits for each workflow stage. This prevents teams from starting too much work at once and creates a pull-based system where new work is only pulled in when there is available capacity. WIP limits expose bottlenecks and maximize flow efficiency.

Cycle Time Tracking

Teams should measure and optimize for cycle time – the total time it takes for a work item to travel through the whole workflow process. Monitoring cycle times and lead times allows teams to identify process constraints and focus improvement efforts.

Continuous Improvement using Kanban Maturity Model

The ultimate goal of kanban is to enable an organizational culture of continuous improvement. Teams frequently review their workflow, processes, cycle times , quality metrics, etc., and run experiments to optimize and increase delivery flow incrementally.  

Other key kanban mechanisms include:

• Using kanban cards or icons to represent work items
• Implementing WIP swimlanes for work item classes 
• Defining clear entry/exit policies for workflow stages
• Holding regular service delivery review meetings
• Using lead/cycle time charts and cumulative flow diagrams
• Running frequent retrospectives and kaizen events

By adopting and customizing these core practices, teams can effectively visualize their value stream, limit non-value-added work, and continuously improve delivery performance over time.

Organizational Transformation and Change Management with Kanban Maturity Model

Adopting the Kanban maturity model is not just about implementing a new process or workflow. It represents a fundamental shift in how an organization operates and delivers value.

As teams progress through higher maturity levels, wider organizational changes become necessary to sustain improvements and realize strategic benefits.

Change Management

Effective change management is critical for a successful agile transformation using the Kanban method. Organizations must proactively plan for and mitigate resistance to change from individuals and teams.

This involves clear communication of the vision, rationale, and expected benefits. It also requires coaching, training, and addressing concerns to build buy-in and overcome cultural barriers.

Leadership Development using Kanban Maturity Model

Progressing through the kanban maturity levels demands a transition in leadership style from traditional command-and-control to a facilitative, servant-leadership approach .

Leaders must embrace principles of continuous improvement, empower teams, and create an environment conducive to experimentation and learning.

Developing leadership capabilities in areas like systems thinking , coaching, and change facilitation becomes paramount.

Organizational Culture

The higher maturity levels of the model require an aligned organizational culture that reinforces lean-agile values and principles. This cultural transformation involves aspects like:

• Fostering a blameless environment of trust and psychological safety
• Encouraging knowledge sharing and collaboration across boundaries  
• Instilling a mindset of customer focus and continuous learning
• Aligning strategies, policies, incentive structures, and performance management

A supportive organizational culture provides the foundation for teams to optimize value streams and achieve higher levels of business agility.

By proactively addressing change management, leadership development, and cultural alignment, organizations can increase their odds of success with enterprise-wide kanban implementation and agile transformation.

Case Studies and Success Stories of Kanban Maturity Model

To illustrate the power of the Kanban Maturity Model in driving organizational transformation, let’s look at some case studies and success stories:

Toyota Motor Corporation

Toyota is widely regarded as the pioneer of the Kanban method and lean management principles .

Their implementation of Kanban practices dates back to the 1950s and has been instrumental in their rise as one of the world’s largest and most successful automakers.

Toyota’s Kanban system optimized workflow, reduced waste, and enabled continuous improvement across their entire value stream. Their maturity in Kanban practices is a prime example for organizations across industries.

Siemens Healthcare

Siemens Healthcare adopted the Kanban Maturity Model to improve software development processes for their medical imaging solutions.

By implementing Kanban practices like visualization, WIP limits, and flow management, they achieved a 35% increase in throughput and a 60% reduction in lead times .

Their successful Kanban journey highlights the applicability of the maturity model in complex product development environments.

Lockheed Martin

The aerospace and defense giant Lockheed Martin used the Kanban Maturity Model to drive an enterprise-wide agile transformation .

By systematically progressing through the maturity levels, they fostered a culture of continuous improvement , enhanced collaboration, and optimized their program management capabilities.

Lockheed’s case study demonstrates the scalability of the maturity model across large, distributed organizations.

The cloud computing company Salesforce adopted the Kanban Maturity Model to streamline its marketing operations and content production workflows.

By embracing Kanban practices like visual management, WIP limits, and bottleneck management , they achieved significant improvements in cycle times , team productivity, and customer satisfaction.

Salesforce’s success story showcases the versatility of the maturity model across diverse business functions.

Next Steps…

The Kanban maturity model charts a course for constantly developing your Kanban implementation and reaching higher process excellence milestones.

Following the 7 outlined stages lets teams progressively upgrade workflow direction, team synergy, and general business flexibility over time.

It’s crucial to remember maturity is a lifelong journey. Even at the most sophisticated level, aim for persistent optimizations adjusting to fluid customer/market conditions.

Some next actions for promoting a successful, lasting Kanban adoption:

• Regularly weigh your current maturity positioning and pinpoint where to focus efforts next
• Motivate an attitude of continuous studying and experimenting among teams
• Keep training and coaching available to deepen understanding of Kanban principles
• Confirm Kanban aligns with the overarching corporate strategy
• Leverage info and analytics to recognize bottlenecks , refine processes , and make smarter choices
• Participate in communities, events, and cross-company connections to expedite maturation and contribute to the broader ecosystem

Cultivating change consciousness and following the next steps sustains maturity. It reaps the benefits of heightened efficiency, dependability, and corporate agility through relentless evolution.

SixSigma.us offers both Live Virtual classes as well as Online Self-Paced training. Most option includes access to the same great Master Black Belt instructors that teach our World Class in-person sessions. Sign-up today!

Virtual Classroom Training Programs Self-Paced Online Training Programs

SixSigma.us Accreditation & Affiliations

Monthly Management Tips

• Be the first one to receive the latest updates and information from 6Sigma
• Get curated resources from industry-experts
• Gain an edge with complete guides and other exclusive materials
• Become a part of one of the largest Six Sigma community
• Unlock your path to become a Six Sigma professional

" * " indicates required fields

Pardon Our Interruption

As you were browsing something about your browser made us think you were a bot. There are a few reasons this might happen:

• You've disabled JavaScript in your web browser.
• You're a power user moving through this website with super-human speed.
• You've disabled cookies in your web browser.
• A third-party browser plugin, such as Ghostery or NoScript, is preventing JavaScript from running. Additional information is available in this support article .

To regain access, please make sure that cookies and JavaScript are enabled before reloading the page.