The document describes the Six Sigma DMAIC process for improving solutions. It involves developing decision statements and criteria to evaluate solutions, generating potential solutions using techniques like brainstorming, screening solutions against criteria, conducting cost-benefit analyses, using failure mode and effects analysis to assess risks, and piloting solutions before full implementation. The goal is to define and validate solutions to problems in a systematic, data-driven manner.
The document describes the Six Sigma DMAIC process for improving solutions. It involves developing decision statements and criteria to evaluate solutions, generating potential solutions using techniques like brainstorming, screening solutions against criteria, conducting cost-benefit analyses, using failure mode and effects analysis to assess risks, and piloting solutions before full implementation. The goal is to define and validate solutions to problems in a systematic, data-driven manner.
The document describes the Six Sigma DMAIC process for improving solutions. It involves developing decision statements and criteria to evaluate solutions, generating potential solutions using techniques like brainstorming, screening solutions against criteria, conducting cost-benefit analyses, using failure mode and effects analysis to assess risks, and piloting solutions before full implementation. The goal is to define and validate solutions to problems in a systematic, data-driven manner.
The document describes the Six Sigma DMAIC process for improving solutions. It involves developing decision statements and criteria to evaluate solutions, generating potential solutions using techniques like brainstorming, screening solutions against criteria, conducting cost-benefit analyses, using failure mode and effects analysis to assess risks, and piloting solutions before full implementation. The goal is to define and validate solutions to problems in a systematic, data-driven manner.
Download as DOCX, PDF, TXT or read online from Scribd
Download as docx, pdf, or txt
You are on page 1of 9
Six Sigma DMAIC Process – Improve
Phase - Solution Parameter
To define and come up with solution parameters for statistically validated X’s we need to: • Develop Decision Statement • Develop Solution Criteria • Classify Solution Criteria • Refine Solution Criteria Develop Decision Statement: Solutions should be generated to clarify the purpose of the decision to be made. Parameters to be considered while drafting a decision statement are: 1 How will you manage expectations of customer? 2 How will you establish boundaries on alternatives to be considered to resolve the problem? 3 How will you reflect on prior decisions taken – “Level of Decision”? The next thing to do is to Develop a Decision Statement and generate a list of six to twelve criteria to solve the problem. Consider desired results, restrictions being faced and availability of resources. Classify Solution Criteria: Once criteria have been listed, we have a clearer statement of the objectives against which to judge the various alternatives. In most situations, criteria vary in their degree of importance. We need to classify these criteria to reflect their relative influence on the solution choice. We divide criteria into two basic categories: 1 Absolute Requirements or “Musts” – Mandatory, realistic and measurable requirements which help the project team to screen out unacceptable alternatives. 2 Comparison Criteria or “Wants” – Desirable characteristics which provide a basis for comparison for criteria. Refine Solution Criteria We need to refine the wants and musts criteria before generating possible solutions. The solution criteria can be refined by: Clarifying Everyone’s Understanding – Clarify everyone’s understanding about each criteria by discussing and restating each criteria. Make use of the SCAMPER tool to refine or synthesize the solution criteria.09 SCAMPER is a checklist of idea-spurring questions and stands for: • S – Substitute • C – Combine • A – Adapt • M – Modify Or Magnify • P – Put to other Uses • E – Eliminate Or Minify • R – Reverse Or Rearrange Weighing the “Wants” – Weigh the ‘wants’ to reflect upon the relative importance of each want criteria by using a Likert scale of 1-10. 110 Six Sigma DMAIC Process – Improve Phase - Generate Possible Solution Involve those who will be Affected: We need to make sure we solicit the upfront involvement of People affected by the problem or its solution and People with expertise in the subject matter. We should then Focus on the Root Causes i.e. Make the affected parties revisit the significant root causes to get to a solution. Then, pick on Idea Generation Technique. Five key techniques used for idea generation and synthesis are: 1 Brain-writing 2 Benchmarking 3 Assumption Busting 4 Creative Brainstorming 5 Modified Brainstorming Idea Generation Technique - Brain-writing Brain-writing is a technique used to generate many ideas in a short period of time. Two key modified brainstorming techniques used are Brain-writing 6-3-5 and Constrained Brain-writing. Brain –writing 6-3-5 - The name brain-writing 6-3-5 comes from the process of having 6 people write 3 ideas in 5 minutes on a pre-defined parameter. Constrained Brain-writing: The name constrained brain-writing comes the fact that on certain occasions the team may want to have a set of constrained ideas around a pre-determined focus, rather than ranging freely. Idea Generation Technique - Benchmarking Process benchmarking is a technique of continually searching for the best methods, practices and processes, and either adopting or adapting their good features and implementing them to become the “best of the best”. Idea Generation Techniques – Assumption Busting Assumption busting as a technique is used to trace back from the current performance problems to identify rules and then surface underlying assumptions. The key steps involved in assumption busting are: • Revisit the current problem at hand.1 • Identify the rule(s) responsible for the problem. • Trace the rule(s) back to an assumption in the process. • Test to break the assumption – Is it wrong from the start? Or, Can it be made untrue? For example: In a personal loan approval process the problem is lengthy cycle time for approvals which is leading to dissatisfaction. Investigation of the process reveals that there is a rule existing in the process which makes every vital task in processing the loan pass through a specialist (legal expert, financial expert, credit expert) after it has been processed by an agent. The reason for rule existing in the process is an assumption which says that all loan deals are complex. On investigation and data collection it is found that only 5% of deals are complex and thus the process assumption is wrong. I d e a G e n e ra t i o n Te c h n i q u e – C re a t i v e Brainstorming Nominal Group Technique: The nominal group technique is a structured method to narrow down & prioritize on a list of choices. It is called “nominal” because during the session the group doesn’t engage in the usual amount of interaction typical of a team. Because of this relatively low level of interaction, nominal group technique is an effective tool when some group members are new to each other, relatively low level of interaction is required, issues are of highly controversial nature and a team is stuck in disagreement. Idea Generation Technique – Modified Brainstorming Modified brainstorming technique makes some basic and/or simple amendments to the “regular” creative brainstorming in order to help expand the number and quality of ideas. Three key modified brainstorming techniques used are: Analogy Technique, Channeling Technique and Anti-Solution Technique. Analogy Technique - The ideas generated on the “analogy” then get translated to the real situation (the problem at hand). Channeling Technique – We begin by listing “categories” of ideas for the issue at hand. Then, as the team brainstorms, over a period of time it can “change channels” when new ideas slow down. The objective is to capture a broad range of ideas (several channels), as well as of quantity (as many ideas as possible in each channel). Anti- Solution Technique - We begin by brainstorming around the opposite of the issue at hand. This is probably the easiest of modified brainstorming methods. For example, rather than brainstorming on ways to ensure complete information on a personal loan form we brainstorm on how to ensure we get no/incomplete information on the personal loan form. 113 Six Sigma DMAIC Process – Improve Phase - Screen Against Musts and Wants Once possible solutions are listed, we can begin the process of seeing how they perform against the solution criteria. We base our assessment on the best available information about each alternative. In addition to known facts, this information may take the form of our best projections or the opinion of experts. The criteria serve as the guide for our data gathering. For each criteria we must have complete information about all of the alternatives, so that we can make a reasonable judgment.114 Six Sigma DMAIC Process - Improve Phase - Conduct Cost-Benefit Analysis Cost-benefit analysis weighs the real costs of a potential solution under consideration against the potential benefits of the solution. Consider all costs associated with getting the proposed solution up and running. Cost examples would be: Capital investment needed, Implementation costs (time of project team, process improvement costs, etc), Start-up costs (training, lost production during switch from the old to new process), Operation costs (additional cost of running new process compared to old process). The steps involved in doing a cost-benefit analysis for possible solutions are: • Consider all costs associated with getting solution up and running • Quantify benefits of a fully implemented solution • Compare the real costs of solution against potential benefits Does the identified solution have any risk? Risk can be mitigated for the proposed solution by Identifying potential problem if any with the solution, Ensuring that the solution attempts to reduce the opportunity for error if not eliminated, Is it an “All terrain” or a" Feather bed” solution – How robust is the solution and Understanding the Failure Modes and Effect Analysis. 115 Six Sigma DMAIC Process – Improve Phase - Failure Mode Effect Analysis (FMEA) FMEA identifies all the probable failure modes for the product or process. It prioritizes the failure modes for focused attention by using a scoring model based on Severity (S), Occurrence (O) and Detect ability (D). RPN = S*O*D Based on the above suitable action plans can be created to contain the risk. It is used as a living document and could be a good foundation for building robustness. Definition of Terms: • Failure Mode – The way in which a specific process input fails • Effect – The impact the failure has on the Critical Quality Parameter • Cause – The source of variation that caused the process to fail • Current controls – Systemized devices in place to prevent or detect the failure • Severity – Importance of an effect on critical quality parameter (1-Not severe; 10 – very severe) • Occurrence – Frequency with which a cause occurs (1-Not likely; 10-Very likely) • Detection – Ability of current control to detect the cause before creating a failure mode (1-likely to detect; 10-not likely to detect) • RPN is an acronym for Risk Priority Number. It is calculated by multiplying the Severity, Occurrence and Detectability. 117 Six Sigma DMAIC Process – Improve Phase - Pilot Solution Implementation In general, there is a way to pilot all or some part of every solution that you will want to implement. It is almost always worth the extra effort to pilot. You certainly need to pilot when the scope of the change is large, the change could cause far-reaching unintended consequences, implementing the change will be a costly process and the change implemented would be difficult to reverse. The key steps involved in conducting a pilot are strong leadership from top management, select a steering committee/pilot team, conduct briefings with the pilot team, pilot planning for issueless execution, sell to employees affected under pilot, employee training for pilot execution, pilot implementation on the shop-floor, debriefing after pilot implementation and extend to a second area, if required. 119 Six Sigma DMAIC Process - Improve Phase - New Process Capability / Mapping New Process Capability can be calculated using DPMO Method or Z value method as discussed in the Measure phase. New Team Targets: With the desired results coming from the pilot, the current process baselining needs to be revisited. The new process capability achieved should be made the basis of re-baselining exercise and we need to set new internal team targets accordingly for the staff. With the desired results coming from the pilot, the new improved process “should-be” needs to be mapped. While mapping the new process, we should consider the following workflow instructions: • Establish a product orientation or customer orientation • Establish one-at-a-time processing • Balance flow through bottleneck • Drive parallel processing • Reduce handoffs 121 Six Sigma DMAIC Process - Control Phase - What is a Process Control? A control mechanism that ensures that the process performance be maintained are at level that satisfies the customer ’s need and drive the ongoing improvement of process performance. The key elements that constitute a process control system are • Documentation of the process • Develop process metrics • Monitor the process based on the defined metrics When we talk of a process is operating "In-Control" it translates to a situation that only common cause variation is present, process is predictable and process is stable. Control limit Vs Specification Limit Control Limits: It is defined based on process performance. It help determine if the process is “in control”. It is plotted on control charts and it changes when there is a verified, significant change to the process. Specification Limits: It is provided by the customer part of SLA. It help determine if the process is producing defects. It is not plotted on control charts and it changes when requirement comes from the customer.
Six Sigma DMAIC Process - Control
Phase - What are Control Charts? Control Chart is a graphical tool that helps determine if a process is “in control or not”. A control chart has three zones and is graphically represented as: Six Sigma Control Chart Zones Common Causes and Special Causes which result with Variations Characteristics of Common Causes: • Present all the time • Have a small effect individually • Result in random variation • Effect can be tolerated Characteristics of Special Causes: • Not always present • Come from outside influences • Typically have bigger influence than common causes • Effect we want to hear about Six Sigma Common Causes and Special Causes Six Sigma DMAIC Process - Control Phase - SPC - Out of Control A process is said to be out of control if: • One or more data points fall outside the control limits • Seven consecutive data points increasing or decreasing • Eight consecutive data points are on one side of average • Fourteen consecutive data points alternating up & down • Two data points, out of three consecutive data points, are on the same side of the average in zone A or beyond • Four data points, out of five consecutive data points, are on the same side of the average in zone B or beyond • Fifteen consecutive data points are within zone C (above and below the average) 124 Six Sigma DMAIC Process - Control Phase - Leading Indicator vs Lagging Indicator While interpreting control charts we also talk of two indicators: Leading indicator: A leading indicator shows the trend before the defect occurs. For example, you may be able to see a trend of six downward points. This is a leading indicator that the process will produce a defect outside the lower control limit. Lagging indicator: A lagging indicator is an outlier that is already outside the upper or lower control limit. This is a lagging indicator that the defect has already occurred in the process. 127 Six Sigma DMAIC Process – Control Phase - Risk Assessment and Mistake proofing - Poka Yoke Risk needs to be assessed on the “should-be” process to make the implemented solution more robust. Risk assessment of the new improved process makes sure that any potential effects of the possible failure modes do not result in loss of “holding of gains” over a period of time. Two key techniques to assess risk and make sure that no possible failures occur post control phase are: • Failure Modes and Effects Analysis • Mistake Proofing (or Poke Yoke) Mistake Proofing – Poke Yoke: Mistake proofing or poke yoke (derived from two Japanese words poka – inadvertent errors and yokeru – to avoid) helps de-link the Y’s from the X’s. Mistake proofing eliminates the potential for a problem to happen. The key mistake proofing techniques are: • Shutdown – Shutdown or stop a process immediately on occurrence of a failure • Control – Eliminate the occurrence of failure in a process • Warning – Proactively notify the occurrence of failure in a process before it occurs The three methods for prediction and detection approach are: • Contact method – Contact with the part in the process highlights the errors • Fixed-value method – Errors are detected in the process through counting • Motion-step method – Errors are detected by a motion or lack of it in the process
Six Sigma DMAIC Process - Control
Phase - Control and Implementation Plans The four techniques used for process control plans are: • Standardization • Documentation • Monitoring Plan • Response Plan Standardization: Standardization of the “should-be” process steps is required to ensure all responsible for execution have the same understanding. Standardizing the shouldbe process helps answer queries like: • What are the steps in the process? • Who does these steps in the process and when? • Where more detailed work instructions can be found? Documentation: Documentation is a necessary step to insure that the learning gained via improvement is institutionalized and shared across the team by having it documented with proper work procedures. Often the live processes have a tendency to evolve in an ad-hoc manner. How to accomplish each process activity is usually left up to the individuals and thus, much of the organizational knowledge resides only in the minds of all those responsible for execution. Procedure: A procedure is the documented sequence of steps & other instructions necessary to carry out an activity for a process. Monitoring Plan: Monitoring: It helps detect changes as and when they occur in the process and assure that improvements continue to hold for us to be able to meet customer requirements over a period of time. While observing a process a monitoring plan helps define: • Key process and output measures for ongoing measurement of the improved process • When data is to be collected and at how often • Define the method for gathering, recording, and reporting data on the measures Response Plan: Response plan helps identify the next steps on what needs to be done if one detects a change in the process while monitoring. For each of the measure in the monitoring plan, the response plan helps define: • What actions will be taken for an out-of-control event occurrence with a timeframe for the action • Who takes action based on the monitoring data • Where to find trouble-shooting procedures to fix problem
The key elements of a full scale implementation plan are:
• Clear Objectives • Pilot Learning's Incorporated • Implementation Milestones • Resource Needs • Influence Strategy • Implementation Budget • Process Control Plan • Process Documentation
Six Sigma DMAIC Process - Control
Phase - Review and Sign-off The project gets closed when defect reduction is demonstrated over a significant period of time. Black belt and master black belt agrees on time period needed to collect and analyze data. If improvement is not confirmed, project will be reopened. The problem is “turned off” with confirmation run (and “turned on” when old process is used again). The idea of “on-off” is key. We don’t want shift and drift caused by other variables to lead to a wrong decision. Project financial scorecard signed by six sigma champion, black belt, deployment leader, finance manager, process manager, and functional head. The leadership team agrees with the stated benefits.