DMAIC Projects

Revision as of 14:46, 10 February 2022

DMAIC is a project framework for working with Lean Six Sigma (LSS), which is based on both Six Sigma approach to systematic and quantitative approach to process improvements, and Lean ^[1]. A process following the Six Sigma approach aims to control the process in such a way, that no more than 3.4 defect per million possibilities, equal to all possibilities within 6 standard distributions (6σ). DMAIC is the framework used to work with process improvements, in order to reach the low failure rate. However, DMAIC can also be utilized in a different context, but is aimed at improving an existing process ^[2].

DMAIC is an acronym for the five steps in the framework, called Define, Measure, Analyze, Improve and Control. The five stages consist of:

• Define: in the define phase, what needs to be improved and for who is defined.
• Measure: the measure phase is used to further understand and document the problem
• Analyze: Based on the gathered data from the measure phase, the root causes to the problems are identified.
• Improve: With the root causes identified, a solution can now be developed, tested and pilot implemented.
• Control: The solution is first completely implemented in the important control phase. Following the implementation, it is paramount to monitor the effects, in order to ensure the change remains and works as intended.

Big idea

• Big focus on data and quantitative basis
• DMAIC projects can happen continuely – again and again – in order to perfect the process.
• Introduce SIPOC
• Between each phase of the DMAIC project, a gate meeting is held with the relevant stakeholders. During this meeting, the current results of the project is presented for the stakeholders. If the stakeholders find the current results and proposed forward direction adequete, the gate is agreed as open and the next phase can begin. This is much like the Stage-Gate_Process.
  • This is in order to ensure the final solution can work for the stakeholders.

DEFINE

• Identifying and understanding the customer. Defining Voice of Customer (VoC) and focusing the work based on this is key. The VoC typically focus on the challenges of the customer. Insert example and context.
• Critical to Quality (CTQ) follows the VoC. Defining the CTQ means to describe what is necessary to fullfill the VoC. This requires an understanding why the VoC is a problem and what could remedy this. It does however not describe a specific solution. Insert example and context. Include how the CTQ should be measureable (two levels of CTQ, more descriptive, then a hard target).
• Create figure showcasing VoC and CTQ.
• Include details about Critical to Customer (CtC) from Six Sigma. Potentially model. Used and updated continually during the project.

MEASURE

• The measure phase is focused on defining the current facts of the situation.
• A Data Collection Plan is developed to ensure the correct data is gathered, and gathered in the same way. ^[1]
• A range of types of data can be used. The typical ones, such as time consumption, error rate, units produced can be used, but other types, such as customer satisfaction and employee morale. The selected data to collect should fit the type of project and associated goal.
• Data can be collected several ways; counting, evaluating video material, questionaries, observations, etc...

ANALYSE

• Visualize the data to discover patterns.
• Utilize root cause analysis methods, such as a Fishbone_diagram.

IMPROVE

CONTROL

Application

• Utilizing DMAIC in practice. ^[3]

Limitations

• Less focused on qualitative aspects.
• A DMAIC project is quite comprehensive and for smaller improvement projects, the The A3 report might be better suited.

Annotated bibliography

References

1. ↑ ^{1.0 1.1} Josefsen, R., Bækgaard, J., & Holme, K. S. (2014). Perfekte Processer. Praktisk Forlag.
2. ↑ Morgan, J., & Brenig-Jones, M. (2012). Lean six sigma for dummies: 2nd edition. John Wiley & Sons.
3. ↑ T. M. Shahada and I. Alsyouf, "Design and implementation of a Lean Six Sigma framework for process improvement: A case study," 2012 IEEE International Conference on Industrial Engineering and Engineering Management, 2012, pp. 80-84, doi: 10.1109/IEEM.2012.6837706.