Skip the “lean intro” training
I was just attending the TWI / Lean HR Summit run by Lean Frontiers, and heard someone talking about how to train in lean. They said they don’t care in what order you introduce tools, but you can’t skip the introduction. Perhaps its just me playing my normal role of contrarian, but I would disagree with both points.
How many of you have some “lean introduction” training, whether 1 hour or 1 day. It might cover the history of lean, frame up the big picture, and then very quickly cover every tool that they will learn at some point in the future, intending to be broad but accidentally passionately slipping into importance nuances of applying the tools. Then they leave, and …. Nothing. What was the purpose? The purpose was nothing more than to train them on lean. But that’s not actionable, and doesn’t lead to purposeful next steps except more training.
Instead, focus on applicable behaviors, skills, or tools. It doesn’t mean you skip the context, but you put things into context as you go. If a group gives me only 1 hour to train, I will make sure I leave them with something actionable. Maybe its how to perform an After Action Review, or a 5 Whys, or direct observation. It’s probably not TWI or value stream mapping. I will use the teachable skill, that they can practice to extend their learning, and I can still teach the broader context wrapped around that skill.
Secondly, I believe that the sequence does matter. It matters because what you are teaching, and in turn applying, has to be relevant to the individual. I’ve written in the past about organizations that insist upon starting lean with 5S, even it doesn’t solve an organizational or performance problem that they have. So what would make a difference? What would help? What are we passionate about? Start there. There are some capabilities where there really is a logic where A goes before B. But if people don’t appreciate A, then it would be a successful pathway to B.
For example, problem solving is far more effective when you already have a capability of standardization. But its also true that if you try to do problem solving, you learn to appreciate the value of standardization, a realization pattern I’ve observed many times. So which way is really “right”? Neither, and both. The point is, there is no one right answer for the sequence of tools, but there might be a right sequence for you, your team, and your situation.
In summary, the training strategy means just as much as the training execution. Getting people through class isn’t the objective. Getting them to adopt a set of behaviors is the objective. Will your training strategy accomplish this objective?