Why most technology migrations fail (and what we've learned along the way)
summary
Argues migrations scale with accumulated tech debt and gives concrete fixes: inventory and quality standards for 600 engineering teams, a single-source migration map in Backstage, gamified leaderboards to drive 100% adoption, and an automation stack called Autotune composed of test certification, a golden state dashboard, and fleet management tooling that enables automated Log4j-style rollouts when teams meet test and state requirements. Numbers cited: 10 approved languages, 18 frameworks; focus is on measurable outcomes, incentives, and the tooling that actually runs migrations.
AI-written summary · about
chapters (7)
- 0:00Start
- 4:15Infrastructure migrations are the
- 10:54Startup Mode
- 19:41Process Level Ups
- 21:09Have you productified?
- 24:32Let's Autotune It!
- 27:30Takeaways. Migration complexity
related talks
25mMass migrations to the cloud
43mAbout to Start Your Nth DevOps Transformation?
32mDive into technical decisions from successful migrations
14mPatterns of Adoptions and Depreciation
27mLessons from a Year with Backstage: What Worked, What Didn’t...
05mBalancing Technical Debt and Modernisation in DevOps
14mAI-accelerated migrations at scale
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes