Sabotaging a Transformation:Myriad Ways Organizations Inhibit Transformation
summary
Organizations sabotage change through predictable blockers: hidden executives, misplaced sign‑offs, title silos, knowledge hoarders, risk‑averse middle managers, UX or DB gating, and blame cultures. Mitigations include a sandwich strategy (secure C‑level buy‑in, run a co‑located team), inject visible competence or replace blockers, use a short fixed‑price pod engagement to train, ship and rotate people, adopt TDD/pairing and full‑stack roles, remove review choke points, measure velocity, kill fear, and scale continuous delivery (one client reaches 1400 deployments a week).
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:30Why changes fail
- 4:15Ultra-fast dev cycles impact
- 6:03Active saboteurs
- 9:37Passive-aggressive resistance
- 11:01Mitigating active saboteurs
- 14:33Executive buy-in sandwich
- 16:16Benevolent tyrant role
- 18:00Operational sabotage
- 20:11How job titles inhibit transformation
- 26:12Proximity and communication
- 31:00Cut review boards
- 34:05Team skills investment
- 36:13Cultural sabotage
- 36:34Pod model
- 45:15Change as experiment
- 46:18Executive engagement
- 50:08Final thoughts & Q&A
related talks
42mSabotaging a Transformation
51mSabotaging a Transformation
41mSabotaging an Agile Transformation
23mIts transformation! But, is it though?
44mDragging out and failing Agile Transformation – reasons
29m5 ways to screw up your DevOps Transformation
13mTen Ways to Doom Your DevSecOps
36mAgile Déjà Vu – Why Do We Keep Failing at Transformations?