Hybrid work — what high-performing hybrid teams do differently [Part 2 of 4]

Part 2 of 4 — Hybrid Work That Actually Works

Last week's issue outlined the problem: Most hybrid models fail because they were designed around attendance, not outcomes. They were built as an uneasy compromise between the remnants of the remote era of the pandemic and nostalgia for the traditional office setup. They inherited the friction from both without the clarity of either.

That framing begs a deeper question:. If the issue lies with the operating model, what does a good model look like in practice? 

Specifically: what do the organisations that make hybrid stick do differently at the culture and policy layer; before the tech hype, before management training, before anything is measured?

That's what this issue covers.

The policy gap is a decision architecture gap

The most common misconception about hybrid policy failure is that the policy is to blame. It usually isn't. Most hybrid frameworks are detailed, well-intentioned, and genuinely flexible. The problem is structural: many hybrid policies specify where people work, not how decisions get made.

This distinction matters more than it might initially appear. When a policy outlines attendance rules but leaves out communication norms, teams default to the behaviours they already know. Synchronous meetings fill the gap where async decisions should be. Presence becomes a proxy for contribution because there's no agreed alternative. The policy says 'flexible'; the culture says 'show up'.

Research consistently confirms this pattern. A study found that nearly half of employees don't fully understand their organisation's hybrid work plan, largely because these plans lack documented communication norms. The policy exists. The decision architecture doesn't.

High-performing hybrid teams tend to solve this, not through longer policies, but through explicit protocols: a written decision framework that specifies which categories of decisions are asynchronous by default, which require synchronous alignment, and who has authority to call which. It sounds procedural. In practice, it removes the single biggest source of drift; the moment where someone defaults to a meeting because nothing else was agreed.

The management layer is where culture lives

If decision architecture is the structural fix, the management layer is where culture either holds or breaks. And this is where the evidence points.

Gartner found that 75% of HR leaders recognise that managers are overwhelmed. Managers in hybrid organisations have increased responsibilities: They are expected to bridge senior leadership mandates and employee expectations, manage performance across locations, maintain team cohesion without physical proximity, and do all of this while their own working patterns are also in flux. 

The result is predictable. Under pressure, managers revert to the behaviours that got them promoted: visible output, fast responses, physical presence rewarded because it's easiest to observe. Not because they're resistant to change. Because the incentive structure hasn't changed, and they're operating at capacity.

Companies that navigate this successfully address the incentive structure before they address the skill set. This means removing office attendance from performance criteria altogether; not just addressing the language of the policy language, but how managers are evaluated. 

It also means recognising managers who build high-performing distributed teams. Training and development automatically follow. But training delivered without regard for the incentive structure is just performative, not cultural change.

What the policy layer has to achieve

Hybrid culture doesn't set itself. Teams that get this right treat the culture and policy layer as part of the infrastructure, not as a document to produce and file.

This means three aspects working in concert. 

First, documented communication norms, providing explicit guidance on which channels carry which kinds of information, with an expectation that decisions don't always require a meeting. 

Second, performance frameworks that favour outcomes over activity, with managers accountable for team output, not attendance management. 

Third, and often underestimated, a shared language for the model itself. What 'hybrid' actually means, what flexibility it allows, and what the team does when the norms get tested.

Most of this information can be captured in fewer than ten pages. The gap isn't in knowledge; it's recognising that culture is a design issue, not a communication issue.

Next week, part three turns to the technology and tooling layer: Why most organisations are running the right tools on the wrong logic, and what it takes to change that.

Digital Working is published every Wednesday. Share this with a colleague navigating a hybrid transition.