problem solving lean

How to Solve Your Problems With Lean Six Sigma (Free DMAIC Checklist)

Elisabeth Swan is the co-author of “The Problem-Solver’s Toolkit” and co-host of “The Just-in-Time Cafe Podcast.” She’s been a process improvement consultant, speaker, and innovator for over 30 years. She’s the Chief Learning Experience Officer for GoLeanSixSigma.com, a former cast member of ImprovBoston, and – if asked – may still be able to ride a unicycle.

Surgeon Atul Gawande made headlines when he told the world that a simple checklist could drastically reduce unnecessary deaths in The Checklist Manifesto .

Yet, checklists conjure images of forklift drivers on loading docks with clipboards counting boxes. How could they transform healthcare?

“ He has… produced a 90-second checklist which reduced deaths and complications by more than one-third in eight hospitals around the world – at virtually no cost and for almost any operation. ” – James Clarke, reviewing The Checklist Manifesto,  Ulster Med J. 2011 Jan; 80(1): 54.

Aviation was transformed decades earlier when management and engineers at Boeing Corporation created the pre-flight checklist after the 1935 crash of the prototype Boeing B-17 at Wright Field in Dayton, Ohio. Checklists have become so essential to the airline industry that most crashes can be traced to the misuse or failure to complete a checklist.

A New York Times reviewer noted, “no matter how expert you may be, well-designed checklists can improve outcomes”. Since the purpose of process improvement is improving outcomes, Lean Six Sigma and checklists are natural companions.

To prove that, this Process Street blog post will show the relationship between checklists and lean six sigma, and provide you with a free  DMAIC Improvement Project Tollgate Checklist that you can use right now.

Use the links below to jump to that section of the post:

Lean Six Sigma and the role of problem-solving

Lean six sigma & the checklist, introduction phase, define phase, measure phase, analyze phase, improve phase, control phase, checklists and lean six sigma, use process street to reduce error.

Or, if you just want the checklist, check it out below!

Let’s get started.

For those unfamiliar with Lean Six Sigma and process improvement, it is a structured approach for organizations to scrutinize how things are done, poke at data and processes to uncover waste and then cut out things like extra forms, out-dated approvals and other time-wasting steps.

It’s a customer-focused, 5-step problem-solving model that engages entire workforces to constantly seek a better way of doing things.

Proof of Lean Six Sigma’s influence is evident in today’s hiring practices. A poll by GoLeanSixSigma highlights that hiring managers prefer a person who is “ Green Belt Certified ” – having substantial Lean Six Sigma skills – by an almost 80% margin. In an interview with the former head of Twitter, problem-solving emerged as the top skill sought by today’s most influential hiring managers.

In other words, problem-solving (especially via Lean Six Sigma) is an absolutely vital skill.

If problem-solving is a must-have skill and checklists are key to good outcomes, then combining the two makes sense.

DMAIC – Define, Measure, Analyze, Improve & Control – is the 5-Step model for Lean Six Sigma and there’s a set of required tollgates at the end of each phase. These tollgates outline what has to be done in order to move the problem-solving process forward.

Using the tollgates as an outline, we created a dynamic  Process Street template  that you can use for free and run checklists from to track your progress!

Before you can start solving problems, you need a problem to solve.

Picking a process issue – and finding someone in leadership to support you – are two required tasks in this first tollgate. Scoping the project is important (bigger than a “just-do-it” and smaller than “solving world hunger”) but even more critical is finding a Sponsor.

Finding a Sponsor

In a poll asking Lean Six Sigma practitioners what they considered the biggest obstacle to process improvement success, “Getting Leadership Support” accounted for almost a third.

When we coach team leads who tell us they can’t find someone to back their project, we let them know, “No Sponsor, no project”. If nobody in charge has any skin in the game, there’s no point in attempting the process fix. Find a different project that leadership supports.

One thing that helps when searching for leadership backing is being able to explain what Lean Six Sigma is and why it makes a difference. Since the checklist template is dynamic we inserted a video in the Define Phase within the checklist item, “Enlist a Project Champion/Sponsor who will support you and the project”. The team lead can share the video with managers or directors who they consider Sponsor candidates.

There’s also a Project Selection Guide Template embedded in the checklist so users can take a project idea and put it through a few screening questions. Is it a repeating problem? Is there a way to measure it? The checklist serves as a reminder, a source of templates, supporting videos and other just-in-time guidance.

The next set of tollgate tasks cover the Define Phase of DMAIC. This is where problem-solvers clarify the problem, the process impacted and customers of the process.

There is a journey of discovery during this phase as everyone agrees on the issue to solve. One of the big challenges is the tendency of ambitious team leads—or equally ambitious Sponsors—to try to “shoot the moon.”

Shooting the moon

They might want to reduce cycle time, reduce defects , improve margins, and increase customer satisfaction all by next Tuesday. But a project that focuses on everything accomplishes nothing. It’s okay to measure the cost reduction that results from reducing defects. But pick one of those to be the goal. Success is more possible if you focus on one goal at a time .

It takes practice and discipline to develop a manageable goal statement. Another moon shot is aiming for perfection out of the starting gate. When we see a goal statement that claims the team will, “reduce defects from 25% to 0%” then we know there is a sizable risk of failure and disappointment.

That’s why the Define Phase of the checklist includes a Goal Builder Template along with a blog providing tips on how to create well-crafted goal statements.

The primary focus of the Measure Phase is to baseline the process. If you’re trying to reduce defects, you need to know how you’re doing at that now. What’s your track record? You need to know the baseline of the process in order to measure whether or not you made a difference with your improvement when you get to the Improve Phase.

You need to know the gap, so you can close the gap.

The data’s in the system, somewhere…

One of the issues we run into in this phase is problem solvers assuming that data is sitting in a system somewhere waiting to be accessed. If they simply run a report, they’ll have the baseline. Check that off the list. But that rarely goes according to plan.

Maybe there’s system data, but was it entered with care? Is it reliable? We’ve seen teams struggle to use data that didn’t make sense. They could access cycle time data, but it didn’t take into account that the workday ended at 5:00. I had another team looking at why healthcare invoices had to be manually adjusted. They looked up the defect codes and the biggest category was “Other”. System data existed, but it was useless.

Most of the time, it helps to collect some data manually. In order to think through your approach, you need a Data Collection Plan. That involves listing the data you want and considering things like stratification factors—the “who, what, when, where” of data. If you’re looking at defects, should you collect data on defects by product? Defects by the fields on a form? Defects by customer type?

Within the task: “Develop a Data Collection Plan with Operational Definitions and create Check Sheets as Needed”, we’ve embedded a template (The Data Collection Plan) and a video to guide the process.

You’ll learn a lot by collecting the data firsthand, so if the perfect data set is not magically sitting in the system, it helps to have a plan.

Analyze is the crux of the DMAIC method. This is where learners drill down and discover the root cause of the process problem they’ve been chasing. Once you do that, you can solve the problem for good.

But if you have not determined the root cause then you might be solving a “symptom,” putting a bandaid on the problem or implementing a change based on a hunch. All of this means there’s a high likelihood the problem will remain and the efforts will have been in vain.

Finding the smoking gun

If you’ve always been told, “don’t bring me a problem, bring me a solution,” that’s an encouragement to jump right past this step into the fun of solutions. I’ve seen teams go with their assumptions regardless of what the data says or the process analysis reveals. I’ve seen Sponsors who tell teams what solutions they want to be implemented right from the get-go.

How do you stick with analysis long enough to find the smoking gun? The trick is to keep collecting the clues in the Cause & Effect Diagram , aka The “Fishbone Diagram”. It’s an aptly named tool, popularized by Dr. Ishikawa , which resembles a fish skeleton. Its construction allows teams to develop root cause theories around a problem as they build their knowledge of the process.

Each time they collect data, interview process participants on a Gemba Walk or map the process steps, they uncover potential reasons for defects. Making the most of the Fishbone Diagram is key but, during a poll, users reported where they fell short.

Solutions masquerading as problems

