Poka Yoke
en.wikipedia.org
Poka Yoke
1–10 of 64 posts
Re: Poka Yoke
#2Why is it written in katakana?
Re: Poka Yoke
#3I think one implementation if this is where Japanese rail workers point and call out the thing they are noting, checking, or changing as a form of conscious attention.
“Pointing and Calling” (Shisa Kanko):
https://www.atlasobscura.com/articles/pointing-and-calling-j...
https://www.christopherroosen.com/blog/2020/4/20/how-the-rit...
Re: Poka Yoke
#4Why is it written in katakana?
Probably because it's a slogany sort of invented term.
Re: Poka Yoke
#5I think one implementation if this is where Japanese rail workers point and call out the thing they are noting, checking, or changing as a form of conscious attention. “Pointing and Calling” (Shisa Kanko): https://www.atlasobscura.com/articles/pointing-and-calling-j... https://www.christopherroosen.com/blog/2020/4/20/how-the-rit...
That's more of a learned behavior that helps you consciously check everything; it's almost the opposite of pokayoke. Implementing pokayoke would involve locking out (or making it incredibly hard) for rail workers to continue a process without confirming that everything has been done as intended.
Re: Poka Yoke
#6Is this strictly a physical thing or can it apply in software?
Re: Poka Yoke
#7Is this strictly a physical thing or can it apply in software?
Sure, some Linux distros (or is it MacOS?) ask for confirmation before executing `rm -rf /`, which breaks the typical UX of the command but prevents bad mistakes.
Re: Poka Yoke
#8I think one implementation if this is where Japanese rail workers point and call out the thing they are noting, checking, or changing as a form of conscious attention. “Pointing and Calling” (Shisa Kanko): https://www.atlasobscura.com/articles/pointing-and-calling-j... https://www.christopherroosen.com/blog/2020/4/20/how-the-rit...
Maybe. I think it wouldn't qualify for a few reasons. I'm sure others would be able to justify this as being a form of error proofing.
1. From Toyota Production System An Integrated Approach to Just-In-Time by Yasuhiro Monden, "A mistake-proofing system consists of a detecting instrument, a restricting tool, and a signaling device. The detecting instrument senses abnormalities or deviations in the workpiece or the process, the restricting tool stops the line, and the signaling device sounds a buzzer or lights a lamp to attract the worker's attention." I don't think pointing and calling works for this since there is a human in the loop that would have to detect, for example, the speed is too fast for the segment of track, restrict the speed by slowing the train down, and call attention to another operator to help. The goal is to eliminate the human from this process to ideally free them up to do work that respects their humanity [1].
2. Pointing and calling is only 85% effective as called out on the Wikipedia page for it. The benefit of mistake proofing is 100% built-in quality control according to the Wikipedia page.
3. From practical experience in automotive part manufacturing, our customers did not accept human based interventions or process changes as a form of error proofing. The error proofing needs to be built into the process and it can't be something that an operator can by pass. Pointing and signalling can be bypassed if the employee chooses not to do it. I'm sure there is ways of bypassing some error proofing systems, but that's what the customer wants.
Error proofing is part of a system called autonomation []. One of the goals is to be able to have multi-skilled workers be able to work within a cell. Basically the human operator takes on a loading and unloading focus in the manufacturing process. Several operations would be performed in sequence. The operator would put the raw material in at one side of a machine cell, transfer it to the subsequent operations until the last operation has been completed. The goal is for the piece to be produced with minimal waiting time between each successive operation and for the machines to be able to detect if a defect has been produced.
[1] https://michelbaudin.com/2014/04/12/more-on-toyotas-respect-...
Re: Poka Yoke
#9Is this strictly a physical thing or can it apply in software?
Pretty much all good software design practices exist to prevent mistakes by constraining behavior.
It would be interesting to try and formalize it and make it more specifically analogous to what's in manufacturing.
Re: Poka Yoke
#10Why is it written in katakana?
Katakana sometimes is used to draw attention to words that would be normally written in hiragana or kanji. It can sort of function like italics or bold type that way.
In this case it might be used to signify that it is a specific method rather than just a collection of words. The english equivalent might be capitalizing the letters in Six Sigma to refer to a specific industrial quality process rather than the math term.