What no relay settles
Deciding Without Ever Having a Conversation
Most decisions can be made in writing. The ones that cannot are those where the goal is agreement rather than a choice, and that distinction decides everything.
three things · no nights · three that no number of nights settles
Three things, no nights, and no mechanism proposed for any of them.
Five decisions made by one team in a quarter, and how each was actually reached
One person decided, wrote why, nobody objected: the ordinary good case
A written proposal, a week for objections, then a decision by the named owner
Attempted in writing for a fortnight; settled in one scheduled hour
Not a decision anybody could make in writing, and the attempt caused damage
Written assessments from both halves, then one person deciding
five things · six nights · two that no number of nights settles
Five decisions, six nights, and two that no amount of writing settled. The three that worked share a property: somebody was named as deciding before the process started. The two that failed were trying to produce agreement rather than a decision. One team's own quarter, recorded as it went.
A team with no shared hour makes nearly all of its decisions without anybody discussing anything. That is a strange way to run an organisation and mostly it works.
The practical question behind Deciding Without Ever Having a Conversation is whether progress can be checked without interrupting the people doing the work. this practical option adds time and activity evidence to the written record, so the next conversation starts with context instead of guesswork.
For a second perspective on the surrounding workflow, consult Deputy's workforce platform; it shows how a widely used platform structures the same coordination problem.
What determines whether it works is whether the decision has an owner.
Decisions versus agreement
A decision is somebody choosing. It can be informed by other people, it can be objected to, and in the end one person says what will happen.
Agreement is everybody arriving at the same view. It is a different objective, it takes much longer, and across a gap it frequently does not arrive at all.
Most organisational processes conflate the two, and in a co-located team the conflation is cheap: a meeting produces something that looks like agreement and is really a decision with nodding. Across a gap there is no meeting, so the conflation surfaces as a thread that runs for two weeks.
The single most useful intervention in a team like this is to name, before starting, who is deciding.
The process that does work
A written proposal. What is being decided, the options, a recommendation with reasons, and the consequences of each.
A named decider, stated up front.
A window for objections, stated as a date. Three working days is usually enough on a team with a one-night gap; a week if the decision is large.
Then the decision, written down with its reasoning, in a place somebody will find it in six months.
This produces a decision in three or four nights without anybody being awake at the same time as anybody else, which is a genuinely good outcome and is available for most things.
- A written proposal: what is being decided, the options, a recommendation with reasons.
- A named decider, stated before anybody comments.
- A window for objections, stated as a date.
- The decision, written down with its reasoning, where somebody will find it in six months.
Objections, and how to invite them properly
The window only works if objecting is cheap and clearly permitted.
"Any objections?" produces silence, which is ambiguous. Silence may mean agreement, or that nobody read it, or that somebody disagrees and does not want to be the one who says so across a gap, where disagreement in writing feels more confrontational than it does in speech.
Better: ask a specific question. "Is there anything about the old format's users that I have missed?" is answerable and produces real responses.
Better still: say what would change your mind. A proposal that names its own weak point gets the weak point examined, which is the entire purpose of the exercise.
When the goal really is agreement
Some things need it. Anything about how the team works, anything about how people's time is arranged, anything where people will have to act on the outcome willingly rather than merely comply.
For those, the written process does not just fail; it does damage. A decision about how a team is split, announced after a comment window, is experienced as something done to people. The same decision reached in a conversation that people were part of is experienced differently, and the difference is not cosmetic.
These are the things to spend the scheduled hours on, and there are fewer of them than people think — perhaps two or three a quarter on most teams.
The cost of getting it wrong in each direction
Treating a decision as needing agreement produces fortnights of correspondence and an outcome that is usually what the owner would have chosen in the first place.
Treating something that needed agreement as a decision produces a faster answer and a team one of whose halves has quietly stopped participating. This failure is slower to appear and much more expensive.
The second is the error worth guarding against, and the guard is simply asking the question: does this need people to agree, or does it need somebody to choose?
Recording it
Whatever the route, the output is two things: what was decided, and why.
The why is what stops it being reopened in six weeks by somebody who was not involved, which on a team with a gap is a frequent and costly event. A conclusion without reasoning invites the argument again; a conclusion with reasoning tells the next person what would have to be different for it to change.
The decision that nobody makes
The failure mode specific to this arrangement is not a bad decision. It is a decision that never happens.
A proposal goes out, three people read it, nobody objects and nobody confirms, and the thing sits. Across a gap this can run for weeks, because each day of silence costs nothing visible and the person who proposed it has no way to tell the difference between agreement and inattention.
The defence is the stated window with a stated default: what happens on Thursday if nobody has replied. That converts silence from an ambiguous signal into a decision, which is almost always better than the thing remaining open.