The short version
- Across time zones a decision is not one event. It is made in one zone and learned about in another, hours later, secondhand.
- That gap is where decisions come apart: the zone that was asleep receives an outcome without the reasoning, so it reads as an instruction.
- Un-deciding is easy when the record is a meeting nobody in your zone attended. Whoever speaks loudest next wins.
- Publish the decision with its reasoning and its authority, in a form the absent zone can question during their own day.
In one office, a decision happens once. Someone makes the call, the people affected hear it in the same hour, and the reasoning arrives attached to the outcome. Across three countries none of that holds, and the decision has to survive a journey it was never designed for.
"We decided, then the loudest person un-decided."
A decision is not one event
Across zones a decision has three separate moments. It is made, in a meeting or a thread, by whoever was awake. It is transmitted, usually in a summary written by one participant. And it is received, hours later, by people who were not present and who now have to decide whether to treat it as settled.
Each moment loses something. The making loses the people who could not attend. The transmission loses the reasoning, because summaries record outcomes. And the receiving loses the authority, because nobody in the receiving zone watched anyone decide.
What arrives secondhand
| Present in the room | Reaches the other zone |
|---|---|
| The outcome | Yes |
| The reasoning | Partly, and thinly |
| The alternatives rejected | Almost never |
| Who actually decided | Rarely stated |
| The sense of having been part of it | No |
The third and fourth rows are the ones that cause the damage. Without the rejected alternatives, the receiving zone will propose one of them in good faith. Without a named decider, nobody can tell whether the question is settled, which is the dynamic in why decisions keep getting revisited.
How decisions get un-decided
The sequence is consistent. Zone A decides on Tuesday. Zone B reads a two-line summary on Wednesday morning and has a reasonable objection, because the reasoning that would have answered it was not transmitted. They raise it in their own working hours, where nobody from Zone A is present to respond, so their objection goes unanswered for a day and accumulates agreement locally.
By the time Zone A reads it, the question is live again and the original decision has lost its standing. Whoever pushes hardest in the next shared hour wins, which is a decision process determined by stamina and seniority rather than by reasoning.
Notice that nobody behaved badly. Zone B had a legitimate objection and no way to get it answered quickly, which is precisely the waiting problem applied to decisions.
Publishing a decision properly
Four lines, written by the decider, in the place the absent zone will read.
Decided. One sentence, stated as a fact.
By, and when. A person, not a meeting.
Rejected, and why. The two alternatives most likely to be proposed by someone who was not there.
Changeable by. Who can revisit it, and what evidence would justify doing so.
Then make it answerable, because four lines still cannot anticipate every objection. With StandIn, the decision written into the decider's brief is what their StandIn answers from while they are off: someone in the next zone can ask why the alternative was rejected and get the decider's own reasoning with a source under it, during their own working day, rather than waiting a night and drifting into a second debate. It never guesses, so when the reasoning genuinely was not recorded, they find that out immediately and know to ask.
That closes the gap the un-deciding happens in. See how StandIn works.
A rhythm that reduces the problem
Three habits, cheap to adopt.
Never decide something in a meeting one affected zone could not attend, without a 24-hour objection window afterwards. Say so explicitly in the summary: "decided, objections by Thursday 09:00 CET with a reason".
Have the decider write the summary, not the note-taker. A note-taker records what was said; only the decider can state the authority.
And when an objection arrives from another zone, answer the reasoning rather than restating the outcome. Restating is what converts a question into a conflict.
Common Questions
How do you make decisions stick across time zones?
Publish the outcome with its reasoning, the rejected alternatives, and a named decider, then make that reasoning questionable during the absent zone's own working hours. Most un-deciding is an unanswered objection rather than a genuine disagreement.
Should every zone be present for every decision?
No, that is unachievable and would slow everything to the pace of the rarest shared hour. Instead give absent zones a defined objection window and the reasoning they need to use it well.
What if an objection arrives after work has started?
Answer it on the reasoning, and hold the decision unless the objection introduces something new. Reversing on preference after work has begun teaches the team that decisions are provisional, which is expensive in every direction.
Who should write the decision summary?
The person who made the call. It is the only way the summary can state authority credibly, and authority is the part the absent zone most needs in order to treat the matter as settled.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.