Communications
Releases squeezed into a night window, with a rollback nobody has practiced
We turn hand-run release steps into one pipeline your team starts. The approvals your policy requires run inside it, every stage checks its own result, and rollback is tested before go-live.
- Your tools stay
Release 3.8
Started by an engineer on the team
Change ticketupdated by the pipeline
Release 3.8 is live in all regions and every check passed. Change record attached: approval, author, commit and deploy.
What slows releases
Why a release still takes a night, a ticket and some luck
The night window sets the pace
Changes to production wait for a maintenance window, often at night. The steps run by hand, one after another, and if one overruns, the release slips to the next window.
An approval before every change
Every production change needs a change approval first. The request lives in a ticket, apart from the release, so someone pieces together what was deployed, by whom and from which commit after the fact.
A rollback that exists only on paper
The rollback plan is a section in the change request. Nobody has run it end to end, so its first real test is a failed release in the middle of the night.
What changes
Your change process stays. The hand-run steps go.
A Self-Service Release Build automates the release flows that cost you the most, end to end, in the tools you already run. Plan on 4 to 8 weeks.
-
TodaySteps run by hand inside the window, and someone checks each result by eye.
After a BuildOne pipeline per release flow, started by the team. Every stage checks its own result.
-
TodayThe approval sits in a ticket, apart from the release, and the record is pieced together afterward.
After a BuildThe approvals your policy requires run inside the pipeline, and every production release leaves a change record your change board can check.
-
TodayThe rollback plan is written down, but nobody has run it.
After a BuildRollback is tested before go-live, and any engineer on the team can roll back without waiting on another team.
-
TodayThe NOC, support and the change manager ask the release engineer how far it got.
After a Build“Where is it now?” gets answered by status messages in chat or the ticket.
Results
The same work at Nike and ASML
Results from release work at Nike (retail) and ASML (semiconductors). In both, steps that ran by hand became self-service pipelines.
Engineering time back
600+
engineering hours a year given back at Nike, and 300+ at ASML
Read the casesNike · store-server upgrade, per server
Upgrades that ran by hand across five teams became one self-service pipeline
- Servers at the same time: 2 → 8
- Stores: 900+
ASML · release readiness
One place to judge whether a release is ready
Production machine test results in one Python and SQL reporting view, for faster release-readiness decisions.
Nike · deploys to staging
No hand-off to start a test build
A test build to staging devices went from 5 to 10 minutes by a release engineer to about 1.5 minutes, started by the developer.
Reading
Reading for your next change window
- ArticleThe Reliability Tax in Telecom Delivery: Shipping Faster Without Dropping the CallFour pressures on communications platforms, from tightly coupled changes to toil, and the delivery habits that let them ship faster without losing reliability.Read the article
- ArticleProgressive Delivery in 2026: Canary vs Blue-Green vs Feature FlagsHow canary releases, blue-green deployments and feature flags differ, and how each one gives you a fast way back from a bad release.Read the article
- ArticleObservability vs Monitoring: What Senior Engineers Need to Know in 2026The difference between alerts for failures you predicted and telemetry that answers questions nobody anticipated, and how to keep the bill in check.Read the article
Where to start
Start with your last release
The free Release Check shows where your last release spent its time and what that costs a year, in under 5 minutes and without a call.
Contact
Talk to the engineer
Book 30 minutes and bring your last release, or send a message. You talk with Mateusz directly.
