Bell · Launch readiness, migration, two-sided product
Fourteen Systems to One Launch Date, 3M+ Accounts Moved, and a Field App Dispatchers Could Act On
14
Systems Aligned
3M+ / 99.9%
Accounts / Uptime
-40%
Dispatcher Response on Exceptions
Overview
Three infrastructure programmes in one year: a network-product launch that fourteen downstream systems had to be ready for, a phased migration of 3M+ accounts to a new platform, and a two-sided web and Android field-service product for technicians on company-provisioned devices.
The Challenge
No one owned readiness across fourteen systems: requirements lists said what should be true, but nobody checked what was true. The underlying platform had to move without disrupting live service, and dispatchers received generic exception flags they could not act on.
The Approach
Built one dependency map with MoSCoW-classified blockers and a RACI across fourteen teams, plus a readiness assessment of current capability. Escalated the billing gap with a worked fix. Phased the migration with rollback criteria per phase and a 2× peak-load requirement. For the field app, worked real jobs with technicians and dispatchers, replacing generic flags with six exception codes and automatic rerouting; owned release cadence, app-quality metrics and go/no-go.
Key Outcomes
- Held the launch date after a readiness assessment surfaced a billing gap six weeks ahead of launch.
- Migrated 3M+ accounts in phases with rollback criteria, 99.9% uptime and no service disruption; validated 2× capacity.
- Cut dispatcher response time on exception cases by 40% with six specific exception codes and automatic rerouting.
The Result
A requirements list tells you what should be true; a readiness assessment tells you what is true. Launches fail in the gap.