The thing about a twice-weekly production release is that it has to be boring. If it is exciting, something has gone wrong. The team I want to tell you about figured out how to make it boring on purpose.
This is what a Tuesday morning looks like inside the BJ's Restaurants engineering organization, eighteen months into our Aegis engagement together.
The room before deploy.
The pre-release standup is short by design. Eight minutes, never more. Engineers, the on-call lead, one product partner. The pattern is the same every time: confirm the risk class for today's slice, confirm rollback is ready, confirm telemetry is green. Then we ship.
What you don't see in the photo.
What's missing from the room is more interesting than what's in it. There is no war room. No bridge call. No senior leader watching over the engineer's shoulder. The deploy happens. The graphs hold. People go back to whatever they were working on before.
- No war room. The release is small enough that one person can hold it in their head.
- No leadership escalation path live during deploy. If a leader needed to be on the call, the change shouldn't have shipped today.
- No post-mortem. Because there is rarely anything to post-mortem.
The best production release is the one your customers cannot tell happened.
What this took to build.
Getting to this state took eighteen months of process work — and a willingness to throw out the two-week sprint container that everyone in the industry had quietly accepted. The technology is downstream of the discipline.
If you want the full write-up of how the cadence shift happened, that's a different post. This one is just the photos.
— Kelvin Tran. Walnut Creek, CA. May 2026.
Comments