STEP 1: DEFINE THE PROBLEM Problem Statement: What is the problem? A problem is a discrepancy between a standard and the current situation. The ‘standard’

Slides:



Advertisements
Similar presentations
A3 PROBLEM SOLVING TOOL: Date: Contact: SOLUTIONS / COUNTERMEASURES What solutions will solve the root causes? (Tools: Brainstorming and Affinity Diagram)
Advertisements

Lean Training A3. Agenda What is it? What’s it for? How does it work? When do you use it? What’s an example?
Project leaders will keep track of team progress using an A3 Report.
Title: The title should accurately describe the issue to be addressed and can never contain a proposed countermeasure. Overview Note: Remember that the.
Ledger Size DEFINE / BACKGROUND INFORMATION Problem Statement: Goal OR Objective: Scope (if needed):  Problem Statement  Project Scope  Goal Target.
Tool: Benchmarking Purpose: provide realistic goals and direction; monitor performance; improve processes to match the best in Higher Education. Benchmarking.
Project Storyboard Template
PHD Performance Management Program Matt Gilman Spencer Soderlind Brieshon D’Agostini October 19, 2011 PDCA Training Series 2 DO 1.
By Saurabh Sardesai October 2014.
A3 PROJECT CHARTER: Date: Sponsor: VISION OF SUCCESS What outcomes or results do you want to see? What does success look like for our customer? What does.
Paul Prunty The 7 Basic Quality Tools ~ The DMAIC Process Continuous Improvement and … To a hammer, everything’s a nail … How many tools do you have in.
Project Planning Day 2 An Old Adage: Fail to Plan... and You Plan to Fail!
Lean Sigma Overview and its Significance to Project Management Harjit Singh, PMP
6  Methodology: DMAIC Robert Setaputra. PDCA / PDSA PDCA / PDSA is a continuous quality improvement tool. PDCA is introduced by Shewhart. PDSA is Deming’s.
Barry Murash MBBit Nortel 2007
Overview of DMAIC A Systematic Framework for Problem Solving
Six Sigma Black Belt Project Information Prepared: July 20, 2004.
1. 2 What is Six Sigma? What: Data driven method of identifying and resolving variations in processes. How: Driven by close understanding of customer.
Managing Project Quality
Title Defining a Project.
1 Project Name Team Lead Location Month XX, Year.
Greater Cincinnati Lean Improvement Consortium
Therefore improvements are required to ensure a sustainable healthcare system able cope with an increasing demand that: a. NHSG has knowledgeable and confident.
Black Belt Project Storyboard Template
ASQ Raleigh ASQ Raleigh Section 1113 Six Sigma SIG DMAIC Series.
 Name  Work experience  Background in continuous improvement activities  Expectations 1.
2 FOR INTERNAL USE ONLY Project Chartering  Define the components of a project charter  Develop a project idea into an effective project charter  Review.
Practical Assessment Project Template
Insert: Title of Improvement Read Out Date:. 2 Objectives for Today’s Session Share results of improvement effort Demonstrate fact-base, analytical approach.
TEPM 6304: Quality Improvement in Project Management Project Quality Management & Course Overview.
Lean Six Sigma Project Briefing Type Briefer Organization Here
1 DMAIC Define Overview Paul Grooms Black Belt in Training.
Project Quality Management.  Define project quality management.  Describe quality planning and its relationship to project scope management.  Discuss.
A3 PROBLEM SOLVING TOOL: Date: Contact: SOLUTIONS What solutions will solve the root causes? (Tools: Brainstorming and Affinity Diagram) What solutions.
Last Updated: MONTH, YEAR Team: M. W. (Team Leader)R. F. T. D.M.G. T. L.D. J. (Sponsor) Green Belt Project Objective: TITLE Green Belt Project Objective:
A Quick Review of the Components THE DMAIC CYCLE.
Practical Assessment Project Template
Analyze Wrap Up and Action Items
Practical Assessment Project Template

LEAN SIX SIGMA PROJECT TEMPLATE
Green Belt Project Storyboard Template See Green Belt Storyboard Checklist for required contents Visit GoLeanSixSigma.com for more Lean Six Sigma Resources.
Six-Sigma : DMAIC Cycle & Application
Lean Six Sigma DMAIC Improvement Story
Project Title BACKGROUND RESULTS AIM METHODS SOLUTIONS CONCLUSIONS
<Project Name> <Name> SOLUTIONS / COUNTERMEASURES
Problem Solving Updated Jun 2016.
Black Belt Project Storyboard Template Can be used in combination with Black Belt Storyboard Submission Guide Visit GoLeanSixSigma.com for more Lean Six.
Practical Assessment Project Template
Lean Six Sigma DMAIC Improvement Story
OPS/571 Operations Management
Presented By: <Names> <Team Name> <Date>
Lean Six Sigma DMAIC Improvement Story
<PROJECT NAME> THEME STAKEHOLDERS BACKGROUND CURRENT CONDITION
© 2013 American College of Cardiology
GHSP Problem Solving Team Champion: Team Members: Team Mentor:
LEAN SIX SIGMA PROJECT TEMPLATE
LEAN SIX SIGMA PROJECT TEMPLATE
Version: Date: Project title Give your project a title that makes it easy to understand what the purpose is with the project Sponsor/Champion: Black Belt:
DMAIC Roadmap DMAIC methodology is central to Six Sigma process improvement projects. Each phase provides a problem solving process where-by specific tools.
Problem Solving.
DMAIC STANDARD WORK TEMPLATE
The 7 Basic Quality Tools ~ The DMAIC Process
DMAIC STANDARD WORK TEMPLATE
1. Define 4. Implement 2. Measure 3. Analyse 5. Control YOUR LOGO
Quality Improvement Mid-Point Progress Update 18 October 2018
1. Define 4. Implement 2. Measure 3. Analyse 5. Control YOUR LOGO
Validation by Process Owner Validation by Project Leader
Practical Assessment Project Template – DMADV
Presentation transcript:

