16Improve.ppt
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

16Improve.ppt

on

  • 968 views

 

Statistics

Views

Total Views
968
Views on SlideShare
965
Embed Views
3

Actions

Likes
0
Downloads
28
Comments
0

1 Embed 3

http://www.slideshare.net 3

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Beware!!!! New solutions come with new problems
  • Who are my customers? What is my product or service? What are my customer’s expectations and measures? Does my product or service meet their expectations? What is the process for providing my product or service? What action is required to improve the process? What are my customer’s moments of truth?

16Improve.ppt Presentation Transcript

  • 1. LSSG Black Belt Training Improve: How do we get there?
  • 2. DMAIC Six Sigma - Improve
    • Develop Potential Solutions
      • Identify potential solutions through data analysis, brainstorming, benchmarking
    • Create Future State
      • Develop and implement future state process map and/or innovative solutions for the project
    • Evaluate and Mitigate Risk
      • Analyze the impact of the solution and error proof the process
    Measure Control Analyze Improve Define
  • 3. Agenda for Improve What is the Wizard doing?
    • Optimize Solutions (6 Sigma)
    • Kaizen Events (Lean)
      • - Develop and Simulate Future State
    • Mistake-Proof New Process/Risk Management
    • Develop / Implement Pilot Plan
    • Service Recovery
  • 4. Six Sigma Improve Activities
    • Identify available relationships
    • Determine interactions
    • Reduce list of X’s to a critical few
    • Determine optimum settings for X’s
    • Tools: Multivariate Analysis, DOE, RSM/Optimization, and Simulation
    • Implement improvement
    • Verify benefits
    • Verify measuring system
  • 5. Lean Improve Activities
    • Plan for and conduct a week long Kaizen event
    • Learn by doing, and doing it again
      • Repeat Kaizen’s for key processes
    “ Each new improvement reveals new problems!” Freddy Ball é The Lean Transformation Fight Fires React Improve Processes time
  • 6. Kaizen Events
    • The “Improve” process for Lean , where obvious waste has been identified
    • A team-based, 3-5 day event with no down time
    • Cross-functional teams meet full-time (100% of their time!) to solve a specific problem with pre-specified scope, metrics and goals
    • Results presented to management at the end of the week, with project completion in 30 days
    • Assumption is made that the team will have all the support and resources needed from management
  • 7. Kaizen Events
    • Meet within 100 feet and “ walk” the process to identify opportunities that are not working right and do not require detailed data to justify change
    • Count the number of steps within and between tasks; estimate task and handoff times ; add improvement opportunities to Value Stream Map
    • Share “peak” experiences (“Appreciative Inquiry”)
    • Develop hypothesis and test immediately to see if it works
    • Make quick and not so elegant changes
    • Expect the unexpected!
  • 8. Kaizen Event Team
    • The team should include the following:
      • 6-8 people
      • People who work in the process and will have to live with the changes and at least one supervisor from this area
      • Representatives from upstream and downstream processes
      • Support personnel (IT, HR, etc.)
      • One neutral observer
      • Plus a neutral facilitator
  • 9. Kaizen Event - Day 1
    • Travel - am
    • Lean Classroom Training - pm
      • All participants required to attend half-day Lean training (Intro, waste, VSM, takt time, etc.)
      • Review plan for the week
      • Clarify charter and scope; special needs; available data
      • Clarify roles/form sub-teams
      • Distribute materials/post white paper on walls
  • 10. Kaizen Event - Day 2
    • Current State Mapping - am
      • Sub-teams create current process map using large yellow post-its
      • Label with key data; identify missing data
      • Identify major opportunities for improvement
      • Adjust project scope if required
    • Interview Employees/ Collect Data - pm
      • Sub-teams time a sample of existing sub-processes (with stop-watches)
      • Key personnel interviewed for knowledge of problems, suggestions for improvement, and reasons why sample data collection may not be “normal”
      • May be preceded by a tour of the entire process
  • 11. Kaizen Event - Day 3
    • Complete Current State - am
      • Report-outs of key learnings
      • Addition of collected data
      • Identify key opportunities
      • Experiments to test viability
      • Management progress review
    • Create Future State - pm
      • Perform experiments
      • brainstorm improvement opportunities and potential benefits
      • Create high level future state (“desired” state)
  • 12. Kaizen Event - Day 4
    • Complete Future State Map - am
      • Include full value stream linked to customer
      • Return to plant to test proposed final recommended changes
      • Fine tune improvements
      • Create high-level documentation of new standard procedures
    • Create presentation - pm
  • 13. Kaizen Event - Day 5
    • Practice Presentation - am
    • Noon - Lunch
    • Presentation to management
    • Debrief ; Discuss obstacles to success
    • Next Steps/Responsibilities/Kaizen “Newspaper”
    • Create new standard procedures
    • Write report /Send to stakeholders
    • Celebrate!!!
    Goal_________ Date__________ Implementation Team______________ % Complete Date Completed Due Date Responsibility Action steps to achieve goal #
  • 14. Poka-Yokes: Product and Service Failsafing
    • Keeping a mistake from becoming a defect
      • Prevention
        • Determine potential problems
        • Develop fault-proof designs
        • Create prevention plans
    • A proactive approach
      • Detection
        • Develop signaling system/identification
        • Plan for quick response at operator level
        • Do root cause analysis; use “5 Whys”
        • Eliminate special causes
    • An extension of FMEA
  • 15. Prevention vs. Detection Order New Order Call Center Prevention Detection Sales Department Order Placed Order Placed Data Entry Data Entry Order Processed Order Processed Order Sent Order Sent Order Charged Order Charged Order Paid Order Paid Order Placed Order Placed Data Entry Data Entry Order Processed Order Processed Order Sent Order Sent Order Charged Order Charged Order Paid Order Paid Duplicate Payment New
  • 16. Process for Mistake Proofing Describe Defect and Defect Rate Determine Defect Location Study the Process Flow Observe the Process Identify Errors and Determine Cause Determine Prevention Method Test/Re-test in Extreme Conditions
  • 17. Service Recovery
    • A real-time response to a service failure
    • Involves training front-line workers to immediately respond to customer problems
    • Involves identification of potential “incidents” and determination of optimum response
    Process Improvement can take too long. What do we do in the meantime?
  • 18. Service Recovery - How it Works “ Empowerment can only take place when every associate can personally assure customer satisfaction every time!” G ary K. Johnson Process Identification Incidents Remedies Cost of Incident Measurement of Frequency Customer Identification Mission Statement Cost of Poor Quality