Cloud Migration and Talent Retention
You are the CTO of a 1,500-person retail company. You have committed to migrating 80% of workloads to AWS within 18 months to reduce data center costs by $3M annually. Your infrastructure team of 30 has deep VMware expertise but limited cloud skills. Attrition has risen to 15% as competitors offer cloud-native roles. The CFO has approved $2M for training but expects the migration to be cost-neutral in year one. A systems integrator offers to lead the migration for $5M, but you worry about knowledge transfer. The CEO wants to see quick wins to build confidence. A recent AWS bill for a pilot was 20% over budget due to untagged resources and idle instances.
1. How should the CTO balance using a systems integrator versus building internal cloud capabilities?
Read the worked answer
Adopt a hybrid model: use the systems integrator for the initial migration factory (lift-and-shift of low-risk workloads) to accelerate quick wins and meet the 18-month timeline, but contractually require knowledge transfer, paired staffing, and documentation. Simultaneously, invest in upskilling the internal team: create a cloud center of excellence (CCoE) with a mix of new hires and existing staff, fund certifications, and establish a career path for cloud roles. Allocate the $2M training budget to hands-on labs, AWS certifications, and a mentorship program with the integrator. Retain key staff with retention bonuses and clear growth opportunities. This addresses attrition and builds long-term capability while delivering early wins.
2. What immediate steps should be taken to control cloud costs and achieve the CFO’s cost-neutral expectation?
Read the worked answer
Implement cloud financial management (FinOps) immediately: enforce tagging policies, use AWS Cost Explorer and budgets, set up alerts for anomalies, and rightsize instances. Identify and terminate idle resources. Use reserved instances or savings plans for predictable workloads. Establish a monthly cost review with finance and engineering. For the pilot overrun, conduct a root-cause analysis and apply lessons. To achieve cost-neutrality in year one, prioritize migrating workloads with the highest data center cost savings and quick wins (e.g., dev/test environments). Communicate that true cost optimization comes after migration when legacy contracts expire; set expectations with the CFO using a phased savings model.