The RTO Memo Nobody Believes
I read the memo. "In-person collaboration drives innovation." "We're seeing better connection across teams." "This is about culture, not control."
Then I looked at the turnover data. Then I looked at the Slack analytics from before and after. Then I looked at the actual meeting recordings.
The memo and the data were not friends.
The Theater Is Very Convincing
RTO mandates have a beautiful narrative. Leaders genuinely believe it. I don't think they're lying—I think they're pattern-matching to a story they already knew.
"I've always done my best work in an office. Therefore, everyone does their best work in an office." It's intuitive. It feels true. It matches their lived experience.
The problem is that their lived experience is not data. And when you measure actual productivity, collaboration metrics, and output quality, the RTO narrative falls apart pretty quickly.
But here's the thing: I've never seen a leader stand up and say "we're mandating RTO because my previous company culture was office-based and I'm uncomfortable with the alternative." So instead they write the memo about collaboration and culture.
What The Data Actually Shows
I've got access to pulse surveys from twelve companies that did RTO mandates between 2023 and 2025. Same pattern in eleven of them:
Collaboration meetings increased (because people were now mandated to be there) Actual productivity declined Voluntary turnover spiked 2–3 months after the mandate The high performers left first The meetings became less efficient, not more
The collaboration metric that went up? Meeting attendance. Not collaboration quality. Not output. Just showing up.
One company measured it properly. They looked at lines of code, bugs shipped, and code review cycles before/after RTO. All three got worse. When leadership saw the data, they... didn't change anything. They just stopped looking at those metrics.
Why Nobody Says It Out Loud
There's something people need to understand about organizational honesty: it's really hard to admit you're mandating something for reasons you can't articulate.
A CTO told me once, offline, that the real reason for RTO was that he couldn't tell if people were "really working" when they were remote. He was uncomfortable. He wanted to see them. That's honest. That's also not a business reason.
But you can't put that in a memo. So instead you talk about culture and serendipitous hallway conversations. And everyone nods along, even though they know that's not why.
I've sat in leadership meetings where someone would bring data showing RTO was hurting retention. The response was always some version of "yes, but..." followed by an anecdote about how they ran into someone in the kitchen and had a great idea.
Kitchen serendipity vs. 40% turnover. But the turnover data is scary. The kitchen story is comforting. Guess which one won.
The Real Cost
Here's what I've seen happen:
RTO mandate arrives High performers (who have other options) start job searching You lose institutional knowledge You hire replacements (at higher salaries because the market's hot) You're paying more, shipping slower, and all the serendipitous collaboration is now spent onboarding Someone presents the turnover spike as "market conditions" You double down on RTO because admitting it was wrong is now even harder
I watched a tech team go from 8% annual turnover to 32% after RTO. Then leadership hired a culture consultant to figure out the problem. The consultant wrote a beautiful report about improving psychological safety and team cohesion. Nobody mentioned RTO.
Because at that point, you're trapped. Admitting that RTO tanked retention means admitting that the memo was theater. Easier to buy a consulting engagement.
The Uncomfortable Truth
Remote work is not perfect. Async communication is hard. Some collaboration is easier in person. All true.
But if you're mandating RTO, you probably don't have great data about why. You probably have a story that feels true. And you're probably losing people because of it.
The companies moving fast right now? Most of them are fully remote or trust people to pick. They're not trying to engineer serendipity. They're hiring whoever's best, wherever they are.
What Actual Leaders Do
If you're running a team: before you mandate RTO, get real data about whether it works for your team. Measure productivity. Measure retention. Measure collaboration quality (not meeting attendance—actual collaboration).
Then decide based on data, not intuition.
If the data says RTO helps, mandate it. You have evidence. If the data is mixed or negative, pick a different strategy. Maybe it's a once-a-month all-hands. Maybe it's team-specific. Maybe it's trust.
But don't write a memo about culture and collaboration when what you really mean is "I miss the office." That's the difference between leadership and theater.
Most RTO mandates are the latter. And everyone knows it.