STEP 1: DEFINE THE PROBLEM Problem Statement: What is the problem? A problem is a discrepancy between a standard and the current situation. The ‘standard’ can be a goal, target, policy, plan, level of performance, way of operating or accepted expectation in the organization A useful problem statement indicates: the Standard, the Current State relating to the standard, and the Discrepancy between the current state and the standard A properly stated problem highlights the important ways in which the current situation is different from the desired situation. Background: Information necessary for the reader to understand the complete situation Reason for choosing theme. Why are we doing this project? Efficiency, Quality, Customer Satisfaction, etc. What is the Impact or Urgency around this problem? Scope: What are the boundaries of the project; at what points does it Start and Stop A properly stated problem highlights the important ways in which the current situation is different from the desired situation. A useful problem statement indicates: the standard the current status relating to the standard the discrepancy between the current status and the standard STEP 2: GRASP THE SITUATION Document the Current “As Is” State “Go Look Go See “ See with your own eyes where the process is actually occurring Understand Quantifiable measurements that will be impacted by the improvement project. (Objective is to understand current condition and drive to the “Root Cause(s)” of the identified problem This might include: value stream maps, SIPOC’s, flow charts of the processes, system reports / system queries, statistical analyses, review of existing standard work documentation, performance, quality, or volume metrics Analyse data gathered using basic charts. i.e. Pareto, Run Charts, etc. (What is the analyses showing?) Utilise “Fishbone” Diagram (Cause and Effect). Look for the “7 Wastes” in the causes identified Perform “5 Whys” of the most significant cause or to help in establishing the primary, secondary, etc. bones of the fish. Most commonly used to identify potential root causes for a problem. Title: (This is the TEAM NAME) Step 1Step 2Step 3Step 4 DD/MM/YY Step 5Step 6Step 7 Report Out DD/MM/YY SponsorWho is the Sponsor? LeaderWho is the Leader? FacilitatorName of Facilitator? (If applicable) Team MembersNames of all Team Members (Core) Date: __/__/__ STEP 3: PLAN – SMART TARGETS (cont.) Develop a “Implementation Plan”, describes planned improvement, responsibilities and planned completion dates STEP 3: PLAN – SMART TARGETS Develop a “Plan of Action Statement”, state exactly what changes the team is going to make based on the “Root Cause”, Opportunities, and original Problem Statement. Establish SMART (Specific, Measurable, Attainable, Relevant, and Time-Based) targets for the improvement that tie back to the problem. “Do What”, “To What”, by “How Much”, by “When”. Identify “Activity” (Action to be taken in regards to the root cause), associated Principle, and expected benefit STEP 2: GRASP THE SITUATION (cont.) Commonly utilised tools: After Analysis of all the collected Data, Cause & Effect diagram and / or 5 Whys, develop a specific root cause statement that clearly defines the “Root Cause(s)” of the problem. Summarise the Opportunities identified. Fish bone (Cause & Effect)Value Stream Map (Documents process and information flows with time) Pareto Chart (80/20 rule) Run Chart (Shows changes over time and variation) Flow Chart (Process Sequence) #MeasureBaseline% ChangeTargetBenefits ActivityPrincipleBenefits #Action ItemResp.Date 1 2 X STEP 4: DO – ACTUAL SOLUTIONS Implement the Plan described in Step 3 Document any physical layout or process changes as a result of the plan. (Might include graphs etc. showing the changes) Monitor the results of each implemented action. Stagger implementation to see the effect of each solution if possible STEP 5: CHECK – THE SMART TARGETS Gather data from the changes and compare the results against the targets set in Step 3 Provide Actual vs. Target results; describes whether plan was achieved. Rate each target: 100% = ⃝, 75% = ∆, < 50% = X #MeasureBaselineTargetActualRating STEP 6: ACT – STANDARDISE / SUSTAINMENT If the Desired results are achieved in Step 5 (Improvements are Sufficient)  Document changes, Update SOP’s, Train all on new process, plan for Monitoring, and Expansion. If the Desired results are Not achieved return to Step 2 STEP 7: CONCLUSIONS & LESSONS LEARNED Describe Lessons Learned from event and list out-of-scope or to-do items Document What Went Well? (What do you want in the next project) Document What Didn’t Go Well? (What do you want to make sure you avoid in the next project) Are there any Opportunities identified that were out of the scope of this project, but should be addressed in the future