Over a third of respondents reported the issues of “listing solutions” on the Fishbone instead of causes. What we hear are phrases like, “the root cause is a lack of training”.

The problem with “lack of” anything is that it’s a sneaky way of putting a solution on the Fishbone.

The question is, “what is the training addressing?” Is it lack of user knowledge? If that’s the problem, could it be solved with helpful visuals, a simpler process? There are a lot of ways to address user knowledge before jumping to more employee training.

This is when you want to behave like the persistent detective – think Columbo, the classic 70’s TV icon. Every question helps you accumulate clues. People working through the process may have the answer without knowing it. The trick is to keep looking upstream until you find potential culprits. Dig past the symptoms.

To help with this phase, the checklist includes both a Fishbone Diagram Template as well as a video on how to get the most out of the Fishbone.

The Improve Phase is a long-anticipated step in the journey. It’s the step teams generally want to jump to from the start. Testing countermeasures, piloting solutions, watching the problem disappear, that’s the fun of process improvement. If you’ve done a proper job of Define, Measure, and Analyze, this phase falls nicely into place.

The ripple effect

The catch? Unintended consequences.

If you toss a stone into a lake you can see the ripples flow out from the center. The same principle holds true for process change. If you remove a step, change a form, skip an approval , will things fall apart? For that, we look to the Failure Modes & Effects Analysis or FMEA for short.

It’s a methodical way of assessing the potential for things to go wrong. It Involves deciding the potential severity and frequency of future problems and then mistake-proofing the process to prevent them. The technique originated at NASA since they couldn’t risk trial and error when sending men to the moon. By thinking through the risks of change they developed the kind of contingency plans you saw on display in movies like Apollo 13.

That’s why there’s an FMEA Template and a video on how to use it tucked into the main checklist from this post.

It’s okay to make changes. It’s simply key to think through the impact of those changes on other parts of the business.

Process Improvement can happen quickly and have a dramatic impact, but it’s critical to “stick the landing.” The Control Phase exists to see the improvement through to stability.

If teams move on and everyone takes their eyes off the ball, things may start to slip. What they need is the ability to continuously see the performance of the new process.

Sticking the landing

Have you ever tried to watch a game without a scoreboard? How would you know who was winning? Or how much time was left?

It’s the same with process work.

How does your team know how they’re doing? How do you stay aware of how the new process is performing?

By making the data visible.

Keeping an eye on Process Performance can be done with a single metric — you need to focus on one thing. If the goal was to reduce defects, then the single metric would be tracking the daily percentage of defects. A great way to measure success is with a Control Chart.

Control Charts are time charts. You might know them as Line Charts or Run Charts. They include a measure of variation so they are often referred to as “Run Charts that went to college”. They can be created in Excel , but they can also be drawn by hand.

Teams often set up whiteboards in the shared workspace to track things like defects. People can rotate responsibility for updating the chart. If people can see the measure and are responsible for it—they pay attention to it. What gets measured gets managed.

The Control Chart Template is embedded in the checklist for the Control Phase.

Process Improvement is a mainstay of Operational Excellence and checklists are simple but effective ways to make sure you get the outcomes you want. The following quote comes from the interim CEO/President of the Association for Manufacturing Excellence ( AME ).

“ I am a big fan of checklists for ensuring quality at the source. They serve an important purpose in reminding us of all that’s needed in a particular process or project. Without checklists, we risk missing or overlooking something by mistake. Checklists work best when ticking off items as they are completed, not en masse once the entire project is done. The key point is to use and follow them, not “pencil-whip” them from memory after the fact. While not foolproof, checklists can help us cover the details and result in more thorough, successful improvement efforts. ” – Jerry Wright , President, AME

Checklists have transformed healthcare, aviation, and countless other industries. Run this Process Street DMAIC Tollgate Checklist and make sure your next improvement effort gets great results.

Process Street is a powerful piece of workflow software that lets you crush the human error in your organization.

By creating process templates (like the free DMAIC checklist in this post) you can give your whole team a central location for them to see what they have to do, and how exactly they should do it.

No more confusion, no more errors.

Take advantage of our powerful feature set to create superpowered checklists, including:

• Form fields
• Conditional logic
• Variable user permission levels
• Exporting and printing templates
• And much, much more!

Check out our intro webinar to see the app in action!

Stop leaving the success of your processes up to chance. Get started with a free trial of Process Street today!

How do you manage quality control in your business? Let us know in the comments!

Get our posts & product updates earlier by simply subscribing

Ben Mulholland

Ben Mulholland is an Editor at Process Street , and winds down with a casual article or two on Mulholland Writing . Find him on Twitter here .

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.

Take control of your workflows today

• school Campus Bookshelves
• menu_book Bookshelves
• perm_media Learning Objects
• login Login
• how_to_reg Request Instructor Account
• hub Instructor Commons
• Download Page (PDF)
• Download Full Book (PDF)
• Periodic Table
• Physics Constants
• Scientific Calculator
• Reference & Cite
• Tools expand_more
• Readability

selected template will load here

This action is not available.

6.4: Lean Processes

• Last updated
• Save as PDF
• Page ID 50787

• Michael Laverty and Chris Littel et al.

Learning Objectives

By the end of this section, you will be able to:

• Discuss the lean process methodology
• Understand the phases of the lean problem-solving process.

You have learned about different problem-solving approaches that entrepreneurs take to lead their startups and work with others. Most of these approaches have had to do with the entrepreneur’s cognitive or creative mindsets. Now we will learn about an approach that is more rooted in process, called lean process . Lean problem solving has been used as an entrepreneurial methodology in new and emerging ventures, and it’s interesting that it comes from a large corporate, manufacturing background that focuses on efficiencies. The Six Sigma methodology, pioneered at Motorola in the 1970s and 1980s, and adopted by many companies, is a disciplined, data-driven approach that provides companies tools to improve the capability of their business processes. According to the American Society for Quality, “Six Sigma views all work as processes that can be defined, measured, analyzed, improved and controlled. A set of qualitative and quantitative tools is used to drive process improvement. This increase in performance and decrease in process variation helps lead to defect reduction and improvement in profits, employee morale, and quality of products or services.” 26 GE copied it and created the “Process Excellence” programs that millions of managers and others have taken to get certified at various “belts.” Although Six Sigma and Process Excellence do not fit strictly in terms of entrepreneurship, as they are used mainly by large, mature companies, many of the methods fit in the lean model.

Toyota pioneered the lean process in the 1980s. The term “lean manufacturing” is the most common, but it is much more than manufacturing. The lean process is a systematic method for the maximizing of continuous improvement and the minimization of surplus or unused material in the production of a process. The entrepreneur begins the startup with a sense the original product will be the product carrying the organization to success in the long term. In most cases, the good or service will require modification to maintain a process, technology, or up-to-date product offering. Lean problem solving means the entrepreneur’s entire team scans both the company’s internal and external environments for continuous improvement and methods for bringing additional revenue to the startup by cost improvement processes that promote sustainable value. The external environment encompasses customers, industry trends, and competition. The internal environment comprises the factors inside the enterprise, such as employees, and internal practices and processes. In lean manufacturing, for example, improving efficiencies in the internal environment should lead to advantages in the external environment (whether that be cost savings to customers, competitive advantage from more output/superior product, etc.).

For example, every mile saved per day per UPS truck driver results in approximately $50 million in savings per year, according to Juan Perez, the company’s chief information and engineering officer. Using customer data and artificial intelligence, the company created a system dubbed ORION, which is an acronym for On-Road Integrated Optimization and Navigation. 27 To date, the system has resulted in $400 million in savings to UPS. By applying the lean process, everything that UPS saves on the input (by reducing mileage) leads to savings on the output, which leads faster deliveries, lower costs for consumers, and more profit for UPS.

Lean Problem-Solving Process

The lean problem-solving process is a cycle of observation, assessment, and continual evaluation. As shown in Table 6.4.1, this cycle typically involves eight specific steps.

The lean problem-solving, step-wise process allows the business to observe, assess, and continually evaluate.

