Hybrid Work Is a Mandate Problem

The mixed experience of hybrid work does not prove that office is better or remote is better. It suggests something more useful: people, teams, and departments need enough mandate to shape working conditions around the work they are actually doing.

The hybrid work debate keeps returning to the same question: is remote work better, or is office work better?

It is a tempting question because it looks answerable. It can be turned into a policy, a number of days, a rule. It gives leaders something concrete to decide and something concrete to communicate.

But it is too blunt for the work it is trying to govern.

Work comes with different demands. Some of it depends on shared sense-making, fast coordination, or being in the same room. Some of it depends on deep concentration, low interruption, and enough quiet to think.

So when the evidence and experience around hybrid work seem mixed, that may not only be a problem with the data. It may be a problem with the question.

The better question is not whether remote or office is better.

The better question is what kind of work we are talking about, what conditions that work depends on, and who is close enough to the work to judge that well.

That is where mandate enters.

If the work differs, and the people differ, and the team dynamics differ, one central rule will often be too crude to create the best outcome. It may be easy to administer. It may look fair. It may give senior leaders a sense of control.

But it may still be the wrong level of decision.

Hybrid work is not only a location problem.

It is a mandate problem.

What Flexibility Revealed

Flexibility revealed something many organizations had not wanted to look at too closely.

The modern office was not only a place of collaboration, culture, and belonging. It was also a place of noise, interruption, commuting cost, social performance, context switching, weak meeting discipline, and constant availability.

For some people, that cost was tolerable. For others, it was expensive. It showed up as the daily friction of trying to do thoughtful work in conditions that made focus harder than it needed to be.

For some people, remote work did not make them less engaged. It made work less exhausting. It gave them more control over attention, fewer interruptions, less time lost to commuting, and less need to perform availability as a signal of commitment.

This does not mean remote work is better for everyone.

Some people lost energy, rhythm, and connection. Some teams became slower. New employees sometimes had a harder time learning the informal reality of the organization. Some conversations became harder to start. Collaboration sometimes became more scheduled, more transactional, and less alive.

This duality is not a contradiction. It is the point.

Flexibility did not prove that home is better than the office. It proved that the old default had been carrying more hidden cost than many organizations wanted to admit.

It also showed that different work and different people need different conditions.

That should have made the conversation more precise.

Instead, many organizations turned it back into a location debate.

What Return-to-Office Gets Wrong

Return-to-office policies are often presented as practical responses to real concerns. Collaboration has become harder. Culture feels thinner. New employees need onboarding. Managers struggle to see what is happening. Some people are isolated. Some teams are drifting. Some work probably does need more shared time.

These concerns are not imaginary.

The mistake is assuming that office presence solves them by default.

Presence can help. Proximity can matter. Difficult trade-offs, creative problem-solving, onboarding, conflict repair, relationship-building, and shared sense-making can all benefit from being in the same room.

But presence is not the same as collaboration.

It is not the same as trust.

It is not the same as clarity.

It is not the same as leadership.

A blanket policy may be administratively clean, but operationally crude. It treats different work as if it has the same needs. It treats different teams as if they have the same maturity. It treats different departments as if they have the same constraints. And it often treats presence as a substitute for the harder work of understanding what is actually broken.

Poor collaboration may need more shared time, but it may also need clearer purpose, better facilitation, better decision rights, fewer handovers, stronger relationships, or more deliberate shared work. Weak culture will not be fixed by attendance alone. Unclear productivity will not be solved by visibility if goals, measures, feedback loops, and the definition of valuable work remain vague.

When organizations use office policy to compensate for weak leadership conditions, they may increase presence without improving work. They may get more people in the building, but not necessarily more clarity, trust, judgment, ownership, or focus.

The Conditions Hybrid Exposed

Hybrid work did not create the leadership problem. It exposed the conditions leaders had, or had not, built.

In an office, proximity can cover for a surprising amount. People overhear signals, ask quick questions, notice who is worried, and adjust informally. Some of that is useful. But it can also hide weak clarity, low trust, unclear mandate, and poor decision habits.

When work becomes more distributed, those informal patches weaken.

If direction is unclear, people have fewer background signals to lean on. If trust is low, absence becomes suspicious. If mandate is weak, decisions still climb the hierarchy, only now through more meetings, messages, and coordination. And if psychological safety is weak, silence becomes easier. Doubts stay private. Problems hide behind screens. People can appear aligned while holding back what the organization most needs to know.

That is why hybrid work is such a useful diagnostic.

