Remote Work Is Not a Technology Project: It Is an Organizational Transformation

In May, Twitter told its employees that those who could work from home would be allowed to do so permanently. Shopify’s Tobi Lütke announced that “office centricity is over”. Mark Zuckerberg said he expected up to half of Facebook’s employees to work remotely within five to ten years. A year ago each of these statements would have been treated as an eccentric experiment. Today they are strategy.
Most organizations, however, approached remote work as an IT problem. In March that was correct. Someone had to ship laptops, scale the VPN, roll out collaboration tools and close the security gaps that appeared when millions of people started working from kitchen tables. Those projects were executed remarkably well.
The problem is that six months later many companies still think the project is finished.
The questions technology does not answer
Remote work quickly exposed questions that no collaboration platform can answer.
How do managers measure performance? Many managers discovered that they had been measuring presence rather than output. When presence disappeared, some of them had nothing left to measure. The reaction in a number of companies was surveillance software, which tells you more about management than about employees.
How do teams maintain trust? Trust built in an office over years survived the first months on credit. New hires, new teams and new managers have no such credit. The cost of that will appear slowly, in onboarding, in collaboration across functions and in attrition.
How is culture transmitted? Culture has always traveled through informal channels: corridor conversations, observing how senior people handle difficult situations, overhearing a negotiation. None of that happens on a scheduled video call.
What we learned about productivity
The early data on productivity has been surprisingly good. Many organizations report stable or even improved output. But I would be careful with those numbers. Part of the effect is a crisis effect: people worked longer hours, had nowhere to go and were anxious about their jobs. That is not a sustainable operating model.
What the experience does prove is that productivity was never simply a function of physical presence. It depends on clarity of objectives, autonomy, the quality of communication and the quality of management. Remote work did not create those dependencies. It removed the office, which had been hiding them.
Organizational design, not HR policy
Fifty years ago, Melvin Conway observed that organizations design systems that mirror their own communication structures. MIT’s Thomas Allen showed in the 1970s that communication between engineers drops sharply with physical distance, even within the same building. Both insights now work in reverse. If communication no longer depends on proximity, then the structure of the organization no longer has to follow the floor plan.
That is the real transformation. It affects how teams are formed, how decisions are documented, how managers are trained, how talent is hired across geographies and what the office is for. Treating it as an HR policy about home office allowances misses the scale of the question.
For leadership teams and boards, the implication is practical. Before any decision about real estate, there should be a decision about the operating model. What work requires people to be together? What work is better done alone? Which management practices need to be rebuilt? Only then does it make sense to decide how many square meters the company needs.
Leadership question: If employees no longer need to be physically present to create value, what exactly is the purpose of the traditional office?


