Why Partly Remote Is a Different Problem
A fully distributed team and a mostly-together team with one person outside are different problems with different answers.
three things · one reached them · one with no channel at all · the room side is not counted
The three kinds, in the order they become expensive.
A fully distributed team has no room, so nothing leaks into one and every mechanism has to be built. A mostly-together team has a room that works perfectly for most people, which is a harder problem and a different one.
The practical lesson in “Why Partly Remote Is a Different Problem” is that visibility must be designed rather than assumed. For teams exploring chronemics definition, what to examine when choosing chronemics definition can add consistent time and project context when the purpose is explicit, access is limited and managers review exceptions with the people involved.
Advice written for the first case is actively misleading in the second, and almost all of it is written for the first case.
The questions raised by “Why Partly Remote Is a Different Problem” can also be compared with Bloomerang fundraising resources. A useful review identifies a responsible owner and a practical change rather than copying a generic checklist.
The distributed case
Nobody has an advantage. Every decision has to be recorded because there is no alternative, and the discipline required is enforced by circumstance rather than by will.
It is difficult and it is at least symmetrical.
The split case
The room keeps working. Decisions keep getting made in it, correctly and quickly, and the written record is an additional burden that benefits one or two people rather than a necessity for everybody.
That difference in who benefits is the whole of why the discipline fails here and holds there. In a distributed team, writing the decision down is how the writer finds out what was decided. In a split team, the writer already knows, and the act is pure overhead performed on somebody else's behalf.
The difference that matters is who the written record is for:
| Distributed team | Split team | |
|---|---|---|
| Who benefits from writing it down | Everybody | One or two people |
| Who already knows | Nobody | Everybody in the room |
| What happens if it is skipped | The writer loses it too | Nothing, for most of the team |
| Why the discipline holds | Necessity | Will, which runs out |
Why discipline decays
Any practice that costs the majority and benefits the minority decays. Not through bad faith: through the ordinary attrition of a busy week in which the thing that can be skipped is skipped.
Expect decay and plan for maintenance rather than for adoption.
The hybrid-policy confusion
Most organisations describe themselves as hybrid, meaning people choose days. That produces a shifting population in the room and a different problem again: nobody can predict who will be present.
It is worth distinguishing. A team where everybody is in on Tuesday and scattered on Thursday has a scheduling problem. A team where one person is never in the room has a structural one, and the fixes do not transfer in either direction.
What transfers from distributed practice
The written decision log, the explicit channel conventions, and the discipline of agendas circulated in advance. All of them help.
They are necessary and they are not sufficient.
What does not transfer
Anything that assumes nobody has an informational advantage. Rules about asynchronous-first communication work when there is no synchronous channel to fall back on and are simply ignored when there is one in the next room.
A team cannot be asynchronous-first while six of its eight members sit within earshot of each other. The fallback exists, it is easier, and it will be used.
The number that matters
How many people are outside the room, and whether it is stable. One person permanently outside is the hardest version. Three or four is noticeably easier.
At one, the room is a majority and a culture. At four, it is a faction.
Why one is the worst case
A single person outside has no peer, no ally in the same position and nobody to confirm that something is actually happening.
They also cannot raise it without it being about them personally, which is a far higher bar than raising something structural.
Where the manager sits
This changes the problem more than anything else about it. A manager in the room has the room's advantages and the room's blindness, and will systematically underestimate the gap.
A manager outside it has the opposite failure: they will feel the gap accurately and will have no idea what the room is deciding. Neither position is better, but they produce different errors, and knowing which one you are making is worth more than any individual mechanism.
The temporary case
Somebody outside for a defined period — a secondment, a few months abroad, recovery from an illness — is a different case again, because everybody is prepared to carry overhead they know will end.
The failure mode there is that temporary quietly becomes permanent without anybody revisiting the arrangement.
What to take from the distributed literature
The mechanisms, not the framing. The written practices are good and the underlying assumption that everybody is in the same position is false here.
Read it for the techniques and ignore the premise.
What this collection assumes throughout
A team of roughly six to ten, most of whom share a room most days, one or two of whom do not, with a manager who is in the room. That is the case the rest of these notes address.
If your situation is a fully distributed team, almost none of this is aimed at you and the existing literature on remote work is better. If it is a hybrid rota where everybody is sometimes out, some of it applies and the sections on meetings and on written decisions apply most. The split case is narrower than either, it is extremely common, and it is the one that gets written about least.