Problem Statement
THE FLOOR WAS FULL. NOBODY COULD SAY WHY.
A facilities manager at a mid-sized tech company was once asked, casually, over coffee, why the fourth floor still ran at full capacity — badges, desks, the works — three years after half the team had proven they could ship just as well from home. She paused longer than the question should have needed. Then she said: "Honestly? Nobody's ever asked me to turn it off."
That's not a story about lazy management. It's a story about how offices actually die — not with a decision, but with the absence of one. Somewhere, a lease got signed for reasons everyone in the room could name. Years later, the reasons changed, or vanished, or were never really tested — and the lease just kept renewing, because renewing takes no courage and questioning takes some.
This isn't a story about remote work winning an argument. What's actually happening is quieter than that, and more interesting. The office did real work once — several different kinds of real work, stacked on top of each other, so seamlessly nobody noticed there were four separate jobs happening inside one building. Some of those jobs are finished. Some were never really the office's to do in the first place. And at least one of them is still happening, right now, and getting worse the longer nobody names it.
What You Will Take Away
This piece doesn't argue offices are dead, and it doesn't argue they're sacred. Both of those arguments are easy, and easy arguments are usually wrong. What it argues instead is this: the office was never one thing pretending to be simple. It was four things — equipment, apprenticeship, coordination, and belonging — bundled into a single badge and a single lease, for so long that most people stopped being able to tell them apart. Technology genuinely finished one of those jobs. It mostly finished a second. The other two are still open, and pretending they're closed is the actual mistake — not the debate about which days to come in.
THE FOUR JOBS NOBODY SEPARATED
LEGACY ISN'T THE BUILDING. IT'S THE HABIT THE BUILDING TAUGHT.
Ask most people why offices exist and they'll reach for the newest justification available — culture, collaboration, energy. Rarely the oldest, truest one: the equipment couldn't move. A mainframe in 1985 didn't travel. Neither did a filing cabinet, a landline, or the one printer the whole floor shared. You went to the building because the tools of the job physically lived there and nowhere else. That's not a metaphor. That's just what happened.
And then, quietly, the tools learned to travel. A laptop today does more than the server room that used to need its own air conditioning. The filing cabinet became a folder that syncs itself. The one shared printer became irrelevant. The single loudest, oldest reason for the office — the only reason, originally — simply stopped applying, sometime in the last two decades, without anyone holding a ceremony for it.
But the building didn't get quieter. It got busier with new reasons — reasons that arrived to justify a habit that had already outlived its original logic. Culture. Synergy. "The way we've always worked." Nobody sat down and decided these were now the reasons. They just filled the space the old reason left behind, the way water fills a container without anyone pouring it.
THE PART THAT'S HARDER TO ADMIT
SOME OF WHAT THE OFFICE DID, NOTHING HAS REPLACED YET.
Here's where it gets uncomfortable, because the honest version of this story doesn't let anyone off easy.
Coordination and strategy — the meetings, the planning sessions, the arguments that used to require a whiteboard and a room — mostly survived the transition. Video calls aren't as good as being there, but they're good enough for most of what coordination actually needs, and the data backs this up more than nostalgia wants to admit.
Apprenticeship didn't survive nearly as well, and this is the one people undersell the most. A junior engineer used to learn what "good" looked like by watching a senior one make a hard call in real time — not reading about it afterward, not in a scheduled 1:1, but by being two desks away when it happened, absorbing the judgment nobody had written down because nobody thought to. Remote teams have tried to replace this with documentation, recorded sessions, deliberate mentorship programs — and some of it works. But ask any manager honestly whether a new hire's first six months feel the same, and most will admit, if you give them a moment, that something got harder to pass down. Not impossible. Harder.
Belonging is the one everyone feels and almost nobody names accurately. People don't miss the desk. They miss the version of themselves that existed around other people — the version that got noticed on a bad day without having to ask for help, that built trust over a shared lunch instead of a scheduled call, that felt like part of something instead of a name in a directory. Calling this "culture" is how companies avoid saying what it actually is: a real human need that a building used to meet as a side effect, for free, and that now has to be built on purpose, which is much harder than it sounds and much easier to fake with a Zoom happy hour that fools no one.
THE UNCOMFORTABLE ARITHMETIC
"WE OFFER HYBRID" IS NOT THE SAME THING AS AN ANSWER.
Most companies, faced with this, land on some version of: we're hybrid now, we've solved it. That's honest. It's also not the same as having actually done the sorting.
Hybrid, done by policy instead of by purpose, just splits the same unexamined habit across fewer days. Three days in the building doesn't mean three days of the right things happening in the building — the apprenticeship moments, the trust-building, the hard calls made in person. It usually just means three days of the same meetings that were already working fine on video, now happening in a room for no better reason than the calendar said so.
The real difference isn't between remote and hybrid and in-office. It's between a policy built from a list of what your work actually needs — and a policy built from what your company has simply never stopped doing.
IMPLEMENTATION REALITY
| Original Job | What Technology Solved | What's Still Open | The Real Question |
|---|---|---|---|
| Equipment | Fully — computing, storage, and files travel with the person now | Nothing | Why does a policy built for this reason still exist? |
| Coordination & Strategy | Mostly — routine planning and decisions work well remotely | High-stakes, sensitive decisions still benefit from a room | Which decisions actually need one? |
| Apprenticeship | Partly — documentation and recording help, but don't fully replace it | Passing down judgment, not just information | How does a junior person still learn to make the hard call? |
| Belonging | Barely — video approximates contact, not connection | Building trust and morale without relying on a lease to do it | Who is deliberately building this, instead of assuming the building will? |
What Technology Solved
Fully — computing, storage, and files travel with the person now
What's Still Open
Nothing
The Real Question
Why does a policy built for this reason still exist?
What Technology Solved
Mostly — routine planning and decisions work well remotely
What's Still Open
High-stakes, sensitive decisions still benefit from a room
The Real Question
Which decisions actually need one?
What Technology Solved
Partly — documentation and recording help, but don't fully replace it
What's Still Open
Passing down judgment, not just information
The Real Question
How does a junior person still learn to make the hard call?
What Technology Solved
Barely — video approximates contact, not connection
What's Still Open
Building trust and morale without relying on a lease to do it
The Real Question
Who is deliberately building this, instead of assuming the building will?
ABOUT THE AUTHOR
The author has spent fifteen years working across software delivery, enterprise architecture, and product engineering — across teams ranging from three-person startups to organisations with technology functions measured in thousands of headcount. The observation at the centre of this piece is not theoretical. It comes from watching early-career engineers on fully remote teams take visibly longer to develop the judgment that used to pass, almost invisibly, from a senior engineer working two desks away — and from the specific moment of recognising that the gap wasn't about talent, tooling, or effort. It could only be explained by which of the office's original jobs a team had quietly stopped doing on purpose, and which it had simply stopped doing.
Conclusion
The office was never one thing. It was four things, stacked so tightly nobody had to tell them apart — until the day one of them quietly disappeared and took its excuse with it.
Technology retired the first job completely. It mostly handled the second. The third and fourth — teaching judgment, and making people feel like they belong somewhere — are still open, unfinished, and getting worse in companies that assume a badge swipe was ever doing that work on purpose in the first place.
The honest answer to whether offices are still necessary was never yes or no. It's a shorter, harder question most companies still haven't asked themselves: which of the four jobs are you actually still doing, and which one have you just stopped doing without deciding to?
"The office never really argued for itself. It didn't have to — it did four jobs quietly enough that nobody noticed there were four. The mistake isn't that companies kept the building. It's that most of them never separated the jobs long enough to notice one had already finished, and two more were being done badly, by habit, instead of on purpose."
