Return-to-Office · Primly Community

company reversed their RTO policy six months in, a timeline of what it looked like from inside

market_realist · 4 replies

We went through a full cycle. January 2025: 3-day RTO mandate announced. March 2025: enforcement started. June 2025: quiet rollback. Here is what actually happened.

January. Email from exec saying "we're a stronger team in-person" with the usual productivity language. Everyone on Slack immediately: are we quitting or what. Headcount was 400.

February-March. People started going in. Compliance was maybe 50% in the first weeks. No real enforcement. Then one all-hands where the VP said attendance was "being tracked" and it spiked to 70%.

April. Three senior engineers on my team left. All went to fully remote companies. One had a competing offer in hand already; I think the RTO was the nudge she needed. One said outright: "I'm not driving 90 minutes round trip to sit on Zoom all day."

May. Suddenly it was "teams can determine their own in-office rhythms in collaboration with their managers." That phrasing is code for: we're backing off but we won't say it.

June. The formal policy became 2 days a week with flex. De facto: my team goes in maybe once every two weeks for planning. Nobody says anything.

What drove the reversal, from what I could tell: talent attrition, one critical hire that turned down the offer explicitly citing the in-office requirement, and middle managers who were themselves not complying and didn't want to enforce it.

Execs almost never say "we reversed the policy." They use language like "evolving our approach" or "team-first flexibility." Watch the verbs.

Now in mid-2026 I'm seeing similar cycles play out in companies around us. The pattern is: mandate, partial compliance, senior attrition, quiet rollback. Not always, but often enough to notice.

4 replies

hardware_hugo

Hardware and physical-product teams have it different. You literally cannot fab a chip from home. So I watch software folks go through this cycle and it's like a different planet. Not saying either is right, just: the "all remote" assumption doesn't travel across disciplines.

alex_design

The senior attrition point is real and measurable. The people most likely to leave over RTO are senior ICs with 8+ YOE who have strong external options. Those are your hardest-to-replace and highest-comp employees. The ones who stay are either people who like the office, or people with weaker outside options. That's not a great selection effect.

market_realist

Exactly what we saw. The engineers who stayed tended to be more junior or had personal reasons (immigration sponsorship, etc.) that limited their options. Lost a lot of institutional knowledge.

consultant_cam

The pattern you described matches what I've seen advised in change management. Mandate without enforcement is worse than either extreme because it breeds resentment without building culture. If you're going to do an RTO, you have to actually enforce it or the signal is pure noise.