You finally built a team. You have people on salary, a real office, and a hybrid policy because that is what everyone does now. Two days a week in, three days remote. Sounds reasonable.
The problem is most founders set that policy and then never think about it again. They treat hybrid as a scheduling question when it is actually a culture question. And the gap between those two things is where teams quietly fall apart.
What Your Employees Actually Think About the Office
Here is the honest picture. Most knowledge workers are more productive at home for deep, focused work. Fewer interruptions, better personal setups, no open-plan noise. The commute alone, even a modest one, costs them an hour or two of energy before they have typed a single line of code.
But here is what the same people will also tell you: full remote gets lonely. Relationships thin out. Misunderstandings stack up. The newer people on the team never quite feel like they belong. One engineer with nine years of experience put it plainly: he voluntarily commutes ninety minutes each way once a week, not because his company makes him, but because the spontaneous conversations and quick unblocking he gets from a single day in the office pays for itself in career momentum. He treats the office as a tool, not an obligation.
That distinction is everything. Employees who choose to come in because the office gives them something valuable are a completely different phenomenon from employees who come in because a policy says they have to. The first group builds culture. The second group watches the clock.
As Joe Averill explains in his post, Is Hybrid Office Good for Your Company, the question founders should be asking is not how many days to mandate, but what they are actually trying to achieve with in-person time and whether the office they have chosen makes that possible.
The Three Mistakes Founders Make With Hybrid
They pick a number without a reason. Two days in the office is meaningless if nobody can tell you what those two days are for. Meetings that could be emails? Sitting on video calls with remote teammates from a noisier location than your home? That is not hybrid working. That is hybrid theatre. If you cannot explain what in-person time produces that remote time cannot, your employees already know the policy is arbitrary, and they resent it accordingly.
They ignore the office itself. A hybrid policy is only as good as the space behind it. If your employees are coming in to sit in an open-plan room with poor acoustics, no quiet zones, and equipment worse than what they have at home, you have not given them a reason to be there. You have given them a reason to feel annoyed about the commute. The physical space is not a line item. It is the product your hybrid policy is selling, and if the product is bad, no mandate will fix the attendance problem.
They make the days interchangeable. The strongest hybrid setups have structure. One anchor day where the whole team overlaps, used deliberately for collaboration, planning, and the kind of whiteboard work that genuinely benefits from proximity.
Flex days around that for people who want them. Lunio, a Manchester-based ad-fraud prevention company working with Level Workspace, built exactly this model. They structured Thursdays as a full-team day, saw office attendance jump 162%, and watched employees start coming in three and four days a week voluntarily when the contract only required two. The attendance problem solved itself once the office gave people a genuine reason to show up.
What Hybrid Actually Needs to Produce
Think about it from your employee’s point of view. They are trading commute time, money, and the comfort of their home setup for whatever the office gives them. That trade needs to feel worth it, every single time.
The office should produce things remote work cannot easily replicate:
- Relationship depth. The kind that comes from eating lunch together, running into someone from a different team, having a conversation that was not on the agenda. This is what prevents the slow erosion of trust that fully remote teams experience over time.
- Fast unblocking. Problems that would take three Slack messages and a scheduled call to resolve get handled in two minutes when you can tap someone on the shoulder. Junior employees benefit from this the most.
- Collaborative momentum. Whiteboarding a system design, workshopping a pitch, doing a code review in a room with a big screen. Some work simply flows faster when everyone is physically present and can read the room.
Remote work, in turn, should protect the conditions your employees need for deep work: quiet, control over their environment, no commute drain on their energy.
The founder’s job is to make both modes work, deliberately, not to pick a number of days and call it a policy.
Before You Finalize Your Hybrid Setup
Three things worth doing before you lock anything in:
- Ask your team what they would actually use the office for. The answers will tell you more than any framework. If the honest answer is “not much,” your office or your policy needs to change, not your employees.
- Get the space right. If you are signing or renewing a lease, work with someone who understands what hybrid teams actually need. The Level Workspace, Tenant Only Office Space Advisory team has done this for scale-ups across UK and can tell you quickly whether a space will support the culture you are trying to build or quietly undermine it.
- Anchor at least one day as a full-team overlap. Make it worth showing up for. Good lunch, structured collaboration time, something social after. Then leave the rest flexible.
The companies getting hybrid right are not the ones with the strictest policies. They are the ones whose employees genuinely look forward to office days because something good reliably happens there.
Build toward that. The attendance will follow.
