What you share
Shared time is not shared work
Overlapping hours and attendance at the same meetings are necessary conditions for collaboration and are routinely mistaken for the thing itself.
The people this page is about, and which of them have ever worked together
- 01The team's managerEvery working pair in this grid includes this person
- 02The designer
- 03The data analyst
- 04The product managerWrites the brief everybody reads
four people · 6 possible pairs · 3 of them have worked on something together · 1 has only been in the same meeting · 2 have never done either
Four of the eight, and only the pairs that run between those four.
When the manager is the only route between people, the group can visit the product website and use project-level patterns to identify where direct collaboration would remove delay.
An independent source worth comparing with this example is TED.
Four rows from the same pyramid, chosen because the first two are the ones people mistake for the last two
The same company all-hands
8 of 8Everybody attends and nothing passes between any two of them
Any work at all in the last quarter with another member
7 of 8Everybody except the engineer who joined in March
A working day that overlaps by three hours or more
5 of 8Enough overlap to have an unscheduled conversation
Any such work with somebody other than the manager
2 of 8The two engineers, and nobody else
four things · the team is eight people · the widest is shared by eight, the narrowest by two · one of the four is true of all of them
Four of the nine rows counted on this site, drawn together so the gap between the first row and the last one is visible.
Two of the rows on the panel above are about being available at the same time. Two are about work. The first kind is true of five and eight people respectively. The second kind, in its strict form, is true of two.
That gap is the subject of this note, because the two kinds of row look alike on a pyramid and get treated as though they measured the same thing.
The necessary and the sufficient
Overlapping hours are a necessary condition for a certain kind of collaboration. Two people whose working days do not meet cannot have an unscheduled conversation, cannot solve something together in an afternoon, and cannot ask each other a quick question without a day's delay. Everything gets slower and some things become impossible.
So overlap matters, and a team with none has a real constraint. The error is reading the constraint backwards: concluding that because a team has overlap, it has the collaboration the overlap would permit.
Five of these eight share three hours or more. In those three hours they could do a great deal together. In the quarter counted, two of them did.
Why availability gets mistaken for connection
Because it is measurable, and because it is the thing that gets discussed.
Time zone overlap is the one structural fact about a distributed team that everybody knows. It appears in hiring decisions, in scheduling arguments, in the recurring debate about core hours. It is concrete, it is on everybody's calendar, and it is the thing people cite when asked whether a team can work together.
The pair count is not measured anywhere by default, so in the absence of it the overlap figure gets asked to carry the weight. A team with good overlap is described as well set up for collaboration, which is true in the sense that nothing is preventing it, and false in the sense anybody means it.
The same error with meetings
The all-hands row is true of all eight and is the clearest case. Every member attends. For an hour a week the entire team is in one place, synchronously, paying some degree of attention.
Nothing passes between any two of them. The transfer is one-to-many and back out again, which is the correct design for an announcement and produces no pairs at all. The note on the pair that only exists in a meeting goes through this in detail; the point here is only that attendance is the widest row on most pyramids and buys the least.
What to do with the overlap you have
The constraint is worth taking seriously in one direction: if the overlap is small, deliberate pairing has to be built differently.
- With three hours or more, the cheap mechanisms work. Two people can be given one task and left to find each other. A review can be sent and answered the same day. A problem can be looked at together.
- With one hour, the pairing has to be made asynchronous and explicit. The task has to be the kind that passes between two people in writing — a draft one of them extends, a decision one proposes and the other settles, a review with a day's turnaround. The pair forms more slowly and it does form.
- With none, the pairing has to be the whole point of the arrangement rather than a by-product. Nothing accidental will happen, so everything has to be set up: a specific handover at a specific boundary, somebody whose job includes being the one who writes things down for the other end of the day.
What the core-hours argument is really about
Most teams have had the argument about core hours at least once, and it is conducted as though the question were how much overlap is needed.
It is not. A team with six hours of overlap and no shared work gets nothing from the sixth hour, and a team with two hours and four live pairs uses both of them. The quantity only matters once there is something to spend it on.
So the useful version of the argument is not how many hours but which pairs need them. Two people with a real seam between them need an hour in common; six people who never interact do not need any, and requiring them to be awake together is a cost with no return.
The row worth adding
If the pyramid has an overlap row on it, add the strict pair row underneath — how many members have worked with somebody other than the manager — and look at the two together.
A team with wide overlap and a narrow pair row has the conditions and is not using them, which is the most fixable situation on this site. A team with narrow overlap and a comparable pair row is doing well under a real constraint, and the right move is probably to protect the hours it has rather than to arrange anything new.