Deploy as Everyday Activity

Deploy = boring. The norm.

Deploys should be everyday

Daily deploys reduce per-deploy risk. Smaller changes, fresher context, faster rollback.

Weekly or monthly deploys batch risk. The release becomes a feared event.

DORA elite performers deploy multiple times per day. The shape of the release determines the risk, not the cadence.

What enables daily deploys

Trunk-based development. Long-lived feature branches force big-bang merges.

Feature flags decouple deploy from release. Code lands in production behind a flag, enabled later.

Automated tests with high coverage. Without them, every deploy is a gamble.

What blocks daily deploys

Slow CI: above 30 minutes makes daily painful.

Manual approvals: each layer of approval halves the deploy rate.

Brittle environments: if staging is broken half the time, deploys stall.

Rollback is as important as deploy

Aim for under 5 minutes from rollback decision to live.

Automated rollback on SLO regression beats manual rollback at 2am.

Practice rollback. The first real rollback is not when you want to discover the procedure.

How to make daily deploys real

Measure current deploy frequency. Set a target: this quarter, double it.

Pick the biggest blocker. Usually CI speed or approval theatre.

Treat deploy frequency as a leading indicator. Rising frequency means the pipeline is healthy.