Skip to content
Body of Knowledge · Cross-cutting chapter

Distributed and Hybrid Work

Not a competency: the conditions under which most of the competencies are now exercised, and how to engineer against the tilt toward the centre.

6 min read · updated 2026-10-08

Why a chapter rather than a competency

Distributed and hybrid work is not a competency. A manager is not examined on it directly, and no question asks whether remote work is good. It is a condition under which most of the twenty-nine competencies are now exercised, and it pushes several of them the same way. Information arrives later and more filtered. Effort and contribution are harder to see. The boundary between work and the rest of life is thinner. Opportunity flows toward the centre unless something stops it. And the signals a manager relies on, such as the mood in the room or the question asked in a corridor, arrive faintly or not at all. This chapter states those changes once, so the competencies they affect can point here instead of each restating them. Those that point here most are CC-4 Motivation, recognition, and sustainable pace (motivation, recognition and pace), CC-3 Inclusive practices and equitable opportunity distribution (equitable opportunity), PL-5 Career development and growth paths (one-on-ones and growth), PL-2 Feedback and difficult conversations (feedback and the reaction to bad news), DE-5 Designing how work flows (how work flows) and SV-6 Organisational design and leading change (organisational design).

The default gradient

Left alone, a distributed organisation tilts toward wherever the decision-makers sit. Decisions are made in the meetings the centre can attend and information moves in the corridors the centre walks. The stretch work goes to the people the leader sees, and promotions follow. Nobody has to intend any of this, which is why reminders to include remote colleagues achieve nothing. A reminder does not counteract a gradient. Each design principle in this chapter is a way of engineering against the tilt, and each failure it describes is a way of leaving the tilt in place.

The gradient has been measured. In the randomised experiment reported in Nicholas Bloom, James Liang, John Roberts and Zhichun Jenny Ying, Does Working from Home Work? Evidence from a Chinese Experiment (2015), employees assigned to work from home were more productive and reported higher satisfaction than office-based colleagues doing the same job, yet they were promoted less often. Being out of sight took them out of the opportunity flow, even when they performed better. A later randomised trial, Nicholas Bloom, Ruobing Han and James Liang, Hybrid Working from Home Improves Retention without Damaging Performance (2024), tested a hybrid arrangement of two days at home and found no loss of performance or promotion, along with a substantial improvement in retention. Taken together, the two studies tell a manager what they need to know. The tilt is real and costs the organisation talent. It also comes from how the arrangement is designed and is no law of nature: the hybrid design that kept people visible did not produce the penalty.

What changes, competency by competency

Information latency and filtering. A manager who used to hear about a problem the day it happened now hears about it in the next written update, after the person has decided how to present it. The instruments of PL-2 Feedback and difficult conversations and PL-6 Leading through leaders (skip-levels for signal, direct observation of artifacts, a visible reaction to bad news) matter more. The written record matters most. A distributed team runs on what is written, and a decision that lives only in a call was made without the half of the team that was not on it.

Visibility of effort and contribution. In an office, effort is seen. In a distributed team it has to be inferred from output, which favours the visible kinds of work and the people who narrate their own. Under CC-4 Motivation, recognition, and sustainable pace the manager has to go looking for what deserves recognition, since it will not be noticed in passing, and under CC-3 Inclusive practices and equitable opportunity distribution the opportunity ledger has to be kept by site, because the pattern will not show itself.

The boundary between work and life. When the desk is at home, the working day has no natural end, and a manager's late-evening message reads as an expectation. Sustainable pace under CC-4 Motivation, recognition, and sustainable pace and the manager's own boundaries under CC-6 Self-management become harder to hold and matter more, because the team takes its norm from what the manager visibly does.

The signals of disengagement. PL-5 Career development and growth paths treats withdrawal, cynicism and a halt in the flow of ideas as early signals of attrition, and across a video call they arrive later and fainter. The one-on-one is the instrument. The pattern shows up in the manager's notes across several of them.

Decision-making. A decision made in a meeting that one location cannot attend is a decision made for that location. The flow of work under DE-5 Designing how work flows and the structure under SV-6 Organisational design and leading change have to be designed so that decisions are location-neutral: made in writing, or in meetings every location can attend, and then published.

Onboarding. A new hire in an office absorbs context by proximity. A new hire at a distance absorbs what is written down and what a named guide tells them. For distributed hires the first-quarter plan under PL-3 Hiring and onboarding is mandatory, and the department baseline under CC-3 Inclusive practices and equitable opportunity distribution keeps the quality of onboarding from depending on which team someone happens to join.

Design principles

Engineering against the gradient looks like the principles below. They are written as design decisions because that is what they are. An attitude will not hold against a tilt.

  1. Written first. Decisions, context and status are written down and published where every location can read them, and the written record is the canonical one. A meeting may come before the decision, but it does not replace the record.
  2. Location-neutral decision-making. Anything that affects more than one location is decided by a process every location can take part in on equal terms: a proposal with a comment window, or a meeting at an hour every location can attend, recorded and summarised.
  3. Opportunity tracked by site. The stretch work, the visible work, the strategic project and the promotions are counted by location as well as by person, and the pattern is corrected before it hardens.
  4. Rituals that work in every time zone. Shared rituals are designed for the whole organisation instead of being run by one office and streamed to the rest. If one location experiences a ritual as a party and another as a broadcast, it is a belonging failure presented as a belonging initiative.
  5. Leaders assessed on their remote members' experience. A manager with distributed reports is measured partly by asking those reports about their experience, because the default gradient favours the centre and the leader usually sits there.
  6. The manager's own boundary, visibly kept. Messages go out in working hours, holidays are not interrupted, and the working day ends. The team learns its norm from what the manager does.
  7. Deliberate in-person time. Where an organisation can bring distributed people together, it does so on purpose. The time goes on building relationships and having the hard conversations that a call handles badly. Status updates, which a document handles better, are a poor use of it.

Reading the scope tags in a distributed organisation

The scope tags ([team], [org], [exec]) apply unchanged. Distributed work widens the gap between scopes. How Judgment Scales describes information latency as growing with scope, and it grows faster when the layers also sit in different places, so the executive's structured sensing has to reach further. A manager of managers with teams in three cities is in effect working at slightly higher scope than the same manager with three teams along one corridor, and should read the [org] items with that in mind.

What does not change

The competencies themselves stay the same. A difficult conversation is still difficult over video, and a manager who defers it because the medium is awkward has still deferred it. Feedback is still specific, timely and anchored in behaviour. The intervention threshold is the same. The culture is still set in the costly moment, which people watch as closely on a screen as in a room. This chapter describes conditions. None of them is an exemption.