# Kaizen in Action - Kiro Harada [EN]

* Self Introduction: Agile Coach, Domain Modeler, SCM Consultant. He started his career as a chemical engineer in cosmectics R&D. Found that QA needs better management. He's been practicing SCRUM since 2004. He is working to make your business and developer easier and safer.

* Kaizen.
* Is it really possible to teach Kaizen? A better question is: Is it possible to teach how to teach to ride a bicycle?
* Teaching
* Why Kaizen is improtant?
* continuous improvements
* always
* timelessly
* endlessly
* Dangerous false assumption
* Our performance is not good enough because we have not done enough. We must do more.
* Overtraining is the #1 cause of athlete failure.
* We use external measurements to access our performance.
* Toyoda Type G Automatic Loom -- still operation and kept as an exhibit piece.
* auto stop if something is broken.
* it only produces good product
* an operator can take a break anytime
* operatore can handle 60 looms concurrrently.
* Your Kaizen isn't continuous
* because you/team are exhausted.
* you/team are not improving.
* the product being made isn't "good".
* It's much easier to manage what you can see.
* Muri - Mura - Muda
* muri - overload / overburden
* mura - unevenness
* muda - waste
* you need to elminate muri first with kaizen to eliminate muda.
* How to start?
* create slack
* without slack you cannnot do anything without harming your performance
* remember overtraining athletes
* take your time to understand limits
* prioritize "slack" time
* try eating ice cream with coworkers to slack.

* Team Dialogue
* if each member of your team has slack, use your slack to meet together and have a dialogue regularly
* take your time time to talk
* Agreeing on Issues
* come up with issues you want to fix together


* Issues / problems examples?
* We need to improve the quality of our software
* We need better Scrum
* We have to use CI/CD
* Devops need to be implemented

* Lack of solution is not a problem



* Learn and know your teams value and strengths so you can play to your pros
* Small experiements by focusing on easy and fast experiements will allow you to find correct answer and path overall.
* Set-based Design
* Eliminate what is not needed. Eliminate what testing isn't needed.
* Combining testing for less.
* Rearrange testing method to make it easier.
* Simplify testing.

* Finding Defects Early
* Build in ways to allow early detection of breakage.
*
* Good teams have an approach to their team standards
* Good standards means good documentation which allows teams to share with other coworkers and with other teams -- in f2f meetings.


Kaizen is to make your work easier and safer. This is why it is important to do this over and over.


Toyota has one of the best factories in the world, this book shows how they achieved that.



Q&A: Please see Mandarin version of notes since author was moderating. Thank you!