Define the shared object of work
A cross-location project can appear aligned because every team uses the same project name, while each is actually working towards a different immediate outcome. Start by naming the next shared object: a site brief, an approved visual sequence or a tested workflow. Describe what it must contain and who will use it next. This makes the collaboration concrete without demanding that every team organise its internal work in the same way. The shared object becomes the place where different expertise meets, and where a disagreement can be examined as a specific decision rather than a general communication problem.
Write for the colleague who is offline
A useful handover message contains the current state, the decision made, the reason it was made and the next action that remains open. Include the relevant material directly rather than assuming the recipient remembers a discussion held in another time zone. Imagine the colleague beginning work while everyone who attended that discussion is unavailable. Can they distinguish a suggestion from a settled choice? Can they identify what would justify changing direction? Writing for that moment reduces the need for a live explanation and gives the receiving team enough context to exercise judgement within the agreed scope.
Separate discussion from authority
A crowded conversation does not automatically make a decision shared. Name who can decide each class of question and who should be consulted before that decision is made. A creative lead may settle composition, while a local owner confirms the meaning of market-specific copy. Put these roles beside the work rather than in a distant organisation chart. When a question crosses boundaries, identify a single person responsible for coordinating the answer. This helps teams participate openly without interpreting every comment as an instruction, or waiting for unanimous agreement on choices that already have an accountable owner.
Design a rhythm around dependencies
Meeting frequency should follow the work’s dependencies, not the anxiety created by distance. Some decisions need a live conversation; others are better handled through a written review with a clear closing time. Identify the small overlap periods that matter and reserve them for questions that benefit from immediate exchange. Outside those periods, use status updates that show what changed and what action is needed. A predictable rhythm helps people plan focused work and makes silence easier to interpret, because the team knows when a response is expected and when another location is simply offline.
Preserve local knowledge in the shared record
A global template can organise work while still leaving room for local context. Record the assumptions that depend on a particular location, language or operating arrangement, and identify who can confirm them. When a local team explains why a familiar approach will not fit, preserve the reasoning rather than only the revised instruction. That context may become important when the project expands to another setting. The shared record should allow differences to remain intelligible, so that collaboration produces a coherent outcome without erasing the expertise that each location contributes to the work as it develops.
Editorial draft prepared for the BGX concept preview. This is not a regulatory announcement or evidence of a deployed client project.