ARE YOU READY?

Too much too late.

Many entrepreneurs create a startup with an idea that they develop without any feedback from potential customers, relying on their own knowledge or assumptions about the market. Consider the story of Rapid SOS: https://hbr.org/2018/05/do-entrepren...eed-a-strategy . What would most likely happen when they decided to go forward with their product? Will it be a fit to the customer’s needs or solve their problems? How is lean process different from this?

Lean Problem-Solving Phases

Observation is the phase in which the entrepreneur studies the challenge and notes all facets of the challenge requiring solution. In this phase, the entrepreneur asks questions and conducts research about the change needed for a successful product, outcome, or service. The entrepreneurs must determine why the change is needed. What is the purpose of the endeavor? Feedback is extremely important in this phase.

For example, a community asked a group of entrepreneurs to help address the youth obesity problem in a middle school. The entrepreneurs began to study the intake of food by the children and determined that both the content of the school lunch menu and the lifestyle of the majority of the children were affecting the obesity rate in the community. They then defined the purpose of the project as finding a low-cost, low-risk method of changing the lunch menu and agreed that the primary outcome would be a 30 percent reduction in the obesity rate of the children. The entrepreneurs began to assess the cost of changing the lunch menu and observing what else the kids ate. The entrepreneurs discovered that the lunch menu change required to reduce the obesity rate was beyond the financial capability of the school district. Research also showed that many of the children, products of single-parent homes, were eating high-calorie, high-fat, take-out foods for dinner. Further observation revealed that the children did not engage in physical activity after hours because the local surroundings were not safe. The community needed a process to transform the wellness of the children, and the entrepreneurs recommended using a lean process approach to help the children as quickly as possible.

After the observation of the problem comes assessment , the phase in which the entrepreneur experiments and analyzes the potential process and its capabilities. The entrepreneur leverages creative tools and resources to arrive at a solution and assesses each step of a possible solution. Each step must add value to the solution, or that step in the solution is unnecessary. In addition, the step must be capable of solving the issue and add flexibility to the solution. How is the process or product being improved? In this phase, a prototype of the product is developed and delivered. The entrepreneur must ask the customer if all needs and wants are satisfied with the prototype. If the prototype is being developed for mass production, surveying customers about potential sales is essential. In the school lunch example, the school system would have been the customer of the new food menu (prototype) in the assessment phase.

Evaluation is the phase in which behaviors are analyzed to assess success. The entrepreneur continually studies each phase of the solution to observe the effectiveness of outcomes desired by the client. The entrepreneur ensures that transformation is built into the habits of the school to obtain, maintain, and develop the desired outcomes.

In a real-world example of a company applying lean processes, the New Balance Company, which designs and manufactures both athletic and casual shoes, used a batching approach in the early 2000s that organized production by departments, so that all of the cutting took place in one department, all of the stitching took place in another, and so forth. While it seems that batching tasks would improve efficiency, at New Balance, it meant that production of one pair of shoes took nine days. Executives observed piles of inventory sitting between floors and departments, and noticed employees waiting while there were delays in the production line. They also noticed that the pay structure contributed to the piles of works in process because employees were paid by the piece, which encouraged them to produce as much as possible.

The company applied lean principles to rearrange the production floor by value streams, or the making of a product by sharing similar processing steps. On one side was “cut and stitch” products using US materials of leather and mesh, while another side used premade products from overseas for soles, inserts, and kits. This change cut the time to make a pair of shoes down to four hours, meaning that domestic plants could ship some orders in twenty-four hours, while competitors may need as much as 121 days to ship when they outsourced manufacturing to Asia.

An often-used lean problem-solving tool is whiteboarding ( Figure 6.16 ). Whiteboarding is a type of graphing that permits the entrepreneur to plot each step in a process to build comprehension and detailing of the process. The entrepreneur draws each step on the whiteboard using a linking-type diagram, and draws arrows to show how processes affect other processes. Seeing the flow of the process allows the entrepreneur to note where functions in the process are duplicated or inconsistent.

For example, in a community garden, storing tools, such as hoes and hand trowels for weeding, in different sheds wastes time when preparing to begin the process of weeding. These tools should be stored collectively to eliminate multiple trips and wasted time. Seeing the process on a whiteboard or other medium brings awareness to how processes can be improved. After the process is changed, it is graphed again for further scrutiny.

ENTREPRENEUR IN ACTION

The origin of lean.

Would it surprise you to know the origin of lean, in modern times, is considered to be Henry Ford’s production line? Although we don’t necessarily think of the creation of automobiles as an entrepreneurial venture in today’s world, Henry Ford was truly an entrepreneur for his time when the manufacture of automobiles was just beginning. Not only did he recognize the opportunity inherent in the sale of automobiles, he recognized the need to create an efficient process for automobile production that could decrease costs and, consequently, the selling price of the vehicle. As the first entrepreneur to join the use of interchangeable parts with moving conveyance to develop fabrication processes, Ford was able to turn over inventory in a very short time; however, Ford’s process could not deliver variety. In fact, Ford was quoted as saying of the Model T’s color, “You can have any color as long as it's black.” 29 It had the fastest drying time; hence, it was the only color he used for a number of years.

The Ford system was built around one static product. In the 1930s, when the market demanded product variety, the company was not set up to address this challenge. Kiichiro Toyoda (Figure \(\PageIndex{2}\)), the second president of Toyota Motor Corporation, visited the Ford plant in Michigan to learn more about their application of the assembly line concept. After observing, he proposed a new production system that would strive to “right size” equipment to better match tasks and the volume of work, as well as introducing quality assurance steps in each sequence of the work process. Toyoda’s approach shifted the focus from machinery to process, optimizing efficiency while maintaining quality.

• Guide: 8D Problem Solving

Daniel Croft

Daniel Croft is an experienced continuous improvement manager with a Lean Six Sigma Black Belt and a Bachelor's degree in Business Management. With more than ten years of experience applying his skills across various industries, Daniel specializes in optimizing processes and improving efficiency. His approach combines practical experience with a deep understanding of business fundamentals to drive meaningful change.

• Last Updated: June 13, 2023
• Learn Lean Sigma

8D Problem Solving is a systematic and structured approach used to solve business related problems. It names has been given by the fact there are 8 steps or 8 disciplines that are followed to identify, correct and eliminate recurring problems.

8D Problem Solving is regarded as robust methodology that has proven its worth across multiple industries and manufacturing in particular. The methodology was Initially developed within the automotive industry, it has since been widely adopted in manufacturing, logistics and health care to name a few. The 8D approach goes beyond helping team just identify the root cause of problem but also provides a structured approach for implementing and verifying corrective actions.

Table of Contents

What is 8d problem solving.

The 8D Problem-Solving methodology was developed in the late 1980s  by Ford Motor Company. The term “8D” stands for “Eight Disciplines,” which represent the eight critical steps in problem-solving.

Initially it was only intended to resolve issues within the automotive manufacturing process. However, over the year since then the methodology has gained universal acceptance and is now applied across various sectors. The 8D approach was heavily influenced by quality management systems like Total Quality Management (TQM) and methodologies like Six Sigma and forms a key part of quality roles and Six sigma qualifications.

8D is also encourages collaborative team based approach to addressing issues in the workplace This methodology was purposefully designed to be a cross-functional effort, ensuring to bring together expertise from different departments or disciplines to comprehensively address an issue by looking at it from all point of view. Here are the key components:

Preparation : Before diving into problem-solving, the team gathers all necessary resources and tools.

Team Establishment : A cross-functional team is assembled, each member having a specific role and responsibility.

Problem Description : The issue at hand is clearly defined to ensure everyone has a shared understanding.

Interim Actions : Short-term solutions are implemented to contain the problem and prevent further damage.

Root Cause Analysis : Various tools and methods are used to identify the real cause of the problem.

Permanent Corrective Actions : Long-term solutions are selected and verified to eliminate the root cause.

Implementation : The long-term solutions are implemented across the board, including necessary changes to policies and procedures.

