Ledger Size

Event Name:

Start Date:

ANALYZE / THINK
Future
State Map

Hypothesis
Testing
Effort /
Impact
Graph

Event Team Members:

DEFINE / BACKGROUND INFORMATION

Problem Statement:

Problem
Statement
Project
Scope
Goal

Target Date

Goal OR Objective:

Scope (if needed):

Actual Date

Target Date

IMPROVE / IMPLEMENT
After
Picture
Cycle
Time
Yield Rate

Actual Date

MEASURE / UNDERSTAND
VSM
Takt Time
Cycle
Time
Spaghetti
Chart
Baseline
Capability
Data
Collection
Plan
Before
Picture

Target Date

Actual Date

CONTROL / SUSTAIN
Control
Plan

Target Date

Target Date
Actual Date

Actual Date
Validation by Process Owner

Validation by Project Leader

End Date

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

Event Team Members: Enter the names of the people on the kaizen team and identify the Facilitator.

ANALYZE / THINK

In this section, list the actions taken by the team to think

through potential solutions for the problem.

FMEA

Graphics

Hypothesis
Tests

Team used brainstorming techniques including idea generation and 5 Whys to

identify the root causes of the problem. Main contributors were determined to be:
DEFINE / BACKGROUND INFORMATION
Problem Statement: What is the problem? How big is it? Where is it occurring? When
did it occur/start? How do you know?

Problem
Statement

Project Scope

Goal

Target Date
Actual Date
Target Date

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.

Lack of standardization of searches by Associates results in inconsistent

success.
Most Associates are not trained on the use of Boolean search capabilities.

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.

MEASURE / UNDERSTAND

Lack of consistent use to terms inhibits search capabilities.

Actual Date

IMPROVE / IMPLEMENT

DOE

Trial
Experiment

In this section document the improvements the Team has

implemented or planned:

Creative
Solutions

Pilot

Process Map

Fishbone

C&E Matrix

Data
Collection
Plan

Utilizing existing data on most commonly sought topics, a Master Search Term
lexicon was developed and distributed to all Associates in the area.

Measurement
System
Analysis

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)

Process
Capability
Analysis

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)

Average time to locate information sought is 95 seconds.

Average search success (finding the information sought) is 65%.

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.

Average number of files opened prior to finding information (includes only

successful searches) is 6.

Target Date
Actual Date

Average number of files opened during unsuccessful searches = 11.

Average time spent on unsuccessful searches = 142 seconds. I

CONTROL / SUSTAIN

Implemented tracking tick sheet to identify most commonly sought after

information by topic.

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.
Target Date
Actual Date

Validation by Process Owner

Validation by Project Leader

Mistake
Proof

Control Plan

Target Date
Actual Date

End Date