A while back, I came across the idea of “read-only Fridays.”
No production changes. No writes. Just observation.
At first, it sounds like a sensible process rule.
But in production systems, rules like this usually exist for a deeper reason.
Read-only Fridays aren’t really about Fridays.
They’re about trust in your platform.
They’re not about the calendar.
They’re about confidence.
When teams trust their platform:
- deploys are small and reversible
- rollbacks are boring
- observability answers questions quickly
- on-call doesn’t feel like a gamble
Friday isn’t special. It’s just another day.
When they don’t, risk gets pushed into process rules.
Freezes, sign-offs, exceptions, calendar-based safety nets.
Those rules aren’t failures , they’re signals.
They tell you the platform doesn’t yet give teams enough confidence to change safely, so humans compensate instead.
The interesting question isn’t “Should we allow Friday deploys?”
It’s:
*“What would need to be true for this rule to disappear?”
*
Almost always, the answer is platform work:
- clearer pipelines
- faster feedback
- better observability
- easier recovery
Calendars don’t create safety.
Platforms do.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.