Prevent Recurrence : Measures are taken to ensure that the problem does not occur again.

Team Recognition : The team is congratulated and acknowledged for their efforts.

How does 8D Compare to over Problem-Solving Methods?

Between quality management systems and lean six sigma there are several problem-solving methodologies such as PDCA (Plan-Do-Check-Act), DMAIC (Define-Measure-Analyze-Improve-Control), and A3 . However the combination of the 8D steps results in a comprehensive frame work that is:

Team-Oriented : Unlike some methodologies that can be carried out by individuals, 8D strongly emphasizes team collaboration as a core principle as seen in steps D1 and D8.

Structured Framework : 8D provides a very detailed, step-by-step guide for solving complex problems, by breaking it down in to logical steps making it easier to manage and track progress.

Broad Applicability : While some methodologies like DMAIC are closely tied to Six Sigma, 8D can be applied in various contexts without being tied to a particular quality management system.

Focus on Prevention : 8D not only aims to solve the problem but also focuses on implementing changes to prevent its recurrence, making it a complete approach to problem solving.

The 8 Disciplines Explained

D0: prepare for the process.

Before you start 8D you should prepare for the 8D process. This phase sets the foundation for the entire methodology, ensuring that the team is able to tackle the problem effectively. Therefore, effective preparation helps in avoiding unnecessary delays and ensures that you’re not solving the wrong problem.

Within the initial preparation step you should also the time to think about what knowledge, expertise and experience you need within the team. Cross-functional teams are important, as they bring alternative perspectives and skills to the table rather than everyone looking at the problem from one point of view. Make sure you consider expertise, availability, and interest when selecting team members.

D1: Establish the Team

In D1 you should establish the team by clearly defining the roles and responsibilities for each team member. This includes assigning a team leader, subject matter experts, and roles for data collection , analysis, and communication this helps to provide the team members clarity on how they will be involved and contribute to the success of the problems solving activity.

Team Composition

Once roles are defined, where possible ensure that the team is balanced in terms of skills and expertise. A well-rounded team will be more effective in tackling various aspects of the problem.

Communication

Establish clear methods communication, both within the team and with external stakeholders. Such as deciding on regular meeting schedules that everyone can attend, reporting formats, and tools for collaboration.

D2: Describe the Problem

In D2 it is time to create a well formed problem statement. This step is key as it provides a foundation for understanding the problem which will lead to generally more successful problem-solving. It ensures that everyone clearly understands what needs to be addressed, setting the scope for the entire process. Ensure that the problem is clearly understood by everyone in the team at this stage to prevent confusion later on in the process.

5W1H Method of creating a Problem Definition

Use data gathering techniques such as observations, interviews, and document reviews can help to precisely identify the problem. A useful tool to use at this stage could be the 5W1H Problem definition method.

You can find out more about this method with our 5W1H guide .

Problem Definition – is / is not template

When creating your problem definition ensure to be specific, measurable, and unambiguous when stating the problem. You should avoid generalities and ensure that the problem statement is understandable to someone unfamiliar with the issue. If you are new to this process it may be helpful to give the statement to someone unfamiliar to the process and see if they understand it or if they have questions. You can then clarify any questions by adjusting the problem description to improve the claity.

D3: Implement and Verify Interim Actions

In D3 while the team is investigating the root cause, interim actions are must be implement to contain the problem and minimize its impact. This is particularly important in critical situations affecting safety, compliance, or customer satisfaction. 

In this step you should identify, plan, and execute short-term fixes that can quickly contain the problem. This could include quarantining the product to ensure it is not sent out to the customer or even pausing production lines that continue to product defects. Ensure these actions are documented for future reference.

Use metrics and KPIs to gauge the effectiveness of the interim actions. Make adjustments as necessary.

D4: Root Cause Analysis

D4 is where you start to understand what is causing the issue by identifying the underlying reason for the problem. The objective is to find the root cause, not just the symptoms.

At this stage there are a range of quality and lean six sigma tools that can be used to conduct root cause analysis , which can include the Fishbone Diagram for structured brainstorming and the 5 Whys technique for causal chain analysis.

We have a range of guides on all of these techniques for you to use.

Once identified, it is important validate the root cause through experimentation or additional data analysis to ensure it’s the actual cause and not a symptom, this can often be an overlook critical step in the root cause process.

D5: Choose and Verify Permanent Corrective Actions

In D5 you need to choose what actions to be taken to prevent the problem reoccurring and any solutions implemented should be verified that the actions correct the problem this can involve trial runs, further data collection and inspections of product or services being produced.

You should also consider factors like cost, impact, and feasibility when choosing a permanent corrective action and should also conduct a risk assessment to evaluate potential negative outcomes of the actions taken

An implementation or action plan is often useful to document at this stage to detail the steps for implementation, assign responsibilities, and set timelines.

D6: Implement Permanent Corrective Actions

Once verified, implement the corrective actions across all relevant departments or processes. This can involved documenting the new process and training out to all stakeholders involved to ensure the new process is followed and that the stakeholders understand the reason for the change.

At this point you should continue to regularly monitor the situation to ensure the corrective actions are sustained and effective, this could be for a period of 30, 60 or 90 days after the problem was resolved to ensure the new process has become a sustained and issues do not reoccur. 

D7: Prevent Recurrence

In D7 to prevent recurrent you should review and update organizational policies or standard operating procedures (SOPs) to prevent a recurrence of the problem and document the new standard process

It is important to conduct regular reviews to continuously monitor the process and ensure procedures are being followed but also to identify further opportunities for process improvement.

D8: Congratulate the Team

The final step D8, after the hard work and successful problem resolution, it is important to acknowledging and congratulating the team is vital for morale and future engagement. With the recognition of a successful 8D Problem-solving activity complete you are more likely to encourage future participation as the method gets a reputation as being useful and successful at solving problems. 

Whether it’s a team lunch, certificates of achievement, or simply a public acknowledgment, celebrate the success in a way that resonates with your team.

Finally it is always important to conduct a lessons-learned session and document the insights gained during the process for future reference. This can be used as a future point of reference for problem solving activities.

Mastering the art of problem-solving is crucial in today’s complex and fast-paced environment. The 8D Problem-Solving methodology offers a structured, team-based approach to tackling challenges that can arise in any sector, be it manufacturing, public services, or logistics. This guide has walked you through each of the eight disciplines, offering best practices and highlighting common pitfalls to avoid. We’ve also enriched your understanding through real-world case studies that demonstrate the methodology’s versatility and effectiveness. Remember, the strength of 8D lies not just in identifying and resolving problems, but also in preventing their recurrence through systemic improvements. By adhering to the principles and steps outlined in this guide, you’re well on your way to becoming an adept problem solver, capable of driving continuous improvement in your organization.

• Zarghami, A. and Benbow, D.W., 2017.  Introduction to 8D problem solving . Quality Press.
• Camarillo, A., Ríos, J. and Althoff, K.D., 2017. CBR and PLM applied to diagnosis and technical support during problem solving in the Continuous Improvement Process of manufacturing plants .  Procedia Manufacturing ,  13 , pp.987-994.

Q: What is 8D problem solving?

A: 8D problem solving is a systematic approach used to address and resolve complex problems. It is widely utilized in various industries to identify the root causes of issues, develop effective solutions, and prevent their recurrence.

Q: Why is it called "8D" problem solving?

A: The name “8D” refers to the eight disciplines or steps involved in the problem-solving process. Each discipline represents a specific stage in the methodology, allowing for a structured and comprehensive approach to problem resolution.

Q: What are the eight disciplines (8D) in problem solving?

A: The eight disciplines in problem solving, often abbreviated as 8D, are as follows:

• D1: Form a team
• D2: Define the problem
• D3: Implement containment actions
• D4: Determine the root cause
• D5: Develop and implement corrective actions
• D6: Validate the effectiveness of corrective actions
• D7: Prevent recurrence
• D8: Congratulate the team

Q: What is the purpose of forming a team in the 8D problem-solving process?

