Email me: email@example.com
Intro: Welcome to the E6S-Methods podcast with Jacob and Aaron, your weekly dose of tips and tricks to achieve excellent performance in your business and career. Join us as we explore deeper into the practical worlds of Lean, Six Sigma, Project Management and Design Thinking. In this episode number 146, we get back to "Completely Intentional," part 2 of ourMistake Proofing series. If you like this episode, be sure to click the "like" link in the show notes. It's easy. Just tap our logo, click and you're done. Tap-click-done! Here we go. http://bit.ly/E6S-146 Leave a Review! http://bit.ly/E6S-iTunes
***Completely Intentional - Mistake Proofing***
Objection 1: mistake proofing is no different than "engineering"
Counter 1: Agreed, but beware of "over-engineering." These should be solutions that are elegant because they are simple.
Objection 2: Mistake proofing are only band-aids. They don't get to the root cause.
Counter 2: If a mistake-proof cannot be put on a root-cause than a mistake proof on the symptom is better than nothing.
VI Key Rules:
a. Build Quality Into the Process
b. All Errors Can Be Eliminated
c. Seek Out the Root Cause of the Error
d. Start now. Don't wait for perfection
i. Quick hits:
1. when solution is low-risk (lower than risk of not doing so).
2. when there is a medium (50/50) likelihood of success.
VII Different levels of mistake proofing
a. Containment - Identify Defects Before They Move to the Next Operation
b. Detection - Detect Defects Within the Operation
c. Prevention - Makes the Occurrence of Errors Impossible
i. Severity - when the error cannot be contained or prevented, these can reduce the severity of the symptoms
1. e.g. Air bags and seat belts do not reduce the occurrence ofautomobile accidents, but reduce the severity of the trauma from accidents
ii. Perceptions - when error prevention or containment are not viable, how can you engineer a perception to control the situation? Customer Experience Management
1. Classic design problem - High-rise hotel tenants were complaining the elevators are too slow and they wait too long in the lobby.
a. Typically teams try to design a better/faster and more complex elevator system
b. The elegant solution was to install mirrors in the lobby to occupy customers.
VIII Mistake Proof examples - everyday - mistakeproof.com
i. Password hints, strength indicators, "re-enter" confirmation box
ii. Spell check, autocorrect,
iii. Programming syntax error check
iv. "Close without Saving" error message
1. Object-oriented programming keeps us from stepping on each other's data.
2. Unit testing and "smoke testing"  come closer to the notion of poka-yoke, in that they are located close to the source of the potential mistakes and the quick feedback they provide can keep mistakes from moving further along in the process.
Outro: Thanks for listening to episode 146 of the E6S-Methods podcast. Stay tuned for episode 147 with Design Thinker, Lauren Miller, where she shares her experiences applying best practices in design to diabetes care. Don't forget to click "like" or "dislike" for this episode in the show notes. Tap-click-done! If you have a question, comment or advice, leave a note in the comments section or contact us directly. Feel free to email me "Aaron", firstname.lastname@example.org, or on our website, we reply to all messages. If you heard something you like, then Clammr and share it. Don't forget you can find notes and graphics for all shows and more at www.E6S-Methods.com. "Journey Through Success. If you're not climbing up, you're falling down." Leave a Review! http://bit.ly/E6S-iTunes