Most Return-to-Office Mandates Fail Because the Office Was Never Designed for the People Returning

At dinner, the first night of a business trip last week, with a potential partner company I am not permitted to name, one of their senior developers mentioned he had read my posts on LinkedIn arguing against return-to-office. He had clearly done his homework on everyone he was meeting that week, and he brought it up warmly, not as a challenge.

I have built a public position on this: RTO is usually a control mechanism wearing a culture initiative's clothes. So we spent part of dinner talking it through, friendly and unhurried, him and a few others telling me what they actually liked about working the way they did.

The next day I toured the campus, and I understood. A workforce in the thousands, not all of them developers: groundskeepers, culinary staff, the people who keep an entire campus running, every one of them colocated, no offshore teams, no consultants filling the gaps. Food, dry cleaning, the small services that eat into anyone's evening, all priced at cost, so no one had to weigh convenience against their paycheck. Some employees had been there more than a decade, and turnover was close enough to zero that it came up before I asked.

This was not a sterile cubicle farm. It was a masterpiece of architecture and design across multiple buildings on one campus, built with the same care the company put into deciding who worked there. They had not invented full colocation. They had perfected something my own career started inside, back before offshoring and globalization scattered every technical team across time zones and buildings. Most of the industry gave that up; this company never did.

Most return-to-office arguments have nothing to do with this. Most of them come from leaders who cannot manage what they cannot see, who have decided that presence is a proxy for productivity because presence is the only variable they know how to measure. I do not build systems that require a room. I build systems that maximize valuable output regardless of where the output happens. But I watched a room do something a video call genuinely cannot: put the right people in front of the same whiteboard, at the same moment, with nothing lost in translation. Almost no company has kept that room. This one had.

Here is what happens instead, at nearly every company that mandates a return without those conditions. The employees with other options leave quickly, because they were never asked and now know exactly where they stand. The employees without options stay, and the relationship sours slowly instead of ending cleanly. Output declines, quietly at first, the way morale always declines before it collapses. The manager who ordered the return notices the decline and responds the only way they know how: more oversight, more check-ins, more managing of the thing they could not manage from a distance and now cannot manage in person either.

That response has a name. It is the Overcompensation Loop: control rises, autonomy falls, the falling autonomy confirms the original fear, and the fear demands more control. If your management style only works because it is propped up by hallway conversations, that is not a system. It is Heroics wearing a return-to-office badge, and it fails the same way heroics always fails: quietly, until it fails completely.

The leaders who get this right are not different from the ones who get it wrong. They stopped trying to fix output by mandating presence, and started asking a harder question first: what would make our best people choose this.

The system does not need more return-to-office. It needs three conditions this company had before its policy became defensible: full colocation, not the fragmented kind where every teammate sits in a different building and takes every meeting on a headset; infrastructure the technical workforce designed, not infrastructure management selected and then surveyed for reaction; and a track record, near-zero turnover among veteran employees, that proves people are choosing the conditions rather than enduring them. A leader who cannot point to all three already in place is not solving an output problem. They are looking for cover to solve a control problem instead.

There is one question that tests for this faster than any policy memo: is your team genuinely excited to return to the working conditions you are providing? Not compliant with. Not resigned to. Excited by. If the honest answer is no, the mandate will not fix what you think it fixes, and no amount of enforcement changes the answer.

I write about structural leadership for technical leaders in high-stakes operating environments. The full operating model is in LeadershipOS: http://TheLeadershipOSBook.com

---

I write about structural leadership for technical leaders in high-stakes operating environments. The full operating model is in LeadershipOS: http://TheLeadershipOSBook.com