Three Steps to Change: Lessons from Battling Bureaucracy
summary
Fifteen years of federal work reduces to three actions: create desire, target specific workflow waste, and let teams own fixes. Example program goes from 32 apps, one deploy per year → 290+ deployments as teams adopt agile; a bottleneck that required 48 hours → 12 minutes 30 seconds after targeted automation; another project ships 160 more features after automation. Uses value‑stream mapping, baselines, dashboards and small J‑curve experiments to prove and scale change.
AI-written summary · about
chapters (13)
- 0:00Intro
- 2:24The Challenge: Fix this program
- 5:02Paula's Three-Step Formula
- 9:45Deployments over time
- 17:28Visualize the work
- 21:51Numbers work too
- 23:25Truth... it depends on perspective
- 25:14How to Make Change Happen
- 27:04Allow the J-Curve to Happen
- 30:57Change Improvement Board
- 32:01Improvements to waste can be dramatic!
- 33:06Catalyst Change Cycle
- 33:415 Take Aways
related talks
52mSmall Steps Are the Fastest Way Forward: Life Beyond Agile & Scrum
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
49m5 Steps to a DevOps Transformation
30mHow a Business Exec Led Agile, Lead, CI/CD
30mHow We Led Three Banks Through DevOps Transformations
33m7 habits of a high performing team
34mYou only have to change one thing to do the DevOps
44mScaling Agile With a Super-Effective Global Delivery Machine