Fordel StudiosThe company tried remote work. Coordination fell apart. Projects slipped. Communication happened in real-time Slack messages that required everyone to be available simultaneously or the thread died. Decisions got made in informal video calls that the right people were not on. Management could not tell who was working and who was not because they had not built any visibility mechanisms other than physical presence. They concluded remote work does not work. They told everyone to come back to the office.
They did not try remote work. They tried in-office work without the office and called it remote.
What Remote Work Actually Requires
Remote work is not in-office work done from home. It is a fundamentally different communication model that requires: decisions documented in writing before they are implemented, not after. Context available asynchronously so that team members in different time zones or schedules can participate without being present in real-time. Meeting culture that defaults to async and reserves synchronous time for decisions that genuinely require it. Trust that replaces presence as the mechanism for accountability.
None of these things are naturally present in organisations built around in-office norms. The coffee conversation is the decision. The whiteboard session is the planning. The hallway context is the briefing. Remove the office and the organisation has no alternative communication infrastructure. The team does not fail because remote work fails. It fails because the organisation's communication was always built on physical proximity and nobody noticed until the proximity was gone.
“RTO mandates are management admitting they do not know how to measure output, so they are going back to measuring presence. Presence is easier to see. It is also not what you are paying for.”
What Successful Remote Teams Built
Every engineering team that makes remote work genuinely function has the same characteristics: written-first culture where the default is to document decisions and context rather than communicate them verbally. Explicit ownership so that anyone can know who is responsible for any part of the system without asking. Meeting discipline that makes synchronous time scarce and therefore valuable. Manager skill in evaluating output rather than presence.
These are hard to build. They require changing the habits of everyone in the organisation simultaneously, including the habits of managers who built their careers on in-person visibility. The companies that called people back to the office mostly tried for twelve months and gave up. The companies that made remote work are the ones who treated it as an organisational design problem, not a policy problem, and invested accordingly.
The Real Cost of Going Back
RTO mandates do not remove the need for async communication. They just hide it behind physical presence for the engineers who comply and lose the engineers who do not. The best engineers — who have the most options — are the least likely to accept a commute they did not sign up for. The engineers who stay are disproportionately the ones who had the fewest options. This is not a coincidence. It is a selection effect that the company is paying for whether it notices or not.
The fix for failed async communication is not an office. It is learning to communicate asynchronously. It is harder. It takes longer. It does not generate the comforting visibility metric of seeing people at their desks. It builds an organisation that can operate effectively regardless of where anyone sits, which is an actual competitive advantage.