A: Forming a team at the beginning of the 8D problem-solving process helps ensure that the right individuals with the necessary expertise are involved in addressing the problem. The team collaboratively works towards understanding the issue, analyzing data, and developing effective solutions.

Q: How is the root cause determined in the 8D problem-solving process?

A: Determining the root cause (D4) involves conducting a thorough analysis of the problem. Various tools and techniques, such as cause-and-effect diagrams, 5 Whys, and data analysis, are employed to identify the underlying factors contributing to the problem.

Q: Can the 8D problem-solving methodology be applied to any type of problem?

A: Yes, the 8D problem-solving methodology is a versatile approach that can be applied to various types of problems across different industries. It provides a structured framework for problem resolution and can be tailored to suit the specific needs and requirements of different situations.

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Download Template

Free lean six sigma templates.

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

Other Guides

LEI's Learning Portal

New intro to lean thinking & practice.

This online course serves as an introduction to the key concepts, philosophies, and tools associated with lean thinking and practice.

Lean thinking and practice helps organizations become both innovative and competitive, which in turn allows them to become sustainable.

This engaging, online, go-at-your-own-pace course is designed to give you an understanding of what lean is, what it might look like in your workplace, and how to start applying it.

Welcome to Lean Thinking & Practice

Learning objectives.

This course works for people new to the concepts of lean and continuous improvement, for individuals looking to improve their lean understanding and skills, and for organizations wanting to level set the lean knowledge of their workforce to speed progress.

Recognize where and how to apply lean principles, systems, and concepts, to increase value and eliminate waste in your daily work

Resolve business challenges by using scientific method, PDCA-based problem solving

Identify work activities as being “value-add,” “incidental,” or “waste” and understand how all three affect workflow

Understand the five dimensions of the Lean Transformation Framework and explain why all five are necessary for a transformation to occur

Time Estimates Per Unit*

*Actual times may vary.

Senior Instructor John Shook

Shook co-authored Learning to See, the book that introduced the world to value-stream mapping. He also co-authored Kaizen Express, a bi-lingual manual of the essential concepts and tools of the Toyota Production System. With Managing to Learn, Shook revealed the deeper workings of the A3 management process that is at the heart of Toyota’s management and leadership.

Patience Onakpoya

This is just what I needed. I have just recently started my career in manufacturing and what I have learnt from this course comes in handy. I highly recommen...

This is just what I needed. I have just recently started my career in manufacturing and what I have learnt from this course comes in handy. I highly recommend for all engineers.

Excellent insight into Lean practice

Andrew gardler.

The course was thorough in delivering the knowledge regarding Lean concepts and how they work, the content was easy to follow and was easy to digest.

Very insightful course!

Jennifer segers, so you want to see change.

Sometimes it's the littlest things that make the biggest difference. Think of the smallest problem you have a work, and you might find it isn't really a pro...

Sometimes it's the littlest things that make the biggest difference. Think of the smallest problem you have a work, and you might find it isn't really a problem if you use the tools to fix it!

Definitely worth the time investment!

Christy leite.

This was an excellent course. The topics were organized into a method of integrating video, slides, and articles/letters providing real live examples of the ...

This was an excellent course. The topics were organized into a method of integrating video, slides, and articles/letters providing real live examples of the application of the thought process and lean tools. Applying lean tools without the basic lean thinking will not take us very far in a lean journey. This course provides insightful material. The exercises provide insightful questions challenging the student to reflect deeply on the material just learned and how to apply it in their daily work. I highly recommend this course to employees of all organizations from the shop floor to the CEO.

Stay connected on all things lean thinking and practice.

Add your email to LEI's mailing list to get the latest updates.

Please enter a valid email address

Please check this box if you wish to proceed

Oops, something went wrong. Please try again with a different email address.

Additional Courses

Intro to Problem Solving

Problem solving is critical to every position in every industry. In this course, you will learn to grasp the situation at the gemba (where the work is done) and use all your senses to understand what is truly happening.

Developing Structured Problem-Solving and Leadership Skills using A3 Thinking - Managing to Learn Remotely

This comprehensive training will teach you how to use the potent A3 methodology, based on the proven scientific method of plan-do-check-act (PDCA), to address an important business problem within your organization.

Learning to See Using Value Stream Mapping - with Live Coaching

This workshop shows you how to make and apply this fundamental and critical tool based on the Lean Enterprise Institute's groundbreaking value-stream mapping workbook, Learning to See, which has introduced the mapping tool to thousands of people.

• Consultancy
• Online Courses

SIGN UP TODAY

• Lean , Lean Wiki , Six Sigma

DMAIC Model | The 5 Phase DMAIC Process to Problem-Solving

• 5 mins to read
• July 1, 2020
• By Reagan Pannell

Summary: An Introduction to DMAIC

Dmaic – the dmaic model.

The 6 Sigma DMAIC model remains the core roadmap for almost all Lean Six Sigma problem-solving approaches that drive quality improvement projects. It is used to ensure a robust problem-solving process is followed to give the best chance of the best solution being found.

A note about the structure and the approach used in this article.

Our approach to DMAIC follows Quentin Brook’s book “Lean Six Sigma & Minitab” which for anyone wishing to study Lean Six Sigma is a must for the  Green Belt Course  and the  Black Belt Course .

What is the dmaic model.

DMAIC is short for: Define, Measure, Analyse, Improve and Control. These are the key phases that each project must go through to find the right solution. This flow is the concept behind DMAIC Analysis of an issue and its the DMAIC cycle all projects must go through.

As you can quickly see from the 5 DMAIC phases they follow a logical sequence as we will go through in more detail below. But they also make sure you do not try to jump to implementing a solution before you have properly, defined and measured what you are going to be an improvement.

We all love to jump to solutions, but the DMAIC problem-solving structure helps us have a more rigorous approach so that we do not short cut the process and perhaps miss the best solution or perhaps implement the wrong solution as well. It can help companies better structure their problem-solving approaches and be more robust in their approach. 

DMAIC – The 5 DMAIC Process Phases

The phases throughout the DMAIC model have and can be broken down in many different ways. One of the best approaches we have found is from Opex Resources which shows how to examine the existing processes, and with a project team, and the sigma improvement process, we can solve complex issues.

DMAIC Define Phase

The purpose of the Define phase is ultimately to describe the problems that need to be solved and for the key business decision-makers to be aligned on the goal of the project. Its about creating and agreeing the project charter .

All too often, teams have identified solutions without actually defining what it is they will actually be trying to do or perhaps not do. This can lead to internal confusion and often solutions which completely miss the business requirements and needs.

• Define the Business Case
• Understand the Consumer
• Define The Process
• Manage the Project
• Gain Project Approval

DMAIC Measure Phase

In the measure phase, the goal is to collect the relevant information to baseline the current performance of the product or the process. In this stage, we want to identify the level of “defects” or the errors that go wrong and use the baseline to measure our progress throughout the project.

The key goal of this phase is to have a very strong and clear measure/baseline of how things are performing today so that we can always monitor our progress towards our goals. We need to understand our cycle times , process times, quality metrics.

Many projects are delivered without clear benefits being shown because the team never fully baseline the current status before making changes.

The Measure phase can be broken down into 5 key areas:

• Develop Process Measures
• Collect Process Data
• Check the Data Quality
• Understand Process Behaviour
• Baseline Process Capability and Potential

100% Free Fundamentals of Lean COURSE

Take our free course.

JOIN FOR FREE

Join our Lean Six Sigma Yellow Belt Certification Course

We can’t solve problems by using the same kind of thinking we used when we created them” Albert Einstein Tweet

DMAIC Analyse Phase

The goal of the DMAIC Analyse phase with the lean six sigma improvement process is to identify which process inputs or parameters have the most critical effect on the outputs. In other words, we want to identify the root cause(s) so that we know what critical elements we need to fix.

During this phase, the teams need to explore all potential root causes using both analytical approaches, statistical approaches or even graphical tools such as VSM’s and Process maps to uncover the most important elements which need to be changed/fixed.

The Analyse phase can be broken down into:

