0:03 hi welcome back in this section we will
0:06 discuss mystique goofy do you want
0:08 errors and mistakes recurring in your
0:11 processes I bet the answer is No
0:14 well mistake proofing is here to answer
0:17 that particular concern mistake proofing
0:20 or it's Japanese equivalent Pocoyo key
0:23 is the use of any device or method that
0:25 either makes it impossible for an error
0:28 to occur or makes the error immediately
0:31 obvious once it has occurred mistake
0:34 proofing aims to reduce the occurrences
0:37 of mistakes and errors that users in the
0:40 process commit mistake proofing can be
0:43 categorized into three subcategories the
0:47 highest level will be prevention second
0:50 that is detection and the least level is
0:52 containment once an error occurred in
0:54 the process what we want to do is to
0:57 contain it for it not to affect other
0:59 processes and for its impact to be
1:03 contained or minimized the higher form
1:05 will be detection now before the actual
1:08 defect or actual error or mistake will
1:10 be committed there is a way for you to
1:13 detect the likelihood of it happening or
1:15 detect whether it has been created
1:18 already or not giving you an idea of
1:20 stopping the process for you to minimize
1:23 the effect of that particular error or
1:25 defect now the ultimate goal as
1:27 mentioned is to prevent to eliminate the
1:30 possibility of the error or mistake to
1:33 be committed within the process so these
1:34 are the levels that we can play into
1:37 when we talk about mistake proofing what
1:39 is the best time to use mistake proofing
1:42 here are some best scenarios when we can
1:45 use mistake proofing when a process step
1:47 has been identified where human error
1:49 can cause mistakes or defects top or
1:52 especially in processes that rely on
1:55 workers attention skill or experience if
1:58 the process is fundamentally based on
2:01 the judgment of a human component then
2:03 there's a higher possibility of a
2:06 mistake according errors are most likely
2:08 to be committed by the human component
2:11 because of the poor process design that
2:14 has been embedded into our processes
2:17 next in a service process where the
2:19 customer can make an error which affects
2:21 the output let's say when you're filling
2:24 up a form in a bank or when you are
2:27 transacting in a government office so
2:29 their process is susceptible to errors
2:31 because there's a component of you
2:34 interacting with their process and if
2:36 the process design again is poor then
2:40 the likelihood of mistakes are high at
2:42 the handoff step in a process when
2:44 output or first service processes the
2:46 customer is transferred to another
2:49 worker when you say handoff this is the
2:52 activity where and you are endorsing or
2:54 you are giving your output to the next
2:57 process so mistakes is most likely to
3:00 happen on those particular gaps when a
3:02 minor error early in the process causes
3:05 major problems later in the process so
3:07 this is a classic example of a
3:09 particular error committed within a
3:11 process but does that mean deducted
3:14 early therefore creating more negative
3:18 impact to the whole process or series of
3:19 process steps inside your organization
3:22 and last when the consequences of an
3:26 error are expensive or dangerous when an
3:28 error let's say for example a medical
3:30 error or an industrial error or mistake
3:33 has the likelihood of being created then
3:36 it's the best scenario or chance for you
3:38 to implement a mistake proofing activity
3:40 it could mean a severe impact to the
3:43 employee's health and safety and could
3:45 mean a loss of life these are scenarios
3:47 for in mistake proofing is highly
3:50 recommended to be applied now in your
3:52 journey as a Lean Six Sigma practitioner
3:54 you have to understand that our
3:57 objective is that we want to prevent the
3:59 mistakes recurring so that we can reap
4:01 the gains of the improvements that we
4:04 have embedded into our processes coming
4:07 from the validated root causes now how
4:09 to use mistake proofing first you have
4:11 to rate a process map and review each
4:14 step for possible occurrence of errors
4:16 this is actually related to your natural
4:18 face wherein you have your process map
4:22 to identify potential causal step and we
4:24 are now identifying the possible
4:25 occurrence of error come
4:28 from those process steps number two for
4:30 each potential error identified the root
4:33 cause or source now this is in relation
4:35 to your analyze phase wherein we are
4:37 validating the potential root causes
4:41 using data for it to be valid if this is
4:44 valid then we will now put ways on how
4:46 to prevent this errors as given on
4:49 number three if it's not possible to
4:51 prevent it then think of ways on how to
4:53 detect the errors as early as possible
4:57 and number five implements the mistake
4:59 proofing action items as given in this
5:01 particular phase which is improve phase
5:04 now this is the general framework of how
5:07 we can identify mistakes before it can
5:10 happen and how can we implement those
5:12 mistake proofing action items moving
5:15 forward here are some examples of
5:18 mistake proofing activities or
5:20 strategies now look at your household
5:22 these are common examples that you can
5:25 see at their households or offices who
5:26 AOPA helps prevent mistakes while
5:29 manufacturing equipment for example this
5:32 is more of a design change when you see
5:35 your electric outlets or the cables that
5:38 are being used for projectors printers
5:42 and laptops there are specific cables
5:45 that are designed to fit on specific
5:49 slots of those equipments or appliances
5:51 this prevents putting the wrong cable
5:54 the wrong slab and we have examples that
5:57 we can see on the offices visual
5:59 management is also an example of music
6:02 proofing strategy using labels interval
6:03 files and your documents in the offices
6:07 and even on your personal household we
6:10 also have visual management applied to
6:13 input connections of TV or audio
6:15 appliances this color coding sockets
6:18 allows visual aid for workers and for US
6:21 consumers and one example mistake
6:23 proofing that has been done that I think
6:27 most of us can relate is that before the
6:29 way it runs up into an ATM is that you
6:32 have to transfer your card and then you
6:34 will do your transaction the money will
6:36 come out from the machine and then you
6:39 will have to pull out your card
6:42 the receipt problem is that there are
6:45 cases wherein the card is being left
6:47 into the machine now what the ATM
6:50 manufacturer did is to do sequence to
6:52 prevent the particular mistake if you
6:56 can notice the sequence is now card the
6:59 new Beltran sack then the card will come
7:02 out the money will come out and there is
7:04 it will come out last part of the transaction
7:05 transaction
7:08 now this eliminates the problem of cards
7:10 that are being left out in the ATMs
7:12 another set of examples are smoke
7:16 detectors in hotels offices the smoke
7:18 detector does not prevent the fire to
7:21 happen but it mitigates the risk of the
7:23 fire to have severe damage on the
7:26 particular facility by detecting it and
7:28 by putting mitigation actions like
7:31 triggering the water sprinklers the same
7:34 way a circuit breaker operates whenever
7:36 there is a short circuit then the
7:38 circuit breaker will cut the electric
7:40 operations at your household preventing
7:42 the possible severe damage of the
7:45 particular electric trip moving forward
7:48 what we want you to practice is that you
7:51 have to look for possible errors that
7:54 could happen in your process validate it
7:56 and put necessary mistake proofing
7:59 actions for the error not vertical
8:02 either it be a detection or prevention strategy
Chrome Extension