Building a Culture of Continuous Improvement

The slides are clear, covers the ideas, and stand on their own. Thanks for sharing. The acronyms, I bet, add to confusion around training. As an outsider it just different for no particular reason. Instead of swig or whatever it was, call it an epic or big a problem, or strategic direction or wahtever. The secret weapon is having everyone understand the current direction, then get sub-tasks down in size for faster iteration feed. This drives a beautiful feedback cycle. Successes are built upon, and failures are cheap. It look like you guys are getting there. The big problem might melt away as it's covered in n smaller problems that gets tacked quickly. Quarter cycles goes away. Documentation is important for certain things, I would argue that it's the process (retrospective) rather than documents that is of value. Does anyone actually read those old lessons learned, say, a week or two after they were published? Anyone in the control cycle, "leadership approvals" will slow you down. Can you empower people to do the right stuff on their own? I manged it via prioritization of a queue. Only the top of the queue matters, and people what how stakeholders prioritize items. They will self-prioritize right very quickly, and only leadership input required is when things change.