Teams working across time zones cannot resolve things by asking. What is not written down is unavailable to anyone who was not in the conversation, which changes how work has to be organised.
Verbal context does not survive distribution
In a shared office a great deal of information moves through short unplanned exchanges. Nobody records it because everybody who needs it is present.
Distributed teams lose that channel entirely. Colleagues in other time zones were not present, and there is no equivalent moment in which they could have been.
The information does not become less necessary, so it has to be produced deliberately in written form or the work proceeds without it.
Decisions need reasoning attached
Recording that a decision was made is only half of what is required. What matters later is which alternatives were considered and why they were rejected.
Without that, the same options are reopened repeatedly by people who have no way of knowing they were already examined and dismissed for good reasons.
A short record of the choice, the reasoning and the constraints in force at the time prevents a substantial amount of repeated discussion.
Response latency changes what is asked
When a reply takes a working day, a question that could have been answered in seconds becomes a meaningful delay, and people learn to avoid asking.
They proceed on assumptions instead, which is faster and occasionally wrong, and the error is discovered after work has been built on it.
Reducing this depends on making the answers findable in advance rather than on responding faster, because response speed is limited by geography.
Writing is slower and it is the work
Producing a clear written explanation takes longer than saying the same thing aloud, and the cost falls on the person writing while the benefit accrues to others.
Teams that treat this as overhead rather than as part of the job find the practice erodes, usually starting with the people under the most delivery pressure.
Where it is treated as deliverable work and reviewed accordingly, it persists, because the incentive matches the effort being asked for.
Findability determines whether any of it helps
A written record that cannot be located is functionally equivalent to no record, and distributed teams accumulate documents faster than they organise them.
Conventions about where decisions live, consistent naming and periodic removal of superseded material are what turn an archive into something usable.
Without that maintenance the volume itself becomes the obstacle, and people return to asking colleagues, which reintroduces the dependency the writing was meant to remove.