Workplace flexibility often survives because of an unofficial exchange. Employees get some freedom over where they work, and in return, they occasionally answer an urgent message or solve a problem outside normal hours. Remove one side of that arrangement, and the other side may disappear surprisingly quickly.
Employees at one software company learned this after a new CTO arrived and replaced their longtime hybrid culture with strict office hours. His position was simple: if someone was not physically at their desk between 9 and 5, whatever they were doing did not count as work.
When employees asked whether that included fixing emergencies from home after hours, he confirmed that it did. So the team stopped checking Slack, email, and production alerts the moment they left their desks.
For a while, nothing catastrophic happened. Then a Friday deployment went wrong just minutes before everyone went home. Keep reading to see why the CTO’s own words soon returned to the conversation.
A rigid new CTO bans after-hours work, so employees stop helping the moment they leave their desks
Some workplaces function because employees give more than their contracts technically require. They answer one late message, check an alert during dinner, or solve a weekend problem because they feel trusted and invested in the team’s success. That extra effort can become so routine that management stops recognizing it as generosity.
This software team discovered exactly what happened when a new CTO dismissed that invisible contribution as “not work”: employees stopped providing it.
Emotionally, this was less about revenge than reciprocity. Before the policy change, workers had flexibility during ordinary hours and voluntarily returned that flexibility when emergencies appeared. The arrangement was imperfect because after-hours labor was unpaid, but there was an informal exchange of autonomy and goodwill.
The CTO removed one half of that exchange while apparently assuming the other half would remain. Instead, employees adjusted their behavior to match his explicit definition of work.
A fresh perspective is that the disastrous weekend was not primarily evidence that remote work was necessary. It exposed an organizational dependency that should never have remained informal. A business-critical software platform was effectively relying on employees voluntarily monitoring production outside working hours.
The CTO’s rigid policy revealed that weakness dramatically, but the previous system had also concealed it. Once the company created a compensated on-call rotation, it finally converted invisible goodwill into recognized responsibility.
Organizational psychologist Denise Rousseau, Ph.D., a leading researcher on the “psychological contract,” describes these contracts as employees’ beliefs about reciprocal obligations between themselves and their employer. Unlike written employment agreements, they include implicit expectations involving trust, support, flexibility, loyalty, and additional effort.
When workers perceive that an employer has violated those expectations, their commitment and willingness to contribute beyond formal requirements can decline.
That framework helps explain why everyone suddenly became unavailable at 5:00. The employees had not necessarily stopped caring about customers. Management had redefined the relationship.
When flexibility disappeared and off-site effort was explicitly declared worthless, continuing to donate evenings and weekends would have preserved an arrangement that recognized neither their time nor their contribution.
Still, the employees were not the only lesson here. Deploying at 4:52 on Friday without dependable after-hours coverage was an operational failure waiting to happen. Critical systems should not depend on someone’s willingness to glance at Slack during dinner.
The eventual solution—formal on-call duties, compensation, and restored hybrid work—was healthier than either extreme. Goodwill can strengthen a workplace, but it makes terrible infrastructure. If a company cannot function without employees regularly donating their personal time, that invisible labor was always real work. Management simply had not priced it yet.
Take a look at the comments from fellow users:
These Redditors thought deploying at 4:52 p.m. on a Friday was the biggest mistake in the story
These commenters questioned why a live service lacked a properly organized and compensated on-call rotation
These Redditors appreciated the malicious compliance of refusing to perform unpaid work outside normal hours.
These users focused on the broader fallout, from lost workplace goodwill to frustration with the discussion itself
The 61-hour outage did more than embarrass a new executive. It put a price tag on labor the company had previously received through goodwill. Research from both Microsoft and Gallup shows how complicated the boundary between office hours, remote flexibility, trust, and after-hours communication has become.
In the end, the company landed somewhere more sustainable: defined on-call duties, actual compensation, and eventually renewed hybrid flexibility.
But who deserves the biggest share of blame—the CTO who eliminated the safety net, or whoever thought 4:52 Friday was a marvelous time to deploy?
