Most cross-functional friction is not disagreement. It is two teams solving slightly different problems, both convinced they are aligned. Distance makes that easier to miss and slower to correct.
// Alignment is a written artefact
Verbal alignment expires the moment the call ends. The teams I have seen work across locations write things down: the problem, the bet, the metric, the non-goals. One page, owned by design as often as by product. If a decision cannot survive being written in a paragraph, it was never a decision.
// Design the meeting, not just the product
A weekly review where nothing is decided is a status call in costume. I structure reviews around the choice on the table — here are two directions, here is what each costs, here is what we need from you today. Engineering and PM stop being an audience and start being co-authors.
// Trust travels slower than Slack
Remote pods need disproportionate investment early: shared context, visible work-in-progress, and a manager who repeats the why more often than feels necessary. The repetition is the job. People in another location cannot absorb context by osmosis.
// Credit loudly, correct quietly
Uniting teams across locations comes down to who gets seen. Name the researcher, the writer, the engineer who unblocked the release — in the forum where it counts. Handle the misses one-to-one. That asymmetry is what makes a distributed team feel like one team.