Sometimes you need to be a cruise director
summary
The claim is concrete: an AWS→GCP migration of multiple petabytes faces a two‑week deadline and stalls from analysis paralysis, not technical gaps. The choice is operational: split into data and pipeline migrations, permit a short double spend on storage (about $20,000 per PB per month) so teams can test safely, get executive sign‑off, and actually move the data. The result is measurable — migration finishes by the deadline and the org got Google credits — so facilitation, not wizardry, wins.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 1:01Critical delivery pressure
- 3:33The illusion of the miracle worker
- 5:21Need for a facilitator
- 7:25Why teams need a cruise director
- 10:34Migration project lessons
related talks
46mEverything you need to know about cloud migration
13mManaging the marathon: Leading teams through migrations
53mPanel Discussion - Performance & Scalability
24mFilling the void
33mWhen scalability becomes more than a buzzword, or how to saddle a unicorn
41mThe monolith must die! - How to convince managers
23mData Team as an Optimisation Problem
36mHow we try to avoid the technology migration trap at Netflix