Thanks, Bill. Your perspective is giving me lots to think. I don't know if I interpret point #2 correctly, but I've started imagining how to be more intentional in embedding learning in meetings, by focusing on a concept, example and expectation, that can be immediately applied. Something to try this week!
My teams got used to me asking questions about where they were finding problem spots (slowdowns/cycle time, quality/error hits along workflow, stuff getting the way (aka old/bad procedures/practices), etc.) and we would take one of those and discuss it. I felt if I could provoke the conversation and then listen, the team would bring back an innovative and actionable solution. The key, as you stated so clearly, is to try something! :)
Thanks, Bill. Your perspective is giving me lots to think. I don't know if I interpret point #2 correctly, but I've started imagining how to be more intentional in embedding learning in meetings, by focusing on a concept, example and expectation, that can be immediately applied. Something to try this week!
My teams got used to me asking questions about where they were finding problem spots (slowdowns/cycle time, quality/error hits along workflow, stuff getting the way (aka old/bad procedures/practices), etc.) and we would take one of those and discuss it. I felt if I could provoke the conversation and then listen, the team would bring back an innovative and actionable solution. The key, as you stated so clearly, is to try something! :)