Back to the Office to Sit on Video Calls?

Posted by & filed under .

Over-the-shoulder view of a woman in an office on a video call with six colleagues shown on her laptop screen.A statistic has been getting a lot of attention lately, and I think it deserves more than a shrug emoji. A New York Fed staff report, surveying college-educated workers, found that 48.8% of office-based workers had no in-person meetings at all on their most recent day at work. And on their in-office days, 70.6% of them had at least one teammate who wasn’t in the office.

Let me translate this for you: a lot of people are commuting into an office to sit on video calls with colleagues who are at home. Or, quite likely, with colleagues two desks away, because that’s where the meeting link was. (Bonus points for the room where four people join the same call from four laptops, producing the kind of audio feedback loop a 1970s rock band would be proud of 🙂)

The Office Isn’t the Point; Coordination Is

Here’s the thing: return-to-office is clearly winning on attendance. Johnson Controls’ 2026 workplace survey says 67% of employees now work in the office five days a week, up from 57% the year before. But attendance was never the goal. The argument for the office was collaboration: whiteboards, quick unblocking conversations, mentoring the junior engineer who’d otherwise sit stuck for a day rather than ask on Slack. If half of the workers in the building don’t have a single face-to-face meeting, they’re getting the commute without the collaboration. That’s the worst of both worlds.

I don’t think the fix is “everyone back five days” or “everyone remote forever”. I’ve seen teams do great work both ways. What doesn’t work is a policy that controls where people sit but not who’s there together. A mandate counts badges; a good engineering leader cares about whether the right people are in the same room on the same day.

What I’d Do as a CTO

  • Pick anchor days per team, not per company. The team that needs to whiteboard the architecture should be in together; it doesn’t matter much whether accounting is in that day too.
  • Decide what in-person time is for and protect it: design sessions, planning, onboarding, pairing. Then push status updates and anything that’s mostly reading out loud into documents, or to an agent that writes the summary.
  • Default meetings in the building to a room, not a link. Sounds trivial; it isn’t.
  • Measure outcomes, not attendance. If a team ships well with two anchor days, why on earth would you force a third?

As a side note, I suspect AI makes this question more pressing, not less. When agents write a growing share of the code and the status reports, the work left for humans is mostly judgement, alignment and teaching: precisely the things that benefit most from being in a room together. Wasting office days on video calls is wasting the most valuable time you have.

Bottom line: getting people back to the office was the easy part. Getting them in the same room, on the same day, for something worth the commute, is the actual management job.