What We Got Wrong About Hybrid Work in the Gulf
The argument about hybrid working has largely been conducted in days per week. Three days, four days, core hours, anchor days.
That framing has proved to be close to irrelevant. Organisations with identical policies report very different outcomes, which suggests the policy was never the variable.
The number of days was the wrong debate
What distinguishes organisations where hybrid works is not attendance. It is whether the work itself was redesigned for distributed collaboration.
Where meetings, decisions and documentation still assume everyone is present, remote days become second-class and the policy generates resentment regardless of the number attached to it.
Proximity bias turned out to be real
Where a portion of the team is more visible to leadership, that portion accumulates advantage in assignments, recognition and progression. This happens without intent and it is measurable if anyone looks.
Few organisations have looked. Checking whether promotion rates differ by attendance pattern is straightforward and frequently uncomfortable.
Onboarding was the genuine casualty
Experienced employees with established networks adapted well. New joiners did not.
The informal learning that used to happen by proximity has no distributed equivalent unless one is deliberately built. Organisations that noticed this early and rebuilt onboarding around structured contact have far better retention among recent hires than those that assumed it would resolve itself.
Regional factors were underweighted
In this region, commute times, summer heat and a workforce with substantial international family commitments all affect the calculation differently than in the markets where most hybrid policy was written.
Importing a policy designed for a different context and applying it unchanged has been a common and avoidable mistake.
Design the work, then set the policy
The useful sequence is the reverse of the one most organisations followed. Establish which activities genuinely benefit from being in the same room: complex problem solving, difficult conversations, early-stage creative work, developing junior colleagues.
Then build the attendance pattern around those. It usually produces fewer required days than a blanket policy and considerably better attendance, because people can see why they are coming in.
It also gives managers something to plan around. Anchor days chosen because a team genuinely needs them are respected; anchor days imposed centrally are worked around. The organisations still arguing about the number are generally the ones that never did this work.
