The CFO Question That Exposed £2.3M in Hidden Risk
summary
A single boardroom question How long to rebuild production if we lost it all tomorrow? exposes £2.3M of risk: 150 microservices deployed seven different ways, 23 configuration repos, backups driven by faith. The fix is a GitOps rebuild using Terraform modules, Atlantis for PR-driven applies, Flux for Kubernetes sync and image automation, SOPS+KMS for encrypted secrets, Pluto for deprecation checks, and EKS on AWS. Outcome: disaster deployments stop and they deliver 4 hours with full audit trail and restored operational confidence.
AI-written summary · about
chapters (10)
- 0:00Welcome and introduction
- 1:08The £2.3M wake-up call
- 6:47Two perspectives on risk
- 7:49Five stages of transformation
- 12:24The awakening moment
- 13:27Strategic alignment over tools
- 14:33Technical implementation details
- 27:18Human transformation success
- 28:40Business and career metrics
- 30:02Final call to action
related talks
43mHow GitOps Enabled Us to Answer an Unanswerable Question
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery
21mBuilding A DevOps Culture in a Remote World
22mOops, I deployed too hard
46mEmbracing Collaborative Chaos
21mPlatform Security
44mDevSecOps: Balancing Agility, Security & Stability in a Continuous Software Business