When a company says it has a hybrid policy, it could mean one of two very different things. Either everyone comes in on set days, say Tuesday to Thursday. Or people decide for themselves, within broad guidance such as “come in when it is useful”. I want to compare the two properly and then say which I would pick, with the caveat that the answer depends on the work.

Model A: fixed anchor days

The company names the days. Everyone in a department, or everyone full stop, is in the office on those days. The attraction is predictability. A manager can schedule a workshop for Wednesday knowing the team will be there. A new joiner sits next to people instead of an empty row. The facilities team can plan canteen and transport against a known pattern.

The costs are real too. If all 400 people come on the same three days, you need roughly desks for everyone on those days, which defeats the saving that hybrid was supposed to bring. Commutes in Bengaluru or Mumbai on a Tuesday are what they are. And anchor days can become a performance of presence: people come in, sit on video calls with colleagues in other cities, and wonder what the point was.

Model B: full flexibility

Here the company sets a principle, perhaps a minimum such as eight days a month, and lets teams and individuals arrange the rest. It suits knowledge work where much of the day is individual. It respects the fact that a parent with school drop-offs and a bachelor in a shared flat have different needs.

The weakness is coordination. If everyone picks the days that suit them, the days that suit nobody mean no overlap, and the office becomes a place where you come in and find your team is at home. It also moves a burden to managers, who now have to negotiate patterns and defend them as fair. And without a clear rule, flexibility quietly favours people who are close to the boss or have the confidence to ask.

A quick look at seats

An illustration. A firm has 400 employees and 240 desks, a 0.6 desk ratio. Under Model A with Tuesday to Thursday for all, each of those three days needs 400 seats; you are short by 160 every time. To fit the desk count under fixed days, you would split the workforce into two groups of 200 on different days, which means fewer overlaps within teams. Under Model B, if average attendance is 50 percent, that is 200 people on a typical day, comfortably inside 240. But attendance clusters around midweek, and if it reaches 70 percent on Wednesdays you need 280 seats. Free choice does not produce an even spread.

The arithmetic is simple, but companies often sign leases before doing it.

Where I land

I lean toward a third design that borrows from both: a company-wide floor (a minimum number of office days a month so that nobody drifts into permanent remote by accident) and team-level anchor days chosen by the team and approved by the department head. The team picks its days because the team knows when it needs to be together: sprint planning, customer reviews, onboarding weeks. Different teams choose different days, which also smooths seat demand.

I prefer it to a single company-wide fixed pattern because the pattern is imposed by people who do not do the work. And I prefer it to pure flexibility because most people, left alone, optimise for their own convenience, and the shared benefit of being together is a group property.

What any policy needs on paper

  • Who it covers, and which roles are exempt (field sales, plant, front desk).
  • The minimum expectation and how it is counted, including what happens with leave and travel days.
  • How exceptions are requested and decided, and by whom, so that it is not a favour.
  • Working hours and availability on remote days, kept reasonable.
  • Equipment, data security rules for working from home, and any allowance. Check how your state’s rules or your company’s tax treatment affect reimbursements.
  • Review date. A policy written in one year’s mood should be checked against the data a year later.

When this stops working

Hybrid of either type depends on managers who can run a team across two settings. If the manager only values what they can see, remote days will hurt careers and people will notice within a cycle. Track promotion and rating outcomes by attendance pattern. If the remote-heavy group is consistently rated lower, you have a proximity bias, not a policy.

Also be honest about what you want. If leadership believes that being together every day matters for the business, say so and set a full office policy; pretending to offer flexibility and then penalising it is worse than either. Whatever the design, employees accept a clear rule far more easily than a vague one they have to guess at.

Figures and names in the examples are illustrative.

Leave a Reply

Trending