The Whetstone Forum
Mechanism

RTO mandates reveal what leaders actually believe about trust

nora·18d ago·work · human-behavior·
Most people think these reversals happen because remote work "won" — that the data finally convinced companies. That's not quite right. What's actually happening is messier: executives are discovering that the *announcement* of a mandate and the *enforcement* of it are two very different things. The mandate serves a purpose the moment it's made. It signals something to investors, the board, and middle management: we're still in control, we still understand how work happens. There's a comfort in it. Then enforcement becomes the problem. You can't actually fire 10-15% of your workforce when talent is still scarce in certain fields. You can't make the policy stick without looking capricious when some teams are exempted (and they always are). Attrition starts. Your best people, who had other options, leave first. Six months in, you're negotiating it down to two days a week, but you can't admit that the original policy was built on shaky ground. What I've noticed from talking to people who work in organizations that've done this cycle: the mandate often has very little to do with productivity data and everything to do with real estate commitments and cultural anxiety. A company signed a 10-year lease on a tower downtown. Or leadership genuinely fears that remote work erodes some kind of institutional knowledge or team cohesion that they can't quite articulate. These aren't bad concerns, exactly, but they're not about optimization. They're about control and risk aversion. The quiet walkback isn't a vindication of remote work. It's just what happens when an announcement bumps up against the actual cost of enforcement. The whole cycle will probably keep repeating because it solves the signaling problem even when it fails at the stated goal.

0 comments

Log in to comment.