Kaizen Week

From apppm
(Difference between revisions)
Jump to: navigation, search
Line 31: Line 31:
 
*End the day by starting a “newspaper” with photos of the process before any change; this newspaper summarizes all the completed actions and findings in a format that is easy to assemble and access. Finally, set priorities for the activities of the second day.
 
*End the day by starting a “newspaper” with photos of the process before any change; this newspaper summarizes all the completed actions and findings in a format that is easy to assemble and access. Finally, set priorities for the activities of the second day.
  
==Day 2==
+
==Day 2== '''prova'''
 
*Quantify the impact of waste identified at first day: elements of the Overall Equipment Effectiveness (OEE) metric should be decomposed to understand the losses in line capacity and identify important losses to be eliminated or reduced.
 
*Quantify the impact of waste identified at first day: elements of the Overall Equipment Effectiveness (OEE) metric should be decomposed to understand the losses in line capacity and identify important losses to be eliminated or reduced.
 
*Design an optimum flow, establish effective operator sequences, define measures and metrics, optimize organization layout and implement it with the support of tools and graphical analysis. Use also team-based tools e.g. brainstorming, cause-effect matrices, Spaghetti Charts and Failure Mode Effects Analysis (FMEA).
 
*Design an optimum flow, establish effective operator sequences, define measures and metrics, optimize organization layout and implement it with the support of tools and graphical analysis. Use also team-based tools e.g. brainstorming, cause-effect matrices, Spaghetti Charts and Failure Mode Effects Analysis (FMEA).

Revision as of 10:38, 28 September 2017

Abstract: With the increased use of lean thinking in recent years, many organizations are using Kaizen events to rapidly introduce change and to create a culture of continual improvement. From a definition easily findable in many articles or books talking this topic, Kaizen event is “a focused and structured improvement project, using a dedicated cross-functional team to improve a targeted work area, with specific goals, in an accelerated timeframe”. It means that this methodology accelerates the Kaizen process in a segment of the production chain or a particular manufacturing cell, where the team participants are managers, engineers, maintenance workers, marketing and finance personnel and production operators. Typically, this event lasts from three to five days. Kaizen Week is a short-term improvement projects that can be defined such a Kaizen event lasting five working days. The scope of this article is to describe this kind of Kaizen event, specifying how it works day by day and explaining its purpose. Finally, the article will evaluate limits and needs on using this tool.


Contents

General description

Word “Kaizen” is the composition of two Japanese terms, “KAI” (change) and “ZEN” (better). Thus, “change for better” recalls the fundamental concept of continuous improvement from lean thinking. Kaizen events are often associated with lean production and they can result in substantial improvements in technical system outcomes, such as lead time, work-in-process inventory and productivity, as well as in social system outcomes, such as employee knowledge, skills, and attitudes aligned with continuous improvement. In the execution of a Kaizen Week there are these following typical activities, carried out during the five days: team training, documentation of the current state, identification of opportunities for improvement, improvement selection with implementation, results presentation and documentation of an action item list for follow-up activities. [1]

Introduction

After selected the intervention area, the method expects the definition of pursuing goals with operations in terms of lead-time reduction, stock and space reduction, man operations reduction, production waste reduction, time of set-up reduction; all of this has done by considering any constraints. The launch of initiative needs the definition of group work (10 people maximum), nomination of group’s leader, meeting of direction with the group work and planning the Kaizen Week (KW); the week musts take place with active production of the concerned department.

Operational preparation

Data collection is needed to photograph the current situation and this is done through the detection of selected area with the study of its layout, the description of most relevant flows, the overview of standard work and standard operations and the evaluation about how much workload each operator have. After the initial data collection, follows the arrangement of group work required material during the week, i.e. forms and various materials (e.g. stopwatch, pencils, glossies, cardboard, wood); furthermore, also need the preparation of material for team member formation. Always here, is determined the meeting place of group, the organization of a final meeting where group work will show at direction the work made; finally, there is the drafting detail plan of KW activities, the week goals validation with team leaders and the announcement to selected people for the team on the work program.

Execution of Gemba Kaizen Week

