Friday Deployments: An Objective Review

Friday deployments offer several benefits, including immediacy, excitement and the rapid discovery of insufficient rollback planning.

They are discouraged unless the alternative is clearly worse and already happening.

Notwerking classifies Friday deployment activity using the Operational Regret Index. This index considers release size, rollback confidence, meeting availability, caffeine reserves and whether anyone has used the phrase “small change” without evidence.

Before deploying on a Friday, teams should confirm:

• The change has been tested somewhere that is not production
• Rollback instructions are written down and not stored inside the system being changed
• At least one responsible person is still reachable
• Monitoring is configured to detect both failure and optimism
• The business understands that “before the weekend” is not a control objective

Where a Friday deployment is unavoidable, Notwerking recommends reducing blast radius, increasing logging and notifying operations before the dashboard expresses an opinion.

If the release succeeds, document the conditions that made it possible. If it fails, document them with greater urgency.