Title: Broadly speaking, what is the Problem Solving effort intending to accomplish?
Opened by: Initiating Person/Organization
Customer: Organization(s) affected by the problem
Owner: Person ultimately responsible for problem resolution and prevention
Tracking #: Product Team or Staff and Serial number (internal)Customer Tracking #: PR/R or Equivalent (external to organization)
Date Opened: Formal initiation date
1a. Problem Description SELECT Suggested Tools & Techniques
Person Responsible: Person(s) responsible
Date Initiated: Date work began
What is or are the requirements?
To what extent are the requirements not being met?
How do weknow there is a problem?
Why was the problem chosen? [Historical background, scope, (size/extent), effect, (safety, cost)]
Are there simple graphics, drawings, or pictures to help others understand the nature of the problem? (mandatory)
Have key participants, team leaders and team members been identified?
Is there stakeholder consensus on the problem description and a pledge of resources?1b. Measurement Method/Goal Statement SELECT Suggested Tools & Techniques
Date Initiated: Date measurement
method identification began
• Is there a description of the method of measurement
that will be used to check that the problem has been
solved? If not, how will we know?
• Are there descriptions of tests and analysis demonstrating measurement methodcapability?
• Is the goal statement consistent with the problem description?
2. Containment Summary CONTAIN Suggested Tools & Techniques
Person Responsible: Person responsible for
• Have you asked what, where, when, who, and the predicted results?
• Have immediate actions been taken to ensure that the customer(s) receive product orservice which meets requirements?
• (Note: Problem cannot be closed if containment is still in effect)
• Is there a method of evaluation for measuring containment effectiveness?
• Is there an interim fix on the direct cause? (First why answer)
• Is containment extraordinarily visible, temporary in nature and does it contain data collection?
3a. Cause Analysis for ProblemCorrection CORRECT(Identify, Analyze) Suggested Tools & Techniques
Date Initiated: Date cause
analysis was begun
• Have you referred to the Problem Solving logic flow diagram?
• Is there evidence to support classification of the problem
as due to common or special cause?
• Was description of theories considered?
QN Process Model (Cause & Effect Diagram)
•Were tests performed to screen through possible root
causes and validated for conclusions?
• Were alternative solutions for correction of the problem
based on the validation of the root cause(s)?
• Were graphics used to explain as much as possible?
3b. Planning for Problem Correction CORRECT (Plan) Suggested Tools & Techniques
Date Initiated: Date planning beganSuggested Questions:
• Did you describe why the solution was
chosen instead of alternative solutions?
• Can you justify the choice of this solution over the alternatives? (Scope of control, relevance, resources, payback, buy-in, etc.)
• Is there a planned method for checking whether the solution corrects the problem, level and type of Error Proofing used?
• Will the proposed change require PPAP(Production Part Approval Process)?
• Is there a planned method for checking potential side effects?
• Have all the stakeholders agreed to the plan? (Approval required through Change Management Process.)
3c. Implementation of Problem Correction CORRECT (Implement)
• Have you utilized the elements listed
below when implementing the planned solution?