Gemba (https://en.wikipedia.org/wiki/Gemba) is another Japanese term means “the real place” and it refers to the place where value is created; in this case is aimed to operative work of groups in the ward from Monday to Thursday. During the execution of KW, everyday there are brief meetings at the beginning and end of the day to review activities and conclusions. Important is final presentation of works and analysis of results on Friday.[2]

Follow Up

After KW the results obtained should be carefully studied and passed 15-20 days there will be implementations of checking intervention with next results consolidation evaluation. Finally, there will be the definition of development plan where changes should be made for optimizing work process.


Application day by day

Example of KW in manufacturing process: following procedure is not strict, but a company may adapt it to its needs.[3]

Example of Schedule

Day 1

  • Agree project scope: the charter should be communicated, participants should be trained and the process should be physically viewed. Through communication of the charter and a brief overview of the process, team members will be instructed on the objectives for the KW and their individual responsibilities in the process. Site leadership should participate in the kickoff session to emphasize the importance of the event and grant authority to the team to make required changes.
  • Observe the process: after created a first draft of the Value Stream Map (VSM), elements of waste should be identified with measure of cycle time, capture work sequence and determine optimum staff requirements.[4]
  • Process performance should be illustrated with time series charts, histograms and Pareto charts as necessary; finance personnel must participate to provide perspective on the business impact of the historical performance relative to the objectives.
  • End the day by starting a “newspaper” with photos of the process before any change; this newspaper summarizes all the completed actions and findings in a format that is easy to assemble and access. Finally, set priorities for the activities of the second day.

==Day 2== prova

  • Quantify the impact of waste identified at first day: elements of the Overall Equipment Effectiveness (OEE) metric should be decomposed to understand the losses in line capacity and identify important losses to be eliminated or reduced.
  • Design an optimum flow, establish effective operator sequences, define measures and metrics, optimize organization layout and implement it with the support of tools and graphical analysis. Use also team-based tools e.g. brainstorming, cause-effect matrices, Spaghetti Charts and Failure Mode Effects Analysis (FMEA).
  • Create a cycle time analysis, the identification and quantification of value-add versus non-value-add work, and the understanding of current standard work combinations.
  • Identify solutions and prioritize opportunities for improvement. At this point the team should identify additional resources necessary to complete the task list, report to management any potential barriers, begin the process of transferring knowledge to support culture change and reasons to embrace the new ways.

Day 3

  • Develop solutions to eliminate critical waste, develop new flow scenarios with new standard work combinations, prioritize changes, plan the implementation, create contingency plans, and begin solution implementation.
  • Complete the new layout implementation and create a future state VSM or process map for illustrating the changes impact visually.
  • Improvements should always be biased toward simple and self-manageable solutions. Complicated or expensive solutions must be reviewed with management and finance to quantify the expected benefits. Proposed changes should also be reviewed with departments such as health and safety, and unions so time is not later wasted with approvals and enrollment.
  • The team should begin implementing changes on this day in order to alleviate some of the burden for the fourth day. Newspaper updates should be prepared again.

Day 4

  • Implement measures and metrics: it is a long day with intense focus on implementing the changes with minimal impact on the operation, documenting new process and standard work.
  • Apply 5S techniques (Sort, Straighten, Shine, Standardize, Sustain) when equipment is rearranged, cleaned and repaired; collect data in order to understand the impact of the process changes and provide feedback for multiple iterations of minor changes to optimize the process.
  • Quantify results with calculation of financial impact.
  • All meetings on this day should take place on the production floor or process area. It is important that management is present at the end of the day to show support for new processes and discuss ways to sustain the changes.

Day 5

  • Align workforce and objectives: launch the new process for regular processing of demand and prepare a report based on the results achieved; any final report should be a simple summary of the information already compiled in the Kaizen newspaper during the week
  • Assess benefits from new-old cycle time and other measures as appropriate: data collection plans and response plans should be in place to monitor performance and respond to problems over the next several weeks.
  • Conduct lessons learnt review with stakeholders where it is explain what worked well and what did not; the intent is to capture best practices and learnings to be applied to future Kaizen events.
  • Plan follow up review in 30 days: review the task list and Kaizen metrics for completion every week for four weeks, or until all items are completed; the task list should assign responsibility to specific employees and list deliverable dates for each task.

Method Features

  • Focus on aims: all weeks must begin presenting at work group clear goals, quantifiable and ambitious. At the end of each day of KW, group work must indicate clearly what extent it is in achieving that goals.
  • Physicality: all improvement activities must be carry out in the office looking at the materials, operators, information and equipment. For example in production, working phases are defined placing physically all material in tidy according to the work sequence. Or else, cycle times are improved trying several solutions with the physically moving of documents, equipments and operations.
  • Rigorousness: all activities have to be conducted and documented using the standard module developed for the week; i.e. Spaghetti-Chart for operators flow analysis, Standard Work Sheet and Percent Load Chart for operations flow analysis, Kaizen Idea Board for representing improvement proposals, Kaizen News for indicating activities to complete after week and Target Sheet for representing achieved results day by day.
  • All group components must present something during the meeting with the direction at the end of the week.[5]

Key points

  1. Flow Analysis. The general question is “how does product value flow along the process?” Several specific questions must be done for seeing the activities properly:
    • How do the materials flow through the process?
    • How do the operators move during the process?
    • How do the information and operations flow during the process?
    • How does the equipment flow during the process?
    • How does the quality flow during the process?
  2. Standardization. “Where there is no Standard there can be no Kaizen” Taiichi Ohno. It means that at the end of each KW, all activities subject of improvement must be standardized and for doing this, it is needed: look at the activities, identify several activities by standardize and standardize them.
  3. Visual Management. The process standardization must be realized through visual and instant systems. Thus, the process can have a built-in quality and then could be a standard process. Example of some tools: billboard in the office for cycle time, layout and productive line roles; a visual Standard Work Sheet in each phase of the productive line and a physical place for everything.

The Kaizen weeks program does it must indicate not only the areas of intervention, but it must also define lines and above all the intervention guide and the final “vision” of the office or service concerned transformation, at least in terms of layout and of flow for each product family.[6]

Consulting and KPO

The proper management of group work is the most important lever that is available during the week. It is of primary importance to train the team leader training, especially during the first times that KW is implemented. Usually, a consultant of lean management conducts a special training session for team leaders: it is recommended that all aspiring team leaders attend this preliminary training to prepare them for their future roles. The need of a consulting company has a not negligible cost, but it is very important for being followed in performing properly and for arriving to a successful conclusion. The KW is a technical method sometimes used for introducing the Toyota Production System (TPS) to the company: this first step allows understanding how to change the entire company, making it lean. In this case, the Kaizen Promotion Office (KPO) is of major importance: KPO is the body that assists various business sectors for applying the tools of TPS. What are the roles of KPO?

  • Analyze processes and locate Muda, Japanese word meaning “futility, uselessness, wastefulness”
  • Plan Muda elimination actions
  • Supervise Kaizen Weeks
  • Facilitate communication between ward activity and managerial goals, turned to cost reduction
  • Develop human resources in lean optics by providing an appropriate training theoretical and applied
  • Develop specialists of TPS and promote lean system.

To canalize the flow value is the absolute priority and this requires a drastic change on the corporate structure: KPO has a high-level role because he must maintain a continuous pressure for realizing revolutionary changes necessary to introduce the Toyota Production System. Usually, in this phase the training needed for a manager is to follow 12 Kaizen weeks in a year and to become a strong supporter of TPS! To implement TPS and to maintain KPO, the company has to make large investments and must bear significant costs for carrying on the change: before making this important step, entrepreneur or top management must be extremely convinced that lean philosophy will work and he must know that once the change begins, halt the process can lead to a gradual return to normality, losing all benefits achieved as well as the amount invested.[7] Operations with a mature Kaizen culture will design facilities to support the frequent process changes necessary to maintain optimal performance in a changing economic environment. For example, equipment designed for mobility, power and air drops designed for quick reconfiguration, moveable lighting on tracks, strategically placed (or minimized) vertical structural supports, elimination of walls, and floors and pathways that are easy to clean and re-mark are all examples of structural design components that can enable more efficient Kaizen execution.

Limitations & Conclusions

Kaizen is a powerful tool for positive change. With proper planning, appropriate use of data and effective tool application, these events deliver significant results to process improvement and financial impact to businesses. Additionally, Kaizen is an effective tool for helping people learn about their own processes (what works, what does not work and what is possible) and for empowering them to effect change. These outcomes cannot be quantified financially, but they are an important foundation for a continuous improvement culture and a committed workforce that accepts responsibility for the performance of their processes. The priceless outcomes of Kaizen may well be more valuable to your organization than the directly quantifiable process improvements. A single Kaizen Week is certainly a strong signal for the potentiality of “lean” approach, but by itself is not sufficient for a true company transformation. Relevant results that could be obtained during a KW, may be lost if management do not keep the pressure high through the grip of what has already been achieved and the launch of others Kaizen weeks.


References

  1. Eileen M. Van Aken, Jennifer A. Farris, Wiljeana J. Glover, Geert Letens, (2010) "A framework for designing, managing, and improving Kaizen event programs", International Journal of Productivity and Performance Management, Vol. 59 Issue: 7, pp.641-667
  2. Masaaki Imai, “Gemba Kaizen: A Commonsense, Low-Cost Approach to Management”
  3. Robert Tripp, Chris Seider, Ulices Calderon, Mike Carnell, “A Plan for a Five-day Kaizen”
  4. Quarterman Lee, Brad Snyder, “The Strategos Guide to Value Stream and Process Mapping”
  5. Geoffrey Mika, “Kaizen Event Implementation Manual”
  6. William Wes Waldo, Tom Jones, “A Team Leader’s Guide to Lean Kaizen Events”
  7. Charles B. Brown, Terry R. Collins, Edward L. McCombs, "Transformation From Batch to Lean Manufacturing: The Performance Issues"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox