# Streamlined CI/CD processes, saving 4,000 hours by introducing automation in software development pipelines. 2015 – 2022 **Situation.** Getting software out the door relied on manual, inconsistent steps — someone remembering the sequence, doing it slightly differently each time — and it slowed releases down and ate engineering hours that should have gone into building things. **Task.** The aim was to streamline the CI/CD process and get automation into the pipelines, so releases stopped being a manual ritual. **Action.** Automated build, test and deployment pipelines went in, so the path from a change to it running in production was standardised instead of improvised. The repetitive manual steps — the ones that were slow and, worse, done differently depending on who was doing them — came out. Once the pipeline is doing it the same way every time, a whole class of "it worked on my machine" and half‑remembered deploy steps just stops happening. **Result.** The automation gave back roughly 4,000 hours and made releases both faster and more reliable. The team could ship without bracing for it — the confidence came from the process being consistent, not from everyone being careful. --- - Role: DevOps Engineer - Categories: [DevOps](https://advisory.engineer.company/categories/devops/), [Automation & CI/CD](https://advisory.engineer.company/categories/automation/), [Reliability & Backups](https://advisory.engineer.company/categories/reliability/), [Testing & QA](https://advisory.engineer.company/categories/testing/), [Technical Leadership](https://advisory.engineer.company/categories/technical-leadership/) - Services: [DevOps & CI/CD Automation](https://advisory.engineer.company/services/devops-cicd/), [Technical Leadership & Consulting](https://advisory.engineer.company/services/technical-leadership/)