Every studio that has been around long enough has a Friday-evening incident story. Ours involves a JSON column, a customer in Lisbon, and a six-hour rollback that ate a long weekend. The story was funny on Monday. It was not funny on Saturday morning.
After that incident we wrote a one-page rule: nothing goes to production after 16:00 on a Thursday, and nothing at all on a Friday. The rule has survived two changes of management, three customers asking us politely to break it, and one VC investor calling it "amateur hour". We kept the rule.
Friday deploys are a quiet way to ruin a weekend. Here is how we got the studio to stop romanticising them.
The rule isn't about being slow. It's about respecting the calendar of the people who run the system after we hand it over. A deploy at 14:00 on a Thursday gives the team three working hours to spot a regression and 48 hours of business calm to fix it. A deploy at 14:00 on a Friday gives the on-call engineer a wedding to leave early.
There are exceptions. A security CVE skips the rule. A production-down incident skips the rule. A founder's anxiety about a launch date does not. We have lost exactly one engagement over this rule. It was worth it.