What to ask for
Name the day, not the number
How to propose an anchor day to a team that has never had one, including the four objections it will meet and what each one is really about.
Days this part is about, hour by hour
Wednesday, the second week
3 of 7Planning day
Wednesday, the fourth week
3 of 7The new starter's first day
Thursday, the fifth week
1 of 7three days · 21 hours logged · seven of them were only possible there · one was made worse by being there
The three days worth asking for more of.
For teams moving between home and office, it helps to review this software and compare time, attendance, and work patterns without treating presence as the result itself.
Teams can compare this approach with current guidance available from Protocol.
The proposal is one sentence long and it is usually met with agreement in principle and nothing happening. The gap between those two is where the work is.
The proposal
Could we pick a day when we are all in? I think we would get more out of one coordinated day than three uncoordinated ones.
Say it to whoever sets the week, not to the group. A group discussion about which day will produce five opinions and no decision; one person choosing after asking produces a day.
The four objections, and what each is about
"People should have the flexibility to choose." This is about freedom and is usually sincere. The answer is that naming one day leaves four free, where a count of three constrains all five — the named version is the more flexible one on any ordinary reading, as long as the count goes with it.
"Different people need different days." Often true, and it is an argument for asking first, not for not choosing. Some days are impossible for some people, and the way to find out is privately, before the day is picked.
"We tried that and it fizzled." Almost always true, and almost always because the day had no purpose attached. A named day with nothing in it decays within a term. The fix is to move something real onto it — the planning, the one-to-ones, the review — so that the day is worth attending on its own terms.
"It is not up to me." Sometimes a genuine constraint and sometimes a reflex. Worth testing, because the thing being proposed is not a change of policy: a team agreeing among themselves which day they will use is not usually something a policy prohibits, and it does not require anybody's permission to try for a month.
What to bring
Not a case. One number from your own record:
Last quarter, seventeen of my thirty-one useful hours were on Wednesdays, and I was in on Tuesdays, Wednesdays and Thursdays.
That sentence does three things at once. It is specific, so it cannot be waved away. It is about your own work rather than about the policy, so it is not a challenge. And it implies the fix without stating it, which lets the other person arrive at it themselves.
The first month
Pick the day, move one recurring thing onto it, and say what the day is for in a sentence. Do not announce a trial, do not set up a review, and do not ask anybody to commit to anything.
Then look at it after a month. If the day is full and the other days have gone quiet, it has worked and nobody needs to be told. If it has not, the thing to examine is whether anything was actually moved onto the day — in almost every failed version, nothing was.
The month-one checklist
Five things, and the arrangement usually fails if more than one is missing.
- The day is named, specifically, not "midweek".
- Somebody asked privately whether any weekday is impossible.
- One recurring thing has moved onto the day, permanently.
- The team knows where it sits when it is in.
- Somebody has said, out loud, what the day is for.
None of these requires approval, a document, or a change to any policy. Together they are the difference between an anchor day that holds and one that is gone by the third month.
What to do if it is not your call
Most people proposing this are not the person who sets the week, and the proposal still works, with one adjustment: propose it as a question about the work rather than as a scheme.
Could we try putting the planning and the one-to-ones on the same day and all being in for it? I think we would get more out of it than we do now.
That is a suggestion about meetings, not a proposal about attendance policy, and it produces the same result. The anchor day arrives as a side effect of a sensible scheduling change, which is the easiest form for it to take.
What success looks like after a month
Not that everybody came every week. That the day became the obvious answer to a question people were previously deciding alone.
The observable signs are small: somebody moves a meeting onto it without being asked; somebody says "I'll catch you Wednesday" instead of sending a message; a new person is told which day to come in on rather than being told the number.
If none of those has happened by the end of the second month, the day has no content, and the fix is to move something real onto it rather than to remind anybody about it.