Managing the marathon: Leading teams through migrations
summary
A team leads a multi-year migration that retires a legacy system for a new acquired stack, reconciling 70 million data points and costing decades of engineering time; the concrete approach uses three personas (patrons, consumers, builders), splits work into capability milestones and integration milestones, and tracks progress with a gamified metric called ticker watch that is celebrated at thresholds; storytelling, delegated responsibilities, and those measurable milestones and metrics keep focus, cut fatigue, and ultimately deliver the migration.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:05Migrations are complex
- 3:34Storytelling in migrations
- 5:42Stakeholder personas
- 7:52Balancing size, time, impact
- 9:15Milestones and metrics
- 11:03Migration narrative
- 12:47Conclusion
related talks
24mFilling the void
36mHow we try to avoid the technology migration trap at Netflix
45mHitchhiker’s Guide for Software Architects: Legacy Migration
11mTips on scaling your leadership outside of your comfort zone
12mSometimes you need to be a cruise director
25mTransforming legacy software
38mTo Migrate or Not? Managing Technical Hype Cycles with KMP & AI
24mScaling leadership