Halving the time from product to production
Replacing manual releases on legacy client set-ups with automated CI/CD on AWS and GitHub Actions across 20+ product modules.
50%faster product-to-production
20+core modules on the new pipeline
Context
Many client products ran on legacy infrastructure with hand-run deployments. Releases were slow, nervous and hard to roll back, so teams batched changes and shipped less often.
What I did
- Designed and automated CI/CD release pipelines on AWS with GitHub Actions.
- Moved 20+ core product modules onto the pipeline, one at a time, without breaking live clients.
- Worked with engineering leads on API integration design up front, so performance risks were caught before sprint commitments instead of after release.
- Earned the AWS Certified Solutions Architect – Associate along the way, which made those conversations with engineering much faster.
Outcome
Time from product to production roughly halved, and releases became routine rather than events.
What I learnt
You don’t need to be an engineer to ship in the cloud, but you do need enough fluency to know what you’re asking for. That fluency is what lets a product person cut a backlog instead of adding to it.
Want the longer version? I’m happy to walk you through it.
Email me