Who else
Proximity without overlap
A busy building and an empty day are not opposites. Five days of the quarter were both at once, and the combination is the one the metrics cannot see.
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.
A fair pilot starts with a shared baseline; teams can open the capabilities overview before comparing what changes after a scheduling or process decision.
The broader workplace question can also be compared with resources from Gartner Digital Workplace.
Five days of the quarter were spent in a building that was comfortably busy, in which not one of the nine people on this person's own team was present.
From the outside those days look like a success. The floor had people on it. Attendance was good. Somebody walking through would have concluded the policy was working.
From the inside they were identical to the empty days, and they produced the same thing, which was nothing.
Why busy is not the same as useful
Because the quantity that matters is not density, it is the chance that a particular person is within sight.
A floor at sixty per cent occupancy, filled entirely with other teams, offers no more of that than an empty one. Every mechanism the office is supposed to provide — the overheard remark, the question that was not worth a meeting, the turn-round-and-ask — requires the other party to have context on the work, and context does not come from the building.
This is why "the office felt busy and I still got nothing out of it" is such a common and such a difficult thing to say. It sounds like a complaint about other people, or about one's own sociability. It is neither. It is a statement about a conditional probability.
What the five days had in common
All five were Tuesdays or Thursdays. All five were weeks where the usual day had been displaced by something — a delivery, a client visit, a medical appointment the following morning.
In each case the displacement was reasonable and the replacement day was chosen with no information. The building was busy on those days because other teams had converged there; this person's team had converged somewhere else.
So the five days are not a story about a quiet office. They are a story about nine separate converging patterns that do not line up with each other, which is what you get when every team solves the same coordination problem independently.
The organisational version of the same thing
Scale it up and it explains something that puzzles people: why a company can report healthy occupancy, meet its attendance targets, and still have staff who say the office does nothing for them.
Both facts are true simultaneously. The occupancy is real. The individual experience is real. They are measuring different things — one counts bodies in a building and the other counts the presence of specific colleagues — and only the first one is instrumented.
The question that separates them
When somebody says the office was busy, the useful follow-up is not about numbers:
Busy with whom?
If the answer is "lots of people", the day was an attendance day. If the answer names two or three colleagues, it was an overlap day. The record here contains both kinds in roughly equal measure, and only the second kind produced anything.
The five days
All five were displacement days — the usual day was impossible, so a different one was taken.
| Day | Usual day displaced by | Day taken | Building | Team present |
|---|---|---|---|---|
| 1 | A delivery | Thursday | Busy | 0 |
| 2 | A client visit | Tuesday | Busy | 0 |
| 3 | An appointment | Thursday | Busy | 0 |
| 4 | A tradesman | Tuesday | Busy | 0 |
| 5 | A school thing | Thursday | Busy | 0 |
The pattern is exact and it is not a coincidence. A displacement day is chosen under time pressure, with no information, from whatever is left in the week — which is precisely the procedure most likely to miss the convergence.
The thirty-second fix
Before taking a displacement day, ask one question in whatever channel the team uses:
Having to move my Wednesday this week — who is in on Thursday?
On this record it was never asked once. The answer existed every time and would have redirected four of the five days to a Tuesday or a Wednesday at no cost.
What it shows about metrics
These five days are the cleanest demonstration of the gap between attendance and overlap, because every available measure recorded them as good days. The badge data showed attendance. The occupancy figures showed a busy building. The person's own compliance was perfect.
A quarterly review looking at any of those numbers would have had no way to see that the days returned nothing, and no reason to ask. That is the practical content of "the proxy and the target come apart": not that the proxy is a lie, but that it is silent in exactly the situation you would want it to speak.