When teaching a Lean Change Management class, we usually let the attendees choose which of the proposed Lean Change Canvases they want to work on as a group, or several groups when the class is a bit bigger. I noticed the Story Telling Canvas was often left out, and when I asked the attendees why, they often mentioned things like: "It doesn't seem to be as impactful as the others.", or "It's unclear to me how to work with this.".

A few weeks ago I had the amazing opportunity to facilitate several in-company legacy coderetreats for one of our clients together with the software craftsperson exatraordinair Koen Metsu. I still believe this is an extremely powerful training format to help people to get into practising babystep refactoring and test automation. 

And then comes that time of the year again, where we look back at a slightly more turbulent year than expected, but with a lot of plans and expectations for the year to come! The team is now starting to take some time to rest and renew in the company of their families, but not before wishing all of our friends, colleagues, Co-Friends, Co-Workers and Co-Companies all the best for this Holiday Season.

After have participated in my 3rd workshop with Christopher Avery on Personal responsibility I started realising how powerful this could be if we could apply this way of looking at, and dealing with, technical problems more. In case you are not familiar with the process can you read about it or watch a short introduction video on it to get the basic gist of it.

Denial