Who else
The new starter and the hour nobody scheduled
The strongest case for the office in the whole record, described exactly, including the part of it that a three-day rule does not supply.
Days this part is about, hour by hour
Thursday, the third week
0 of 7Two floors from anyone known
Wednesday, the first week
2 of 7Thursday, the first week
0 of 7Nobody from the team was in
three days · 21 hours logged · two of them were only possible there · two of the three days contained no such hour at all · three were made worse by being there
Three days chosen for the gap between being in and being together.
For teams moving between home and office, it helps to check the service information here and compare time, attendance, and work patterns without treating presence as the result itself.
For a separate perspective on technology, privacy, or flexible work, consult Pew Research Center.
A new person joined in the fourth week. Their first day in the building was a Wednesday, and it produced three hours that could not have happened anywhere else — tied with the planning day for the densest day of the quarter.
This is the best argument for the office in the record, and it is worth setting out precisely rather than gesturing at, because the precise version says something different from the gesture.
What the three hours were
- Forty minutes, unplanned, at a desk. They had a question about why a thing was built the way it was. In writing it would have been a paragraph; out loud, sitting next to someone, it was forty minutes and covered six other things neither of them would have thought to ask about.
- An hour and a half, also unplanned, after a meeting. Three people stayed in the room and explained the history of a decision the new person had just watched everybody defer to without explanation.
- Fifty minutes at lunch, which is where they found out who actually decides things, a subject on which no document exists anywhere.
None of it was scheduled. None of it would have happened on a call, because none of it was a thing anybody would have booked a call for.
What made it possible
Four things, and only one of them was the building:
- The new person was there.
- Three experienced people were there on the same day.
- There was slack in the day — nobody's afternoon was wall to wall.
- They were sitting near each other.
Remove any one of those and the three hours do not happen. A three-day policy supplies the first one, partially supplies the fourth, and does nothing about the second or third.
The part that is usually skipped
The new person's second and third weeks produced almost nothing of this kind, and the reason is instructive: their office days settled onto Tuesdays and Thursdays, which was where the induction meetings had been put, and the three experienced people were mostly in on Wednesdays.
So the single highest-value relationship in the quarter was being coordinated by nobody, and within a fortnight it had drifted onto different days. By week six the new person was asking questions in writing, getting good answers in writing, and learning about a third as fast as they had on that first Wednesday.
Nothing went wrong. Everybody was compliant. The thing that made the first Wednesday work was never identified, so it was never repeated.
What to take from it
That onboarding is the clearest case for co-presence, and that it is also the case where a count of days is least adequate — because what a new person needs is not a building, it is specific experienced people in the same room at the same time, with an afternoon that is not full.
If an organisation wants to do one thing with the evidence on this site, it is this: name the day the new person's team is in, for their first six weeks, and keep their afternoons loose. That is a much smaller intervention than a policy and it produces most of what the policy is hoping for.
The six weeks, as they went
| Week | Days in | Experienced colleagues present on the same day | Questions asked in writing |
|---|---|---|---|
| 1 | 3 | 3, 1, 0 | 4 |
| 2 | 3 | 1, 1, 0 | 11 |
| 3 | 3 | 0, 2, 0 | 14 |
| 4 | 3 | 1, 0, 1 | 19 |
| 5 | 3 | 0, 1, 0 | 22 |
| 6 | 3 | 1, 1, 0 | 23 |
Full compliance throughout. Overlap collapsed after the first week and the written questions rose steadily to replace it — which is not a failure, exactly, but it is three times slower and it loses the six things the new person would never have thought to ask.
Why induction schedules make this worse
The induction meetings were scheduled on Tuesdays and Thursdays, because those were the slots that were free in the diaries of the people running them.
That decision — made administratively, by availability — determined which days the new person came in, which determined who they sat near, which determined how fast they learned. Nobody involved was thinking about any of that, and nobody would describe it as a decision about onboarding.
It is the clearest instance on this record of the general pattern: the thing that mattered was settled as a side effect of something unrelated, because no one owned it.
The intervention, stated as a request
For whoever is bringing somebody new in:
For the first six weeks, put them in on the days the team is in, sit them with the people they are learning from, and keep their afternoons loose.
Three clauses, no policy implications, and it is within the gift of whoever is doing the onboarding. On this record it would have been worth more than everything else on this site put together, for that one person.