We did a variation reduction kaizen in our plant and these videos helped add more structure and more pointers on that 5 day event. What you're teaching helped our event successful!!!
That is so great to hear - it brings me joy to know that my content helped you directly. Hope you’ll enjoy many more of my videos and wish you the best with your next Kaizen events!
Happy to hear that you liked it. If there are other Lean / Continuous Improvement / 6 sigma topics you’d like an explainer/refresher on, please let me know.
Great to hear that my content is adding value for you. Thanks for letting me know. And don’t hesitate to ask questions or request topics to discuss in future videos 😉
Hi Tom, you mention there are different fish one categories for different sectors. Where would I find them for strategy pls? Google search not helping. Thankyou.
Can't directly help you with those either, except for that I think there shouldn't be a set for Strategy to begin with - it's not really a results driven process (unless you consider a strategy document a valuable result), so analysing which factors led to deviations in the outcomes isn't so much a thing, I would say.
Hi Tom, great video..can I ask, is it possible to use a fishbone diagram for assessing a problem "why did we get a batch manufacturing record error on the document" and if possible which categories would be most suitable??
Hi Anthony, yes, that’s perfectly valid - I would recommend to use 5 or 6 M (you don’t really need Mother Nature/Milieu for this one). Not just because it’s appropriate, but also because that’s probably what your colleagues will be most used to (a bit of consistency in the tools you use makes it easier for the whole team). Just focus more on the information trail -> maybe the measurement device/value was wrong or the registration software (machine) has some bugs, but most likely you’ll be focusing more on the methods (how do we work, are there double checks, etc.) and man factors.
If you're interested in my 6-step problem solving template, it's available for free through this link: www.tommentink.com/problemsolvingtemplate
We did a variation reduction kaizen in our plant and these videos helped add more structure and more pointers on that 5 day event. What you're teaching helped our event successful!!!
That is so great to hear - it brings me joy to know that my content helped you directly. Hope you’ll enjoy many more of my videos and wish you the best with your next Kaizen events!
This is a great video. I'm a quality engineer and this is very helpful.
Happy to hear that you liked it.
If there are other Lean / Continuous Improvement / 6 sigma topics you’d like an explainer/refresher on, please let me know.
@@TomMentink thank will do.
Thanks for the video, very clear and helpful.
Great to hear that my content is adding value for you. Thanks for letting me know.
And don’t hesitate to ask questions or request topics to discuss in future videos 😉
Hi Tom, you mention there are different fish one categories for different sectors. Where would I find them for strategy pls? Google search not helping. Thankyou.
Can't directly help you with those either, except for that I think there shouldn't be a set for Strategy to begin with - it's not really a results driven process (unless you consider a strategy document a valuable result), so analysing which factors led to deviations in the outcomes isn't so much a thing, I would say.
Thanks. This video is very informative.
Great to hear that my work has helped you, thanks for sharing.
Hi Tom, great video..can I ask, is it possible to use a fishbone diagram for assessing a problem "why did we get a batch manufacturing record error on the document" and if possible which categories would be most suitable??
Hi Anthony, yes, that’s perfectly valid - I would recommend to use 5 or 6 M (you don’t really need Mother Nature/Milieu for this one). Not just because it’s appropriate, but also because that’s probably what your colleagues will be most used to (a bit of consistency in the tools you use makes it easier for the whole team).
Just focus more on the information trail -> maybe the measurement device/value was wrong or the registration software (machine) has some bugs, but most likely you’ll be focusing more on the methods (how do we work, are there double checks, etc.) and man factors.
Thanks, i like ur explanation.
Great to see that you liked it!