Hybrid Work Fails in the Space Between Policy and Teamwork

Most organisations now have a hybrid work policy.

Remote work rules are formalised. Attendance expectations are defined. Employees generally know how many days they are expected to be on-site and what level of flexibility is allowed.

From an executive perspective, hybrid work can therefore appear largely stabilised. In many respects, it is.

Yet many leadership teams continue facing familiar frustrations. Collaboration remains uneven. Teams struggle to synchronise effectively. Office attendance fluctuates unpredictably. Managers spend considerable time recreating alignment that previously emerged more naturally through shared presence and informal interaction. The persistence of these tensions suggests that the challenge is no longer primarily about policy.

Most organisations have invested significant effort in defining the rules of hybrid work. Far fewer have invested the same energy in defining how teams should operate once flexibility becomes the norm.

And that distinction matters because hybrid work is ultimately experienced at team level, not organisational level.

Policies create consistency. Teams create operating reality.

Most hybrid models were designed centrally.

The rationale was entirely understandable: create fairness, simplify governance, avoid fragmentation and maintain a degree of consistency across the organisation. The difficulty is that work itself does not happen at organisational scale.

Execution happens within teams. This is where priorities are negotiated, dependencies managed, decisions coordinated and information shared. It is also where the practical realities of hybrid work become visible.

The effectiveness of a hybrid model depends less on the policy itself than on how teams translate that policy into day-to-day operating practices.

This is where a structural gap often emerges. Most frameworks define broad principles — remote work eligibility, attendance expectations, managerial discretion, and the number of authorised remote days. Far fewer define how teams should coordinate collectively once work becomes distributed.

Coordination rarely breaks suddenly

One reason hybrid friction remains difficult to identify is that organisations rarely experience a visible breakdown.

Projects continue to move forward. Meetings continue to take place. Teams continue to deliver. From the outside, everything appears operational. What changes is more subtle.

Without explicit team-level norms, employees gradually develop different assumptions around availability, responsiveness, collaboration and presence. Initially, this flexibility often feels beneficial. Teams gain autonomy and individuals gain control over how they organise their work.

Over time, however, small differences in working patterns begin to accumulate. Information circulates unevenly. Context is repeated more often. Decisions take longer to converge because people are no longer operating within the same rhythm. Managers spend increasing amounts of time reconnecting conversations that have become fragmented across locations, schedules and channels.

Because this friction develops gradually rather than dramatically, many organisations underestimate it for years.

This helps explain why two companies with remarkably similar hybrid policies can experience very different outcomes.

The difference often lies less in the framework itself than in the quality of the operating model teams build within it

Hybrid work is not fundamentally a presence issue

Many organisations still approach hybrid work primarily through attendance management. Return-to-office mandates. Occupancy targets. Presence monitoring.

These mechanisms can influence behaviour. They are often easier to measure than coordination quality. But they only address part of the challenge.

The central question is not simply where people work. It is how teams coordinate when work is distributed across different locations, schedules and channels. That shift in perspective changes the leadership conversation considerably.

Research increasingly shows that attendance mandates can increase presence without necessarily improving collaboration. Some organisations with strict office requirements continue struggling with alignment and execution. Others achieve strong collective effectiveness while maintaining relatively high levels of flexibility. The difference is rarely attendance alone.

Teams derive value from co-presence when it is connected to specific outcomes: solving complex problems, accelerating decisions, onboarding new employees, strengthening social capital or rebuilding alignment after periods of fragmentation.

Without that intentionality, organisations can increase attendance without materially improving how work gets done.

The challenge is therefore less about maximising presence than about designing coordination deliberately.

The missing layer is team-level coordination

Between corporate policy and individual behaviour sits a layer that many organisations still underinvest in: team-level operating agreements.

Some organisations formalise these through collaboration charters or Team Agreements. Others rely on lighter frameworks adapted by managers and teams. The terminology matters less than the role they play. Their purpose is often misunderstood.

They are not primarily about deciding who comes to the office and when. They are about making explicit how a team operates collectively once work becomes distributed.

In practice, hybrid work introduces dozens of small coordination choices that many organisations leave implicit. Over time, those choices shape execution quality far more than the policy itself. The most effective teams tend to establish shared expectations around questions such as:

Taken individually, these may appear operational details. Collectively, they form the team’s operating model.

This is particularly important because distributed work increases the number of coordination interfaces. When expectations remain unclear, people create their own rules. Teams gradually develop parallel ways of working, information becomes harder to find, decisions become less visible and managers spend more time resolving avoidable friction.

By contrast, teams that clarify a limited set of shared practices often experience greater autonomy, not less. They spend less energy negotiating how to work and more energy focusing on the work itself.

One of the clearest lessons emerging from hybrid work maturity is that collective performance depends less on attendance volume than on the quality of the operating agreements that support everyday collaboration.

Most organisations invest more in flexibility infrastructure than coordination infrastructure

The AREMIS research reveals another interesting pattern. Most investments continue to focus on enabling flexibility rather than improving coordination

These figures point to a broader organisational mindset.

Hybrid work is still frequently managed as a workplace administration topic rather than as an operating model challenge.

As a result, organisations invest heavily in booking systems, workplace technology and occupancy management while dedicating far less attention to the mechanisms that help teams coordinate effectively.

Hybrid maturity increasingly depends on an organisation’s ability to orchestrate collective work intentionally, not simply to provide flexibility. That requires coordination infrastructure as much as flexibility infrastructure.

Effective hybrid models are co-designed, not simply imposed

Another assumption that continues to influence many organisations is the belief that hybrid coordination can be standardised centrally. In practice, operating realities vary significantly.

A highly interdependent project team does not coordinate work in the same way as an expert function with fewer dependencies. Some environments require dense collaboration rhythms. Others function effectively with far lighter synchronisation.

This is why the most successful organisations typically combine central structure with local adaptation. They establish a common framework while allowing teams to shape part of their operating practices according to their specific context. The benefits extend beyond coordination itself.

When teams participate in defining how they work together, expectations become clearer, ambiguity decreases and ownership tends to increase.

This matters because hybrid work remains a moving target. According to the AREMIS report, only one organisation in three currently considers its hybrid model both mature and stable. Most continue adjusting as behaviours, technologies and expectations evolve.

Hybrid coordination therefore cannot rely exclusively on static rules. It requires ongoing calibration.

The real shift is operational, not contractual

For several years, hybrid work has largely been framed as a flexibility issue.

Today, the more significant question is operational. The debate is gradually moving beyond: “How many days should employees be in the office?”

Toward a more fundamental challenge: “How should teams coordinate effectively when work is distributed?”

This is ultimately what distinguishes organisations that simply accommodate hybrid work from those that genuinely make it work.

Because hybrid models rarely fail because the policy is unclear. They struggle when too much of collective coordination remains implicit.

And once work becomes distributed, implicit coordination becomes increasingly difficult to sustain at scale.