1. Ledger Size DEFINE / BACKGROUND INFORMATION Problem Statement: Goal OR Objective: Scope (if needed):  Problem Statement  Project Scope  Goal Target Date Actual Date ANALYZE / THINK  Future State Map  Hypothesis Testing  Effort / Impact Graph Target Date Actual Date IMPROVE / IMPLEMENT  After Picture  Cycle Time  Yield Rate  Target Date Actual Date CONTROL / SUSTAIN  Control Plan Target Date Actual Date Validation by Process OwnerValidation by Project LeaderEnd Date Event Name:Start Date: Event Team Members: MEASURE / UNDERSTAND  VSM  Takt Time  Cycle Time  Spaghetti Chart  Baseline Capability  Data Collection Plan  Before Picture Target Date Actual Date

2. Event Team Members: Enter the names of the people on the kaizen team and identify the Facilitator. Event Name: Click here and enter the name of the Kaizen or other Event and the area in which it is being held. Start Date: Enter the date the kaizen starts DEFINE / BACKGROUND INFORMATION MEASURE / UNDERSTAND ANALYZE / THINK IMPROVE / IMPLEMENT CONTROL / SUSTAIN Target Date Actual Date Target Date Actual Date Target Date Actual Date Target Date Actual Date Target Date Actual Date Problem Statement: What is the problem? How big is it? Where is it occurring? When did it occur/start? How do you know? Goal or Objective: State the desired result of the kaizen. A Goal always meets this format: Increase/Decrease the {Primary Metric} from {Baseline/Current} to {Desired Performance Level} by {Date}. If you lack the information to specify each of these variables you may insert “TBD”. In this case you have an Objective which allows you to being your kaizen but requires that you circle back and finalize during the event. Scope: Optional. Use this to clarify what will and will not be addressed during the kaizen if you believe there may be confusion. Use this section to document the steps taken by the team and the conditions they found. For example: “Conducted 16 observations with 5 different Associates representing a range of experience and performance levels. Average time to locate information sought is 95 seconds. Average search success (finding the information sought) is 65%. Average number of files opened prior to finding information (includes only successful searches) is 6. Average number of files opened during unsuccessful searches = 11. Average time spent on unsuccessful searches = 142 seconds. I Implemented tracking tick sheet to identify most commonly sought after information by topic. In this section, list the actions taken by the team to think through potential solutions for the problem. Team used brainstorming techniques including idea generation and 5 Whys to identify the root causes of the problem. Main contributors were determined to be: Lack of consistent use to terms inhibits search capabilities. Lack of standardization of searches by Associates results in inconsistent success. Most Associates are not trained on the use of Boolean search capabilities. In this section document the improvements the Team has implemented or planned: Utilizing existing data on most commonly sought topics, a Master Search Term lexicon was developed and distributed to all Associates in the area. Master Search Term lexicon to be updated and enhanced with the data gathered through the tick sheet. (Team, 7 and 30 day follow-up sessions) Boolean search techniques training deck to be developed and cascaded to all area Associates. (Sue B. and David L, 11/30/09) Help File creation SOP to be revised to require use of Master Search Terms in all documents. (Tracy Q., 11/30/09) Recommendation that all existing Help File documents be rewritten to incorporate Master Search Terms being communicated to Ops Mgr Becky W. for follow-up and assignment. Document the interventions put into place to ensure that the improvements implemented do not fall out: Quarterly Help File audits on all newly-added documents to ensure compliance to MST.  Problem Statement  Project Scope  Goal  Process Map  Fishbone  C&E Matrix  Data Collection Plan  Measurement System Analysis  Process Capability Analysis  FMEA  Graphics  Hypothesis Tests  DOE  Trial Experiment  Creative Solutions  Pilot  Mistake Proof  Control Plan Validation by Process OwnerValidation by Project LeaderEnd Date