The week
The cost of choosing the wrong day
Two people, identical compliance, identical travel, and a fourfold difference in what the quarter returned. The variable is which weekday, and nobody is tracking it.
Days this part is about, hour by hour
Monday, the third week
0 of 7Came in to make up a missed day
Tuesday, the fourth 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
Two days from the quieter end of the week, and one from the full end.
Before adding another fixed office day, teams can view its reporting options to check whether capacity, coordination, or project design is the real constraint.
An independent source worth checking for this subject is Google Workspace Blog.
Consider two people on the same team under the same three-day rule, both fully compliant, both with the same hour-and-five-minute journey.
One is in on Tuesday, Wednesday and Thursday. The other is in on Monday, Wednesday and Friday — because of a standing Tuesday commitment and a Thursday that never worked out.
Both travel the same distance the same number of times. Using the weekday rates from the record here, the first person's days fall where roughly one hour in six needed the building. The second person's fall where it is closer to one in twenty.
Same policy. Same cost. Four times the return for one of them, and nothing anywhere in the system registers the difference.
What the gap is made of
It is made entirely of other people's choices. Neither person has done anything differently in terms of effort, attitude or diligence. The first one picked the days the rest of the team happened to converge on; the second picked days that the rest of the team had drifted away from.
The second person is not getting a diluted version of the office. On the thin days of this record — Monday and Friday together — the hours that required the building came to zero across the quarter. Not fewer. None.
Why nobody notices
Three reasons.
- The policy measures days, and the days are identical. Three and three. Every reporting system that exists will show these two people as the same.
- The experience is not comparable from the inside. Neither person sees the other's quarter. The second one has a vague sense that the office is quieter than people say, which they are likely to read as a fact about the office rather than about their own schedule.
- It cannot be raised without sounding like a complaint about colleagues. "The people I need are never in when I am" is true, unanswerable and socially expensive to say.
What it does over a year
The compounding is the part that matters. The second person has fewer unscheduled conversations, so fewer small pieces of context, so more surprises later, so more rework. They are seen less often by people who make decisions about work allocation. And because the office returns them very little, they come to regard the requirement as pure cost, which it very nearly is for them.
None of that shows up as a performance issue, and all of it is produced by a weekday.
The cheap correction
The correction is not an exception and not a reduction. It is information, and it costs one message:
Who is in on which days?
A shared answer to that question — a calendar, a channel, a line in a weekly note — lets the second person move one of their three days and collect most of the difference. On this record nobody ever asked it, and the information existed the whole time in nine separate heads.
The two quarters, side by side
| Converged schedule | Displaced schedule | |
|---|---|---|
| Days in the building | 34 | 34 |
| Travel | 73h 40m | 73h 40m |
| Colleagues present, median | 5 of 9 | 1 of 9 |
| Hours that needed the building | ~29 | ~7 |
| Rooms obtainable | Rarely | Usually |
| Recorded compliance | 93% | 93% |
Every row that a system records is identical. Every row that matters is not.
What it does to the person at the thin end
Beyond the obvious, three effects compound over a year.
Context arrives late. The unscheduled hour is where most small pieces of context travel. Without it, the same information arrives weeks later, formally, usually after a decision has already been made on the basis of it.
Work allocation drifts. Not through favouritism. Work tends to go to whoever was in the room when it came up, and on this record eleven of the thirty-one valuable hours were exactly that: conversations in which something got decided and someone picked it up.
The policy becomes pure cost. Somebody whose office days reliably return nothing will come to regard the requirement as an imposition, because for them it is one. They are then liable to be read as having an attitude problem, when what they have is a weekday problem.
The sentence to use
I am in Tuesday, Wednesday, Thursday. Most of the people I work with are in Tuesday and Wednesday. Could I move the Thursday to a Monday — same three days?
It names a fact, proposes a change that costs nothing, and does not mention the policy. On this record it would have recovered most of the gap.