The Problem

The platform migration covered in the previous case study didn't run on one team — it ran across multiple scrum teams, spread over several time zones and departments, all needing to move in step during a period where the business couldn't afford drift between them. A migration like this doesn't fail on the technical plan, it fails on teams losing alignment with each other mid-execution.

My Role

Product Manager, coaching the scrum teams involved through the migration alongside leading it.

The Approach

Kept the teams aligned across time zones and departments throughout — consistent ceremonies, shared visibility on where each team stood against the others, and a deliberate effort to keep departments that don't normally sync closely working from the same picture of progress.

The Outcome

The migration in the companion case study shipped on time with zero downtime, across every team involved — that result depended on the teams staying aligned with each other, not just on the technical plan being right. The coaching itself isn't something that was tracked with a number at the time, which is fine — some of this work shows up in the delivery, not in a separate metric.

What I'd Do Differently

Cater more to people's individual speed of learning, rather than coaching every team at the same pace.