Hybrid Work

For a while the question was treated as binary: come in every day, or don't come in at all. Then a few years of company-wide remote work put a price tag on each side. Writing, designing and coding went better at home than at a desk in an open office. Getting a new hire connected to a team, or closing out a discussion where people had drifted into different positions, went noticeably worse through a screen.

So the companies that posted "everyone back in the office starting next month" tended to get the same result. People who had just reclaimed two hours of commuting a day booked conversations with their managers, and the ones who stayed came in to sit on video calls all day. Companies that kept everyone remote ran into the mirror image: someone three months into the job still couldn't say who owned what on the team. Picking whom to ask was itself a task, so a question that would have taken ten seconds from the next desk sat in a chat channel overnight.

Hybrid work is the answer that stops choosing between the two and splits by the kind of work instead. Pick the work that pays for people being in the same room, gather for that, and let the rest happen wherever each person prefers. The hard part is deciding which work belongs on which side.

The rules usually start with three decisions: how often people come in, who sets that, and what the office days are for.

1. Frequency. Either a count — two or three days a week — or a block, like one week per quarter. A count makes daily life predictable; a block lets people who live far away take part at all.
2. Who decides. The company can fix the days for everyone, each manager can set them per team, or each person can choose. Letting everyone choose is the most flexible and produces the most common failure: you come in and the people you needed are home. Teams therefore tend to align on shared days.
3. What office days hold. Put the work that pays for being together there — discussions that have split, a new hire's first week, sessions where several teams have to be in one place. Doing solo work in the office spends the commute and buys nothing.

One time rule usually rides along. A core time block where everyone overlaps keeps an urgent question from sitting unanswered for half a day on remote days.

Exceptions get written down too. Applying the same count to someone in another city, someone with care responsibilities, or someone with limited mobility turns a policy into a filter. What matters is deciding in advance how those people get the value of the days they miss — two consecutive days once a quarter, for instance.

The rule that breaks most often is the mixed meeting. Three people in a room and four on screen means the room talks to itself and the screens lose any opening to cut in. That's why many teams require everyone to join from their own laptop, so every participant appears as the same size rectangle.

Most of the places this policy bites are outside the meeting room.

Job posts carry it as a condition — "two days a week in the office." Candidates use it to work out commute time and whether they'd have to move, so leaving it out means discovering the mismatch at the final interview.

Office layout shifts with it. Different people come in on different days, so assigned desks give way to booking a spot on arrival, and meeting rooms and phone booths get added. Much of an office day turns out to be calls with people who are remote that day.

Information rules move too. Without the habit of writing decisions down — documentation first — something settled in a hallway on an office day never reaches whoever was home. For the same reason, written asynchronous communication carries more weight than it did when everyone was in five days a week. Meeting hygiene follows along: office hours are the most expensive hours of the week, so what fills them gets decided before the calendar does.

Reviews are affected as well. People who are visible feel like people who did more, which tilts ratings and good assignments toward whoever comes in most. Countering that means writing down in advance that the basis for review is what shipped, not who was seen.

"My team is in on Tuesdays and Thursdays, so I'll move that meeting to Tuesday."

Pulling work that needs a room onto the day the room is full.

"This one's a hybrid meeting, so everyone join from your own laptop."

A request to put the people in the room and the people at home on the same footing.

"We left the work arrangement out of the posting, so the interview turned into a conversation about it."

Office frequency is a condition candidates weigh about as heavily as pay.

Pagedeck moved from fully remote to two office days a week once the company passed 45 people. At first everyone picked their own days, and about a month in Mia pointed out a pattern: on the days she came in, the designer and the engineer she needed were at home. The company switched to per-team days and stacked cross-team sessions on Wednesday, the one day every team overlapped.

Grace added a line to it. Office days shouldn't hold solo work — only things that involve other people. Calendars on those days started to look different afterward.

The common misreading is that hybrid automatically combines the good parts of both. Mixing them sounds like keeping the upside of each. Without tight rules, what combines is the downsides: you still commute, you get to the office and sit on video calls, and on remote days you hear about decisions after they were made. Mixing isn't the answer on its own — deciding what goes on which side is.

The other one is assuming that because there are office days, remote practices matter less. Two days in still leaves three days out, and missing documentation leaves the same hole it always did. In one respect hybrid is harder than going fully remote. When everyone is remote, everyone is under the same conditions; under hybrid the people who were in the office and the people who weren't end each day with different information. Leave that gap alone and decisions and opportunities drift toward whoever shows up most.