Skip to content
Came In For This All fifty notes

The week

Anchor days and what they actually fix

Naming one day solves a coordination problem and does not solve three others. Which is which, before anybody announces one.

Days this part is about, hour by hour

The dayEach working hour, in orderNeeded it

Monday, the third week

0 of 7

Came in to make up a missed day

Tuesday, the fourth week

2 of 7

Thursday, the first week

0 of 7

Nobody from the team was in

Could only have happened there: 2Possible anywhere, better there: 1Identical anywhere: 15Made worse by being there: 3

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.

Home / The week

Method

For teams moving between home and office, it helps to read the full product overview and compare time, attendance, and work patterns without treating presence as the result itself.

The broader workplace question can also be compared with resources from Microsoft WorkLab.

An anchor day is a named day on which a particular group is in the building together. Not a requirement to be in three days; a statement that this group is in on this day.

It is the single highest-return change available in a hybrid arrangement, and it is routinely oversold, which is how it gets introduced and then quietly abandoned.

What it fixes

The overlap problem, completely. The first kind of hour requires another person. An anchor day guarantees other people, which is the entire mechanism. Nothing else in a hybrid policy supplies this.

The room problem, mostly. A known date can be booked a month out. On the record here, nine rooms were attempted and six obtained; every one of the three failures was on an unplanned day.

The judgement problem. A day with a name can be assessed. "Was Wednesday worth it?" is answerable. "Were your three days worth it?" is not, because they were three different kinds of day.

What it does not fix

It does not reduce the travel. The journey costs what it costs, and an anchor day is still a journey. It improves the return, not the price.

It does not help whoever cannot make that day. This is the serious one, and it is addressed below.

It does not create a reason to be together. A named day with nothing in it is a fuller version of an empty day. The anchor needs a purpose attached or it decays within a term into a day when everybody happens to be in, doing solo work, in a crowded room with no desks.

The one that needs handling

Somebody will have a standing commitment on the anchor day. A caring responsibility, a course, a fixed appointment, a shared vehicle.

Three ways this is usually handled, in descending order of how well they work:

  1. Pick the day after asking. One private question — "is any weekday impossible for you?" — before the day is chosen rather than after. Cheap, effective, and almost never done.
  2. Two anchors, one group each. Works where the team splits naturally. Halves the overlap, which is a real cost.
  3. One anchor, with the person joining remotely. Honest about the fact that they are getting less, which is better than pretending otherwise, and it should come with something else — a second named day with one or two colleagues, say.

What does not work is choosing the day and then handling the objections as exceptions, because an exception has to be asked for, and the person with the fixed commitment is usually the person least able to spend social capital asking for things.

How to introduce one

Not as policy. As a statement of fact by whoever sets the week:

I am in on Wednesdays. The planning and the one-to-ones are on Wednesdays. Come if that works.

That formulation does the work of a mandate without being one. It makes the day predictable, which is the whole requirement, and it leaves the decision where it was.

What it looks like after a term

The failure mode of an anchor day is not rejection. It is decay, and it has a recognisable course.

Month one. Everybody comes. The day is novel and somebody has usually moved a meeting onto it.

Month two. Two people miss it for good reasons. Nothing is said, because nothing should be — it is not a mandate.

Month three. The thing that was moved onto it has drifted off again, usually because somebody needed to reschedule once and the new slot stuck.

Month four. The day is now a day when some people are usually in, which is where it started.

The decay is caused by one thing: the day had no content of its own. Attendance alone cannot sustain a habit, because the reason to come is that other people will come, and that reasoning collapses the moment it is in doubt.

The two things that prevent it

Something recurring lives on the day, permanently. The planning, the one-to-ones, the review — one is enough, as long as it does not move. This gives the day a reason that does not depend on who else turns up.

Somebody notices out loud when it works. Not a review, not a metric. One sentence, occasionally: that was a good Wednesday, the thing with the schema would have taken a fortnight in writing. It costs nothing and it is what converts a habit into a shared understanding of what the day is for.