Sabotaging a Transformation
summary
Describes concrete failures and fixes: a Norwegian program moves from ~12 to 135 deployments a year by adopting continuous delivery, microservices and mob programming, and a consultancy uses an 8-week pod that ships working microservices within five weeks. Names specific mitigations—Stalin strategy (ignore loud resisters), sandwich strategy (secure exec buy-in and team buy-in), inject competence, change-agent exit timing, seating and title rewrites—and reports these interventions produce durable adoption in the reported cases.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:38Sabotage?
- 3:49Case: NAV Deployments
- 4:44Active saboteurs
- 8:42Active saboteurs mitigation
- 16:27Organizational sabotage
- 28:47Other types of sabotage
- 29:19Pod as a mitigation strategy
- 37:55Other mitigation techniques
- 41:43Outro
related talks
51mSabotaging a Transformation
41mSabotaging an Agile Transformation
01h 05mSabotaging a Transformation:Myriad Ways Organizations Inhibit Transformation
01h 00mBeyond the innovator’s dilemma
55mGetting Unstuck Strategies for Surviving in a Rapidly Changing Post-Agile World
47mOvercoming Obstacles to DevOps
29m5 ways to screw up your DevOps Transformation
41mContinuous delivery in 10 easy mistakes