• Analyse the Process
• Develop Theories and Ideas
• Analyse the Data
• and finally, Verify Root Causes 

DMAIC Improve Phase

The goal of the improvement phase is to identify a wide range of potential solutions before identifying the critical solutions which will give us the maximum return for our investment and directly fix the root cause we identified.

During this phase, the team brainstorm, pilot, test and validate potential improvement ideas before finally implementing the right solutions. With each pilot, the team can validate how well it improves the key measures they identified back in Define and Measure. When the team finally roll out the solution, the results should be seen if the right solution has been found and implemented correctly.

The Improve phase can be broken down into:

• Generate Potential Solutions
• Select the Best Solution
• Assess the Risks
• Pilot and Implement

DMAIC Control Phase

The final part of the DMAIC Model is the Control phase where we need to ensure that the new changes become business as normal and we do not revert to the same way of working as before.

During this phase, we want to ensure that we close the project off by validating the project savings and ensuring the new process is correctly documented. We also need to make sure that new measures and process KPI’s are in place and, finally that we get the business champion to sign off on both the project and the savings. We may need to redesign the workplace following the 5S principles .

The Control phase can be broken down into:

• Implement Ongoing Measurements
• Standardise Solutions
• Quantify the Improvement
• Close The Project

The key closing documents of the Control Phase is a Control Plan that documents all the changes and process steps with key risks, standard work instructions and the Project Close-Out document signed by the business owners to accept the change and the validated benefits.

The DMAIC Model vs. A3 Management vs. 8D Problem Solving

The DMAIC model is not the only project management roadmap. Two others which are important is the A3 format which originally comes from Toyota and is very Lean focused and the 8D which draws more of the DMAIC structure but with the 1-page idea of the A3.

Everyone has their own preference but each method is interchangeable. The DMAIC Structure lends its self naturally to a multi-slide Powerpoint presentation. Whereas the A3 is a single-page document which is perfect for internal communication and adding into War Rooms and Control Towers.

What’s important is that every problem-solving approach follows the PDCA (Plan, Do, Check and Act) Scientific Problem Solving format. The reset is just a preference or using the right tool in the right circumstances.

• Corporate Training
• Courses for Individuals

Our Newsletter

Reagan pannell.

Reagan Pannell is a highly accomplished professional with 15 years of experience in building lean management programs for corporate companies. With his expertise in strategy execution, he has established himself as a trusted advisor for numerous organisations seeking to improve their operational efficiency.

Our Training Courses

Fundamentals of lean.

• Lean Six Sigma White Belt Course
• Lean Thinking Business Course
• Lean Six Sigma Yellow Belt Course
• Lean Six Sigma Green Belt Course
• Lean Six Sigma Black Belt Course

Yellow Belt Course

View all courses, recent articles, 5 essential problem-solving strategies every business leader should know, unveiling the secrets of blue ocean strategy for business growth, the difference between strategy and strategic execution, small steps, big gains: the case for incremental improvement, maximising efficiency and profitability: exploring the benefits of lean consultancy, empowering leaders: the imperative for problem-solving training, view all articles, green belt course, other articles, developing the change management mindset, principe 8: use throughly tested technology | principles of lean, principle 1: use long term goals to drive short term decisions, one piece flow and how it reduces waste and increases productivity, an introduction to measure system analysis, elearning affiliate program | online business courses, a deep dive into the a3 problem-solving approach, how to find out the minimum sample size for lean six sigma, the box-cox transformation: what it is and how to use it, what is the 1 sample t-test, what are the different types of wastes in lean (muda, muri, mura), histogram: a comprehensive guide, related articles, what is a sigma level: a key metric in process capability, an introduction to correlation and regression analysis, lean lifestyle design, 5 essential elements of operational learning, what is the design of experiments tool, lean six sigma online courses.

FREE COURSE | YELLOW BELT | GREEN BELT | BLACK BELT | MASTERCLASS | WORKSHOPS

Lean Accelerator Progam

A Lean Six Sigma Green Belt Masterclass

Ready to start your journey into the world of Lean with this free course?

FREE COURSE

Lean Thinking

A Lean focused continious improvement certification course

LSS Yellow Belt

Propel your career forward, tackle complex problems and drive change

LSS Green Belt

The ultimate fast-track for future leadership

LSS Black Belt

Become an expert in change management and complex problem-solving.

Subscribe to Newsletter

Keep up to date to the latest insights, courses, training, webinars and more. Join our newsletter today.

Lean Accelerator Program

Discover the power of problem-solving, 15 min per day | 3-months | only €999 | learn from experts.

The Lean Post / Articles / Learning to Solve Problems By… Wait for It… Solving Problems

Problem Solving

Learning to Solve Problems By… Wait for It… Solving Problems

By Josh Howell

February 8, 2023

A team learns what matters when it comes to problem-solving using lean thinking and practices.

Becoming a lean enterprise isn’t easy. Even individually, consistently thinking lean, especially in practice , isn’t easy. Thankfully, our forebears have given us models like the TPS house and various frameworks for lean transformation that we can return to when things go sideways. Recently, I needed to do just that. 

I was on a call with an executive team. It was a year or so into launching a new business line with an innovative model for their industry (healthcare). As a small business, the ambitious endeavor required their staff to be fully engaged, contributing all their talents and ideas. The executives hypothesized that a lean transformation would enable this. On the call, however, one of the executives was exasperated with how things were going. 

“We all agree that problem-solving capability is critically important. We’ve been building it, I guess, for more than a year. We’ve been doing a lot of stuff anyway. Yet it seems like we do everything but actually solve problems. Can anyone tell me the last problem we solved? I mean, really?” 

Silence. 

Eventually, another executive responded. “Look, our team’s mindset is changing. The KPIs we’ve established… the daily huddles we’ve set up… the team’s talking about performance and problems every day!” 

“Exactly,” the first executive snapped back. “We talk about problems. We just don’t solve them.” 

As background, the company’s patients are afflicted with a chronic disease. Unfortunately, the insurance model that funds their care, including the company’s services, puts caps on their treatment. Seeing this as their problem to solve, the executive team is trying to prove out a new model that overcomes these limitations to prevent unnecessary suffering. By demonstrating what’s possible, they ultimately hope for widespread adoption of this model across the industry. Again, for a small business, it’s ambitious, to say the least. And admirable. 

A Process (Questions) for Reflection 

This moment caused us to reflect, drawing upon the Lean Transformation Framework’s five questions . One, the purpose was clear. The executives had been doing a lot of work to clarify it, establishing a vision, a mission statement, and even an actionable strategy for the year. Two, the work was… well, I’ll come back to that. Three, the capability in development was problem-solving, check — that was the intention anyway. Four, the management system’s development had made considerable progress. Lots of activity there. And five, mindsets were changing! 

Even a quick run-through of the Framework’s questions provided insight: We could see that the focus had been on developing a management system for problem-solving: KPIs, visuals, huddles, a standard agenda, info in, info out. And correspondingly, leader behaviors, such as how they’d respond to problems. On the other hand, we saw less progress, in practice anyway, on improving the work — where we’d expect to see the impact of problem-solving. Thus, the executive’s lament that problem-solving capability was being developed theoretically at best but not in actuality.  

To illustrate what had been happening: A problem would come up. The executives would huddle to discuss what would have helped them better detect the problem sooner, how they could better organize themselves, and how they could tackle it more effectively. Better KPIs? More frequent huddles? A revised agenda? They’d update their management system accordingly. 

As “good” as these mechanisms were, however, lost in the response was actually solving the problem in the work . So, while a management system was under construction, it was never tested. The work never changed. Therefore, whether the management system could fulfill its purpose remained unknown. What we had here was a meta-problem — a problem with our problem-solving approach.  

No Reflection is Complete Without Self-Reflection 

This experience reminded me of a hard lesson I once learned in a factory. Well, nearly learned, as it turns out. Because here I was relearning it. As I said, lean thinking and practice isn’t easy. 

