This document appears to be a template for Lean event documentation. It includes sections for defining the problem and goals, documenting the existing process, identifying improvement opportunities, planning the event, documenting the improved process and transition plan, and establishing controls to ensure the benefits are sustained. The template provides guidance on the type of information, data, and documentation that should be captured at each stage of a Lean event to effectively define the problem, implement improvements, and institutionalize the new process.

1. <Lean Event Name> <Conducted Date(s)> <Evaluated Date(s)> BB: (Name) Champion: (Name)

2. Defining the Kaizen Focus and Value

5. Describe the Baseline Condition Include Pareto Charts, trend charts, histograms etc to characterize existing process. The purpose of the chart(s) on this page is to explore what is happening with the Y or Y’s that will make this an appropriate project to execute. Plot your primary metric here. Good!

6. Project Charter {Project Name & No. Here} Assigned Define Measure Analyze Improve Control Sched Date Date Date Date Date Date Actual Date Date Date Date Date Date Process Map Number: Number here Black Belt: Name here Process Owner: Name here Champion: Name here Implementation Coordinator : Name here Data Coordinator : Name here Team Members: Name & function here Name & function here Name & function here Name & function here Name & function here Expected Benefits: Hard Savings – xxx $K Soft Savings – xxx $K Other Benefits: List benefit here List benefit here Project Timeline: Customer CTQ(s): Describe customer CTQ (customer need/defect and spec limit.) Problem Statement : List the 4 elements of a problem statement: * Defect identification * Magnitude of the defect (events/unit time, etc) * Where is the defect (location/group/segment) * Why this project is important to work now ($, BHAG support, etc) Project Scope: List project/process boundaries here by using includes … and excludes … Goal Statement: Increase(/decrease) the {primary metric} from {baseline state} to {improved state} by {date} without negatively impacting {secondary metric}.

7. SIPOC Suppliers Inputs Process Outputs Customers ?? ?? Process Description ?? ?? ?? ?? ?? ?? Process Steps Project Boundary Project Boundary ?? ?? ?? ?? ?? ?? ?? ?? ?? ?? ??

10. Kaizen Team Key Stakeholders Define Measure Analyze Improve Control John M M M M M Paul A A A A A George R M M R R Ringo I R I I I A - Approval of team decisions outside their charter/authorities, i.e., sponsor, business leader. R - Resource to the team, one whose expertise, skills, “clout” may be needed on an ad-hoc basis. M - Member of team, with the authorities and boundaries of the charter. I - Interested party, one who will need to be kept informed on direction, findings, if later support is to be forthcoming. Project Phase

11. Pre-Event Work

17. During the Event

20. Document the Transition Plan Item Description Responsibility Date Write new procedures Identify which procedures need to be documented Identify who will do it Identify when it will be done Train employees Identify which employees need to be trained Identify who will do it Identify when it will be done Use this slide to list the things that must be accomplished to transition from the baseline state to the envisioned future state

21. Assuring Implementation

22. Document the Transition Plan Item Description Responsibility Date Date Write new procedures Identify which procedures need to be documented Identify who will do it Identify when it will be done Identify when completed Train employees Identify which employees need to be trained Identify who will do it Identify when it will be done Identify when completed Use this slide to record what is accomplished to transition from the baseline state to the envisioned future state

23. Control Phase