The hours
A day that repaid the journey
The densest day of the quarter, hour by hour, and the four things that made it different from the thirty-three others.
Days this part is about, hour by hour
Wednesday, the second week
3 of 7Planning day, the densest of the quarter
Thursday, the third week
0 of 7Seven hours of solo work at a hot desk
Wednesday, the fourth week
3 of 7The new starter's first day in the building
three days · 21 hours logged · six of them were only possible there · one of the three days contained no such hour at all · two were made worse by being there
Three of the twelve days drawn in full on this site.
When a hybrid policy measures attendance but not outcomes, workforce optimization software can add project-time and workload evidence to a more useful conversation about what different locations enable.
For a separate perspective on technology, privacy, or flexible work, consult UNESCO AI.
The planning day, hour by hour
Wednesday, the second week
3 of 7Three hours at a board, two hours of conversation that would have worked on a call and worked better in a room, two hours of writing up
one day · 7 hours logged · three of them were only possible there
One day of the thirty-four.
A good day deserves setting out at length. Almost everything written about this subject dwells on the failures, which leaves the successful version standing as an assertion nobody has unpacked.
Wednesday of the second week. Seven working hours. Three of them could only have happened in the building, two were better for it, two were indifferent, and none were worse. It was the best day of the quarter by a distance, and it is the only day that produced three consecutive hours of the first kind.
The day
- 09:00–12:00. Quarterly planning at a board. Eight people, a wall, and four hours of argument compressed into three because everybody could see the same thing at the same time and point at it.
- 12:00–13:00. Lunch with the same eight. Counted as
n, because it could not have happened anywhere else, and it is where two of the afternoon's decisions were actually settled. - 13:00–14:00. A conversation with the person who had the objection, walking to the coffee place and back. Possible on a call. Better not on one.
- 14:00–16:00. Writing the outcome up. Indifferent to location.
- 16:00–17:00. Catching three people in turn for thirty seconds each, which on any other configuration would have been three messages and two days.
The four things that made it work
Everybody was there. Eight of nine. That was not luck; the date had been fixed a month earlier and the purpose was known.
There was something to stand in front of. A wall, and a disagreement with a shape. Half the value of the first three hours was that eight people were looking at the same object.
The day was built around the thing that needed the building. The solo work was put in the afternoon, after, rather than scattered through.
Nobody had to find a room. It was booked a month out, so none of the day was spent in a corridor.
What it did not require
It did not require a policy. The planning day would have happened if attendance had been entirely voluntary; everybody would have come, because the reason to come was obvious and stated.
That is the uncomfortable observation. The single best day of the quarter owed nothing to the three-day rule. It was produced by a named purpose, a fixed date and a booked room — three things any team can arrange, and none of which a count of days supplies.
How often this is available
Not every week, and pretending otherwise is how the argument goes wrong. Quarterly planning is quarterly. The new starter arrives once. A wall-sized disagreement turns up when it turns up.
A reasonable estimate from this record is one day a fortnight that genuinely earns a full room, and perhaps one day a week that earns two or three people being in at the same time. Thirty-nine required days a quarter is a long way from either, and the gap is where the other thirty-three days went.
What it cost to arrange
Worth stating, because the implication of a good day is usually that good days are hard to produce, and this one was not.
The date was fixed a month ahead in a single message. The room was booked at the same time. The purpose was stated in one sentence in the invitation, which is why everybody knew what the day was for and arranged their own work around it.
Total effort: one message, one booking, one sentence. That is the entire difference between the best day of the quarter and the fifteen that returned nothing.
The comparison that makes the point
| The planning day | A typical office day | |
|---|---|---|
| Decided | A month ahead | The evening before, or not at all |
| Purpose | Stated in the invitation | None |
| People present | Eight of nine | Median three of nine |
| Room | Booked a month out | Not attempted |
| Hours that needed the building | 3 | 0 or 1 |
| Journey | Identical | Identical |
Every row except the last two is something a team can change by itself.
Why this does not happen more often
Not because nobody wants it. Because arranging a day like this requires somebody to decide that the day is for something, and under a count of days there is no natural moment at which anybody does that.
The policy supplies the attendance, so the question "why are we in on Wednesday" has an answer already — because it is Wednesday — and the better answer never gets constructed. Paradoxically, a team with no attendance policy at all is more likely to arrange a day like this, because the only way to get anybody into a building is to give them a reason.