The policy
The days it does not name
The biggest silence in a hybrid policy, and the reason it is usually deliberate: naming days means owning the result.
Days this part is about, hour by hour
Monday, the third week
0 of 7Came in to make up a day missed through illness
Wednesday, the third week
1 of 7Tuesday, the second week
0 of 7three days · 21 hours logged · one of them was only possible there · two of the three days contained no such hour at all · four were made worse by being there
Three days the policy treats as identical.
When a hybrid policy measures attendance but not outcomes, managers can read the practical product guide and add project-time evidence to a more useful conversation about what different locations enable.
The broader workplace question can also be compared with resources from TechCrunch.
Of the six silences, this is the one that determines nearly everything else. A policy that says three days and not which three has made a specific choice, and it is worth understanding why, because the reason is not laziness.
Why the days are left open
It looks generous. Flexibility is a benefit, and leaving the days open is the cheapest form of it available. The policy can honestly say it gives people choice.
It avoids an argument. Naming Wednesday means hearing from everybody for whom Wednesday is impossible, and those conversations are individual, awkward and slow. Leaving it open means the same problem is distributed and silent.
It is uniform. A single sentence applies to four hundred people in nine locations doing eleven kinds of work. Naming days cannot be done centrally, because the right day differs by team.
It avoids owning the outcome. This is the one that is rarely said. If the policy names the day and the day is empty, the policy is visibly responsible. If the policy names a count and the days are empty, the people are visibly responsible.
That last asymmetry is worth sitting with. Both versions can fail; only one of them produces a failure that points back at the document.
What it costs to leave open
Everything in the first half of this site. The coordination collapse, the two full days and three thin ones, the fifteen days that returned nothing, the person whose three days fall where nobody is.
Put as a single sentence: a count of days maximises attendance and does not even attempt overlap, and overlap is what the whole thing was for.
Why "name the days" is not the same as "mandate more"
The objection to naming days is that it reduces flexibility, and it does. What is usually missed is that it only reduces flexibility if the count stays.
- Three days a week, your choice — three uncoordinated journeys.
- Three days a week, one of which is Wednesday — the worst of both, and the version most often adopted.
- Wednesdays, and the rest is yours — one coordinated journey, four free days, and more of the valuable hour than either of the above.
The third is less restrictive than the first by any ordinary measure, and it is the only one of the three that produces what the policy is for. It is also the one that is hardest to write centrally, which is why it is rare.
The sentence that makes it possible
A central policy cannot name Wednesday for everybody. It can do the one thing that lets every team name its own:
Teams agree their own days together. We are not counting.
Nine words of devolution, and they replace the entire coordination failure with a conversation that takes one meeting.
What naming costs the person who does it
Worth spelling out, because the reluctance is rational and treating it as laziness gets nowhere.
Naming a day means hearing from whoever cannot make it, individually, and those conversations are slow and awkward. It means being responsible if the day turns out to be empty or pointless. And it means having made a decision that can be criticised, where leaving it open means no decision exists to criticise.
Against that, the benefit accrues mostly to other people and is hard to attribute. A manager who names a day well will not be credited with the eleven journeys their team did not waste, because nobody counts those either.
That asymmetry explains the behaviour better than any failure of imagination does. The costs of naming land on the namer and are immediate; the benefits are diffuse and invisible.
What makes it easier
Three things that reduce the cost to the person doing it:
- Ask first, privately. The awkward conversations happen either way; having them before the decision means they shape it rather than contest it.
- State it as a fact, not a rule. I am in on Wednesdays and the planning is on Wednesdays commits nobody and produces nearly the same convergence as a mandate.
- Attach something to it. A day with a recurring purpose defends itself. A day with nothing in it has to be defended by the person who named it, every time somebody misses it.
The version that costs almost nothing
For a manager who does not want to decide anything:
Which day would you all pick, if we were all picking the same one?
One question, one meeting, and the answer is usually unanimous within about ninety seconds, because everybody has already been reasoning about it privately for months. The decision then belongs to the team, and the convergence is just as good.
On this record nobody asked it in thirteen weeks, and the answer would have been Wednesday.