It reveals whether people know what matters without sitting near the same signals. It reveals whether leaders trust judgment when they cannot observe activity. It reveals whether teams have enough mandate to shape collaboration around the work. And it reveals whether the organization has built enough safety for problems to surface before they become expensive.

The problem is not simply where people work.

The problem is whether the organization has created the conditions for good work to happen without relying on proximity to compensate for what is missing.

Mandate at the Right Level

The answer is not unlimited freedom. That is not mandate. That is drift.

The better answer is governed mandate.

Senior leaders should set the broad principles. They should be clear about what the organization is trying to improve, what constraints matter, what customers need, what risks must be managed, and what kind of culture they are trying to build.

But they should be careful about turning all of that into a uniform attendance rule.

The judgment often belongs closer to the work.

People often understand a great deal about the conditions under which they do good work. Teams understand the rhythm of their collaboration better than a central policy can. Departments face different realities: sales, product, engineering, support, operations, finance, HR, legal, and leadership do not all have the same dependencies, confidentiality needs, customer interfaces, or decision cycles.

A single rule can easily flatten all of that.

It may feel decisive. It may look fair. But it can remove exactly the kind of judgment the organization needs.

That is the irony.

Many companies say they want accountability, ownership, and leadership close to the work. Then they remove mandate from the people closest to the work when deciding how the work should happen.

If managers are responsible for outcomes but not trusted to shape working conditions, the mandate problem has simply moved up a level.

They become enforcers of policy rather than leaders of work.

That is unlikely to strengthen engagement.

Especially in a period when engagement is already under pressure, with Gallup’s latest global workplace data suggesting that managers carry much of the recent decline.

Start With the Work

A better hybrid approach does not start with days.

It starts with the work.

Focus work needs different conditions from relationship work. Coordination work needs different conditions from creative discovery. Onboarding needs different conditions from mature delivery. Conflict repair needs different conditions from individual analysis. Some work needs physical presence because the customer, equipment, risk, or context requires it. Some work needs quiet, writing, reflection, and fewer interruptions.

Once that is clear, the location question becomes more useful.

Office time can be used deliberately for the work that benefits from being together: difficult trade-offs, creative problem-solving, onboarding, relationship-building, conflict repair, planning under uncertainty, and shared sense-making.

Remote time can be protected for work that benefits from concentration, writing, analysis, individual production, reflection, and fewer interruptions.

Team agreements can make collaboration explicit rather than accidental. Department-level principles can account for different work realities. Company-level principles can set fairness, direction, and boundaries without pretending every team has the same needs.

This is not less leadership. It is more deliberate leadership.

It requires leaders to understand the work well enough to avoid lazy uniformity. It requires managers to lead through clarity, trust, and mandate rather than proximity alone. It requires teams to be honest about what is working, what is not, and what the work actually needs.

What the Policy Teaches

Every hybrid policy teaches something.

A flexible policy can teach trust, but it can also teach fragmentation if the work is not designed well. A strict office policy can teach commitment, but it can also teach compliance if people do not understand the reason. A team-based policy can teach ownership, but it can also create unfairness if principles and boundaries are unclear.

There is no risk-free answer.

That is why the question cannot simply be office or remote. The question is what the policy teaches people about the organization.

Whether judgment is trusted.

Whether visibility matters more than contribution.

Whether teams are expected to design work deliberately, or merely comply.

Whether leaders understand the work, or are solving discomfort with attendance.

This is where hybrid work connects to the long game.

A policy designed mainly to create control may solve some short-term discomfort. But it can also weaken trust, reduce mandate, and make capable people feel less responsible for shaping the work.

A policy designed around mandate is harder. It requires clearer principles, better conversations, stronger managers, and more honest review of what actually works.

But it is more likely to build an organization that can keep adapting.

Not because everyone gets what they want.

But because the organization learns to place judgment where the work can actually be understood.

The Real Test

Hybrid work did not only test where people should work.

It tested whether organizations trust judgment close to the work.

That is probably why the debate has become so charged. It is not only about commute time, office space, or calendar rules. It is about what people believe the organization believes about them.

Underneath the policies, people are reading a simpler message: whether they are trusted, whether outcomes matter more than visibility, whether managers are allowed to lead, and whether teams are allowed to shape collaboration around the work rather than simply comply with a policy.

If the response to hybrid complexity is to remove judgment from the people closest to the work, the organization has not solved the problem.

It has revealed it.

Part of the wider thread: this piece applies ideas from Leaders Create the Environment and Playing the Long Game to the current hybrid work debate.