My early lean learning occurred as a member of the corporate lean team at Starbucks. One process at a time, my team observed the work in detail and defined the problems to solve. For example, we discovered millions of dollars of product waste in the brewed coffee process and issues with product quality and availability. Then, in a lab store at the headquarters, we experimented with local baristas to develop “better ways” of doing the work that addressed these problems. And finally, through trial and (plenty of) error, we created a leader-led approach to introducing these process improvements that simultaneously built problem-solving capabilities throughout the management ranks.  

Over time, an operating system based on lean principles emerged as a program and as a platform for subsequent adds, such as management routines for multiple levels. We eventually named this program Starbucks Playbook. Through this experience, I learned about lean transformation from the perspective of a corporate lean team based at headquarters.  

A couple of years later, I was challenged with an assignment in a manufacturing company. Perhaps unusually, as a lean practitioner, it was my first time working in a factory. Basically, I was given a target to incorporate an isolated workstation into the nearby assembly line that it supplied.  

I ran the only play (pun intended) that I knew: I observed the relevant work in detail, defined the problem clearly, experimented “offline” with potentially better ways of doing the work, and detailed an implementation plan for the areas managers to carry out. I captured all of this on an A3 .  

But when I handed a copy of the A3 to my coach, he ripped it up! Frustrated, he pointed to the workstation and asked, “What’s changed?”  

All I could say was, “Nothing.”  

“Well, do you believe in learn by doing or not?” He then clarified my assignment. “You can’t leave until the target’s been achieved, physically. Not just theoretically on paper.” (As you might imagine, his language used was more colorful.) 

I learned more about lean transformation over the next few days than at any other time in my career. Unlike at Starbucks, I could engage directly with the people doing the value -creating work and the relevant cross-functional and managerial stakeholders needed to make changes within hours. Some of the new ideas for the work were accepted. Some weren’t. Moreover, these new ideas could be tried immediately. Some worked. Some didn’t. In other words, I could complete multiple cycles of lean transformation — improvement and learning — in a day. 

By following all the way through on my problem-solving, all the way to changing the value-creating work, I confronted every aspect of lean transformation as defined by the Framework’s five questions:  

• clarity of and alignment about the problem, 
• the work and how it would be improved, 
• the knowledge and skills ( i.e., capabilities) required for the work and its improvement, 
• the management system and leadership behaviors around the work and the workers, 
• and the basic thinking of the entire group of stakeholders.  

Nothing was left to the imagination. Nothing remained theoretical. I learned what it took to solve a problem.  

(I kept up my A3, by the way. I still needed to share the thinking and helpful narrative, supported by facts, with the people I was working with. That said, the “story” of the A3 became way more … oh, what’s the word?…ah, colorful.) 

Learning, Relearning, and Passing It Along 

I ended up sharing this story with the executives on the call. And for what it was worth, I advised them to accept the same challenge my coach had given me on that shop floor: The next time a problem comes up, tackle it. Solve it. Now. And then, once that’s done, reflect and start iteratively building the systems that will help you solve the next one even better. 

I’m sharing this story with you because I get to interact with many of you, often at your gemba . What I see is a lot of “lean stuff.” More specifically, a lot of “ lean management system stuff.” And while it’s theoretically good for problem-solving, that’s not what I typically see, in the work anyway.  

Again, it’s not that the lean stuff is “bad.” We don’t need to tear up our A3s. We don’t need to tear down our management systems. We just need to remember what matters. And when we go sideways, which we all will, over and over again, we can revisit the models and frameworks left behind by those who have been there and done that. And then, we can practice, practice, and keep practicing.   

Written by:

About Josh Howell

Joshua Howell is president and executive team leader at the Lean Enterprise Institute (LEI). For over a decade, he has supported individuals and organizations with lean transformations for improved business performance. As a coach, he helps people become lean thinkers and practitioners through experiential learning, believing such an approach can…

I been reading your posts for little longer than a year it has helped me improved my daily workload by implementing the basic lean thinking process practices. Love your inspirational posts about treating people with respect.

Leave a Comment 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.

Revolutionizing Logistics: DHL eCommerce’s Journey Applying Lean Thinking to Automation  

Podcast by Matthew Savas

Transforming Corporate Culture: Bestbath’s Approach to Scaling Problem-Solving Capability

Teaching Lean Thinking to Kids: A Conversation with Alan Goodman 

Podcast by Alan Goodman and Matthew Savas

Related books

A3 Getting Started Guide

by Lean Enterprise Institute

The Power of Process – A Story of Innovative Lean Process Development

by Eric Ethington and Matt Zayko

Related events

June 10, 2024 | Coach-Led Online Course

Managing to Learn

June 12, 2024 | Morgantown, PA

Building a Lean Operating and Management System 

Explore topics.

Subscribe to get the very best of lean thinking delivered right to your inbox

Privacy overview.

• Lean Philosophy

Effective Lean Problem Solving

Solving problems in a business setting is an important part of the Lean methodology. Using Lean strategies, a company can better identify what problems exist, pinpoint the root causes, and come up with the right solutions to get the best results. Learning about how to effectively use Lean problem-solving techniques can help any business to improve and become more efficient.

Lean Problem-Solving Process

When working to make improvements in any business setting, it is important to start by identifying problems or potential problems. Solving existing issues is a great way to eliminate waste and improve efficiency very quickly. For many businesses, this is the ideal with to create a competitive edge that will help you to succeed.

When using the lean problem-solving techniques , you will go through a series of steps to get the results that are needed. The steps in the Lean problem-solving process are as follows:

• Identify the Problem – The first thing to do is identify what the actual problem is. This should be as specific as possible and include as many details and other information as is available.
• Break it Down – Breaking the problem down into different steps or parts is critical. This will make it possible to develop the right solutions for each aspect of the problem and help get things running as they should.
• Establish Targets – It is difficult to solve a problem if you don’t know what a working system should look like. Establishing target goals for the system you are working on will help guide you through the rest of the process.
• Look for the Root Cause – No problem can be truly solved without knowing what the root cause is. Keep asking questions about the issue at hand until you discover what is truly causing the issues. This can often be done using the ‘Five Whys’ technique , where you keep asking why something is happening until you reach the root cause.
• Propose Countermeasures – Next, come up with ways that you can address the root cause. This could be one or more different actions that are designed specifically to deal with this issue.
• Implement Countermeasures – Take the countermeasures that are proposed in the previous step and begin testing them. Ideally this can be done in a small test segment, but if needed it can be done in a full production environment. If a solution seems to work in a small system, expand it out to make sure the results scale up as expected.
• Test the Results – Analyze the results by comparing the situation where the problem was found against your target results. If you are able to accomplish the goals identified as your target results, the problem-solving countermeasures are successful. If not, move back to proposing additional countermeasures to get the results you need.
• Standardize – Once you have found a proven way to address the problem at hand, it is time to roll it out to the entire environment. Establishing new processes and procedures that will be followed by everyone in the facility is the last step in the problem-solving process.

Include All Impacted Parties

When going through the Lean problem-solving process it is important to consult with all the parties that are impacted by the problem at hand. It is quite rare that one person will be able to find the best possible solution to a problem, especially if they aren’t the ones who are directly impacted by the issue. Part of the Lean methodology is to work with various teams to come up with the best way of doing things. If you are facing a problem that needs a solution, you will want to include people from various groups such as:

• Front Line Employees – These are typically the people who will deal with the problem on a regular basis. Nobody will have greater insights into the root cause, and potential solutions, than these employees. Having one or more people from this level helping to solve a problem is critical.
• Supervisor – A supervisor or department manager will be able to provide additional insights into how the problem is impacting the business. They will also be the ones to help coordinate the implementation of any potential solutions so they should be involved.
• Appropriate Management – If a problem, or the expected solutions, will require upper level management approval, someone from that team should be included in the process. It is easier to have someone from the leadership partnering with you from the beginning than to try to bring them up to speed for approval down the road.
• Customers – When appropriate, having a customer available to discuss the problem can be very helpful. Customers are sometimes the ones who have the most information about the symptoms of the problem, which can make them very helpful.

