The hard parts of going hybrid, and what actually helps
Announcing a hybrid policy takes an afternoon. Making it work takes a year of small decisions about fairness, coordination and space. Six problems almost every organisation meets, and the practices that solve them.
Camille Arnaud, Co-founder and head of product, Welyne
7 min read
Before we wrote a line of Welyne WorkOne, we spent months talking to people who had just rolled out hybrid work: HR directors, office managers, team leads, travel coordinators. The stories were different, but the problems were not. The policy was usually fine. What went wrong was everything around it — who decides, who knows, and what happens on a Tuesday morning when forty people arrive for thirty desks.
Nobody knows who will be in
The most common complaint is also the simplest. People make the effort to come in and find their team at home. After two or three empty Tuesdays, they stop coming. The office empties not because of the policy, but because of the uncertainty.
What helps is a shared plan: a week view where everyone marks where they intend to work, visible to their team before they decide. It turns the question "should I go in?" into "the team is in on Thursday". Planning becomes social rather than individual.
Rules applied differently by every manager
A policy that says "up to two days a week, with manager approval" is really fifty policies, one per manager. Some approve everything, some refuse everything, and employees compare notes. Perceived unfairness does more damage than a strict rule applied evenly.
- Write the rules precisely: days per week and month, allowed weekdays, notice required.
- Approve automatically when a request is within those rules.
- Send only the exceptions to managers, with the reason they are exceptions.
The office is sized for 2019
Hybrid organisations end up with offices that are empty on Fridays and overflowing mid-week. Facility teams know the building is underused on average but cannot prove how many desks they need on the busiest day, so nothing changes.
Desk booking with check-in solves the measurement problem. Within a couple of months you know the real peak by weekday and by floor, and you can make small, reversible changes — closing a floor on Fridays, redrawing team neighbourhoods — before committing to anything larger.
Travel lives in another system
Business trips are part of where people work, but they usually live in e-mail threads, spreadsheets and an agency portal. Managers approve trips without knowing the cost; the team calendar says someone is in the office when they are in Milan.
Treating travel as another work mode — alongside office, home and client site — fixes the calendar and the approvals at once. A trip request that carries its own estimate and policy checks takes a manager seconds to approve, and the traveller's week shows where they really are.
Managers become schedulers
Without tooling, managers end up coordinating attendance by chat: who is coming Thursday, can someone cover the client visit, did anyone book a room. It is invisible work and it falls unevenly. The managers most willing to do it get the most of it.
The practices that remove it are unglamorous: one inbox for approvals instead of five channels, anchor days chosen from real data rather than preferences, and rooms booked for the team once rather than argued over weekly.
Nobody measures whether it works
Most organisations cannot answer basic questions a year in: how often do teams actually overlap, how much of the office is used, what did hybrid work do to our carbon footprint, are some teams struggling? Without answers, the policy becomes a matter of opinion and the loudest opinion wins.
Hybrid work doesn't fail at the policy. It fails in the gaps between the policy, the building and the calendar.
Start small, then widen
The organisations that make hybrid work stick rarely launch everything at once. They start with the problem people feel most — usually finding a desk or knowing who is in — with one or two teams, adjust the rules after a month of real use, and widen from there. Remote-day policies come next, then travel, then the reporting that ties them together.
That sequence shaped how we built Welyne WorkOne: each part works on its own, and each one makes the next more useful. But the principle applies whatever tools you use. Make the plan visible, make the rules consistent, measure what happens, and change what doesn't work. Hybrid work is not a policy you announce. It is a practice you keep adjusting.