Skip to content

columnist vs journalist

Topic: Arguing a public position on return-to-office
Axis varied: voice
A: Columnist B: Journalist

Both are public writing on a contested policy, and they source their authority from opposite places.

A stakes a position in the first sentence. “I want to go on record: mandating full-time office return is a mistake, and so is abandoning [the office].” The piece is accountable for that claim and spends itself defending it.

B opens on a person and a quote. “When Petra Villanueva, a senior designer at a mid-size software firm, described her company’s return-to-office mandate to me, she reached for one word: ‘theater.’” The judgment is present, and it belongs to a named source rather than to the writer.

The sharpest single tell. A says I want to go on record. B lets someone else say theater. Strip every first-person judgment from each: A collapses, B is untouched, because B never spent any.

A: columnist

Our company is about to decide what “work” looks like for the next few years, and I want to go on record: mandating full-time office return is a mistake, and so is abandoning shared space entirely. The answer is deliberate hybrid - a handful of fixed anchor days for everyone, the rest genuinely flexible.

I have been thinking about this because I have lived both extremes. I spent three years in a fully remote role, enjoying focused mornings and colleagues I would never have reached in one metro area. I also spent three years on a team that sat together five days a week, and I still feel the difference that made when we faced an actual crisis: someone turned around, caught my expression, and the problem got solved in four minutes instead of four days.

Neither of those experiences is a study. They are observation, and I think observation is the honest currency here.

The case for full return is not wrong on its own terms. Proximity builds trust, and trust is what makes unguarded collaboration possible. You cannot replicate the moment when two people sketch something and a third person walks by and changes everything. That is real.

But full return is not the only way to get it. It is just the easiest policy to write.

Fully remote is not costless either. It quietly taxes people with the least social capital - the new hire who cannot read the room, the early-career employee who learns by watching. Those costs do not show up on any dashboard. They show up, slowly, in who stays.

Anchor days fix the coordination problem without dismantling the flexibility that makes the job worth taking. Pick two or three days when everyone is in. Make them reliable. Build the rest around focused work, wherever that happens.

The office-first leaders want culture. The fully-remote advocates want autonomy. Deliberate hybrid does not split the difference - it takes both seriously enough to design around both.

That is the position I am willing to be quoted on.

B: journalist

When Petra Villanueva, a senior designer at a mid-size software firm, described her company’s return-to-office mandate to me, she reached for one word: “theater.” Management required three office days per week. Within a month, managers were badge-scanning for compliance while the actual project work continued over the chat tool, unchanged. “We drove forty minutes each way to sit in a room and do video calls,” she said.

Her firm’s experiment failed. That does not settle the debate. It documents a misuse.

The dispute, in weeks of reporting conversations with workers, team leads, and one operations director who asked not to be named, is not really about location. It is about which interactions benefit from proximity and whether the schedule protects those moments. Office advocates name trust-building and the unplanned exchange that reroutes a project. Remote advocates name recovered commute hours, a wider hiring geography, and the quiet that focused work requires. Both are accurate. Neither resolves the question.

Elena Marsh, who manages a team distributed across four time zones, said her group stopped arguing about headcount in the building and started arguing about the calendar. “That changed everything,” she told me. Her team now holds two shared anchor days per month, scheduled around decisions that benefit from shared physical presence. The rest is flexible. “People who never came in said it was the first time the office felt like it existed for them, not just for management,” she said.

Office-first leaders read that as insufficient. “Two days a month is a social club, not a working culture,” one operations VP told me, declining to be named. Fully-remote advocates worried the anchor days were a precedent. Both concerns deserve weight.

Neither side has produced, in the reporting I could do, evidence that mandatory full presence reliably delivers what its proponents promise - or that full flexibility alone sustains the trust distributed teams most often report losing first. The calendar is where that case gets made or broken.