Solving problems using Lean methodologies is a great way to help improve efficiency and eliminate waste in any workplace. Having an established process in place will allow you to quickly identify and solve a wide-range of problems in any environment.

Additional Resources

• 8D for Problem Solving – creativesafetysupply.com
• Training to Use 8D Problem-Solving Tactics – blog.creativesafetysupply.com
• Design Thinking: Empathy and Iteration for Innovation and Problem-Solving – creativesafetypublishing.com
• The Great Root Cause Problem Solving Debate – realsafety.org
• No Problem is a Problem – jakegoeslean.com
• Lean Six Sigma in small companies, still effective? – lean-news.com
• Lean Manufacturing Implementation – The First 5 Steps – iecieeechallenge.org
• The Lean Method: Go To Gemba and Improve Your Quality Control – blog.5stoday.com
• Applying Hoshin Kanri – 5snews.com

Related posts:

• Total Quality Management And Kaizen Principles In Lean Management
• Why Lean Transformation Fails
• 7 Reasons to Eliminate Waste and Go Lean
• Go Lean – Visual Factory
• Lean Layout Fundamentals
• Why Single Minute Exchange of Die (SMED)?
• Why You Should Use Takt Time Production & How To Do It
• Why Six Sigma Root Cause Analysis is a Great Tool
• Seven Forms of Waste – Lean Six Sigma

• FlashLine Login
• Phone Directory
• Maps & Directions
• Business Process Analysis
• Process Mapping
• Root Cause Analysis
• 5S Methodology
• Focus Group Facilitation
• Testimonials
• Process Improvement and Lean Terminology

Lean Problem Solving

Lean Problem Solving is a way of approaching organizational problems that is characterized by continuous improvement and the use of proven, problem-solving methodologies. 

The goals of Lean Problem Solving include:

• Identifying and solving problems in less time and achievement of measurable results
• Involving everyone in the problem solving process
• Using data and process flow to focus on a problem
• Developing practical and detailed solutions

Contact us at [email protected] to learn more!

Street Address

Mailing address.

• 330-672-3000
• [email protected]
• Kent State Kent Campus - facebook
• Kent State Kent Campus - twitter
• Kent State Kent Campus - youtube
• Kent State Kent Campus - instagram
• Kent State Kent Campus - linkedin
• Kent State Kent Campus - snapchat
• Kent State Kent Campus - pinterest
• Accessibility
• Annual Security Reports
• Emergency Information
• For Our Alumni
• For the Media
• Health Services
• Jobs & Employment
• Privacy Statement
• HEERF CARES/CRRSAA/ARP Act Reporting and Disclosure
• Website Feedback

Current Openings

APPLICANT LOGIN

• REMOTE OPTIONS

DEPT OF ENVIRONMENTAL QUALITY

We are looking for results-oriented, driven individuals with a thirst for problem solving. at arizona department of environmental quality (adeq) our mission is to protect and enhance public health and the environment in arizona. through consistent, science-based environmental regulation; and clear, equitable engagement and communication; with integrity, respect and the highest standards of effectiveness and efficiency. because arizonans treasure the unique environment of our state and its essential role in sustaining well-being and economic vitality, today and for future generations. we are currently looking for employees who are committed to our agency, passionate to excel in their career and engaged in our mission. only this caliber of employee will be successful in driving our agency towards accomplishing our mission, address:  1110 w washington st. phoenix, az 85007 office of continuous improvement , salary:  $75k-$80k, closing date: open until filled.

We have an excellent opportunity for a Lean Coach to join our team. In this role, you will facilitate continuous improvement through the use of Lean Tools and Methodologies by participating in projects in all aspects of the agency and working with colleagues and functional leaders in accomplishing project goals. This position will also serve as a resource in process improvement methodologies to lead high visibility projects to ADEQ employees.

This position is available for remote work on a full-time basis within Arizona (including virtual office arrangements).

The State of Arizona strives for a work culture that affords employees flexibility, autonomy, and trust. Across our many agencies, boards, and commissions, many State employees participate in the State’s Remote Work Program and are able to work remotely in their homes, in offices, and in hoteling spaces. All work, including remote work, should be performed within Arizona unless an exception is properly authorized in advance.

• Participate in and lead projects resulting in process improvements and waste reduction. • Assist in identification, privatization and selection of potential projects in all functional areas of the agency to optimize existing processes for waste reduction and cost control. • Facilitate project team meetings and provide guidance and support to Project Team Leaders. • Work with teams to identify problems, analyze information and develop and implement process solutions. • Identify barriers to success and solicits help from leadership as and when needed. • Routinely interact with colleagues and projects leaders to ensure that projects are on track. • Report to OCI Administrator as required on progress of projects. • Assists in facilitating and conducting training of colleagues and team members in Lean Tools (Standard Work, Kaizen).

• Knowledge of lean tools and principles (Process mapping, Kaizen, Plan/Do/Check/Act cycle) • Knowledge of strategic planning, quality management and of Six Sigma • Experience leading Kaizen Improvement (facilitated problem solving and rapid implementation) • Excellent analytical skills with ability to focus on high-level strategic plan down to detailed tactical project plans • Strong program and project management skills and excellent organizational skills required • Ability to promote effective team development and encourage collaboration across the agency, • Ability to develop strong working relationships with team members, peers, and management at all levels • Ability to speak to all audiences throughout the organization, understanding the various needs of audience members, and tailoring the message to address their concerns. • Ability to manage multiple projects simultaneously in a fast-paced environment

• Bachelor's degree, preferably in Operations Management, Science or Engineering and at least Seven years (7) of relevant technical or project management experience • Valid Arizona Driver License required

If this position requires driving or the use of a vehicle as an essential function of the job to conduct State business, then the following requirements apply:  Driver’s License Requirements.

All newly hired State employees are subject to and must successfully complete the Electronic Employment Eligibility Verification Program (E-Verify).

Among the many benefits of a career with the State of Arizona, there are: · 10 paid holidays per year · Accrual of sick and annual leave beginning at 12 and 13 days per year respectively for full-time employees · Paid Parental Leave-Up to 12 weeks per year paid leave for newborn or newly-placed foster/adopted child (pilot program). · A top-ranked retirement program with lifetime pension benefits · A robust and affordable insurance plan to include medical, dental, life, short-term and long-term disability · An incentivized commuter club and public transportation subsidy program · We promote the importance of work/life balance by offering workplace flexibility · We offer a variety of learning and career development opportunities

By providing the option of a full-time or part-time remote work schedule, employees enjoy improved work/life balance, report higher job satisfaction, and are more productive. Remote work is a management option and not an employee entitlement or right. An agency may terminate a remote work agreement at its discretion.

Learn more about the Paid Parental Leave pilot program  here . For a complete list of benefits provided by The State of Arizona, please visit our benefits page

ASRS Lifetime Benefits

Persons with a disability may request a reasonable accommodation such as a sign language interpreter or an alternative format by contacting [email protected]. Requests should be made as early as possible to allow time to arrange the accommodation. The State of Arizona is an Equal Opportunity/Reasonable Accommodation Employer.

ARIZONA MANAGEMENT SYSTEM (AMS)

All Arizona state employees operate within the Arizona Management System (AMS), an intentional, results-driven approach for doing the work of state government whereby every employee reflects on performance, reduces waste, and commits to continuous improvement with sustainable progress.  Through AMS, every state employee seeks to understand customer needs, identify problems, improve processes, and measure results.   State employees are highly engaged, collaborative and embrace a culture of public service.

The State of Arizona is an Equal Opportunity/Reasonable Accommodation Employer.

If this position requires driving or the use of a vehicle as an essential function of the job to conduct State business, then the following requirements apply: Driver’s License Requirements

This website uses cookies.

We use cookies to personalize content such as job recommendations, and to analyze our traffic. You consent to our cookies if you click "I Accept". If you click on "I Do Not Accept", then we will not use cookies but you may have a deteriorated user experience. You can change your settings by clicking on the Settings link on the top right of the device.