The Business HACK I learned from the JAPANESE 🇯🇵 

I love your level of honesty so much, Ryan. It really also highlights the reiterative process of implementing LEAN. it's not happening over a year or two

“Continuous improvement of the standard” such clear focus, thanks again Ryan! 😎

The biggest challenge I’ve run into is taking a design that was not optimized for manufacturing and getting engineering to play nice and change the design. The complexity of customer and governmental approvals for design changes is maddening. Standard work and continuous improvement is great, but make sure you are working with the optimal design.

I came to standard work through problem solving. When something was “wrong” asking the question “what should it be” usually. Gets an interesting response. And was almost never documented. Especially painful when working with 4 shifts and no real overlap….

Great video, Ryan. I have a request/suggestion: It would be incredibly valuable (especially for someone like me just beginning my lean journey) if you made videos going into intricate detail on how you actually/literally execute these concepts. You do this a bit in other videos but you could go into further detail showing real SOP’s being written, what software you use, the chain of communication between employees from new idea, how to update an SOP, publishing it for all employees, how employees are notified of the change. Even if you did one video of one concept in intricate detail I think it would open people’s minds more on how lean works, how you think, how we need to think to get to your level. It might be a very long video but I don’t doubt that all of your subscribers would watch every second of it! Thanks!

Fantastic discussion as always 👍👍. "Documenting highlights the waste" is gold.

SoP's should be essential for every business. Great podcast

Brilliant. How do you approve a process change? How do you handle suggested improvements that you know are a bad idea.

Great questions of Ryan

Hi Ryan. Love your channel. I watch all your videos. Quick question (I've been trying to figure this out for years): When documenting a new standard work process, do you document the new process immediately the first time you do it? Or do you play around with the process a few times first, tweak it, improve it as much as you possibly can for the moment... then after a few days (once you're satisfied) document it as standard work?

The whole QR Code thing, is the cellphone inside a company intranet? I mean, what if I wanted to use QR Code but do not want employees sharing the videos with outsiders?

Would love info on leader standard work; our leaders keep trying to use SOPs as a “rules for thee but not for me” manipulation tool, will hold others to them and change them willy nilly to pass the buck but will not use them personally or put enough thought and effort in to set others up to succeed with them. We tried to get them in the habit and seeing the benefit by creating a written standard problem solving process that lays out the PDCA cycle, but they find any excuse to skip it and jump straight back to following their gut and perpetuating their preconceived notions instead of observing and analyzing processes and thinking solutions through. It’s killing our whole lean effort, improvement projects keep dead ending, leaders undo progress inadvertently by rolling out half-solutions and refusing to review and follow updated processes, everyone is demoralized by their behavior as well.

What is the balance for instructions (SOP) between to simple and over complicating the process. (what can you assume or not)