Section 1
Co-located teams leak context for free
In an office, a great deal of reasoning transfers accidentally. Someone overhears the end of a conversation, sees who was in the room, reads the tone of a meeting from the corridor afterwards. None of that is deliberate communication, and none of it survives the move to remote work. Distributed teams have to replace an accidental channel with a deliberate one, and the replacement has to be asynchronous or it just recreates the meeting problem in a different timezone. That means written narrative: not minutes, which record what was said, but a short account of what was decided, what was considered and rejected, and what would make the team revisit it. Teams making that shift are running a change programme, which [How to Lead Organizational Change Through Storytelling](/blog/how-to-lead-organizational-change-through-storytelling) covers.
Section 2
Writing is the constraint, and it is worth paying
The honest cost of this approach is that writing well takes time, and not everyone on your team writes easily, particularly people working in a second language. A leader who insists on written context without accounting for that cost will get compliance rather than clarity. So make it small and specific. Five sentences on a decision beats a page nobody finishes. Accept rough prose. Edit for accuracy rather than style. The purpose is a colleague in another timezone understanding why, not a document that reads well.
Section 3
One canonical place, one predictable rhythm
Context that lives in three tools lives nowhere. Pick one location for decisions and one weekly written update, and make both predictable enough that people know where to look before they ask. Sustained narrative at scale is what turns a scattered group into something coherent, as [Case Study: How Category-Leading Brands Built a Movement with Storytelling](/blog/case-study-how-built-a-movement-with-storytelling) shows.
Section 4
What the weekly update should contain
Three parts, in the same order every week: what changed, what we learned, what is still open. Ten minutes to write, two minutes to read. The consistency matters more than the content of any single edition, because it becomes the place people check rather than a message they might scroll past. Add one thing most remote teams skip: name the decisions that were made outside the update, and where the reasoning lives. Teams do not resent decisions being made without them nearly as much as they resent discovering them by accident. Being told a call happened, and where to read the outcome, closes the gap that produces the discovery.
Section 5
Remote narrative failure modes
The synchronous all-hands as the primary channel is the first. It excludes whoever is asleep, and the recording is watched by very few people, which means the leadership team believes it has communicated while a third of the company has not received the message. The second is performance narrative, where written updates become a place to look busy rather than to transfer context. That happens when updates are read as evidence for evaluation, so keep them separate from performance reporting. The third is context that stops at the manager layer. Managers under load summarise, and the summary loses the reasoning, which is the part that was worth sending. Small distributed teams can move quickly when this works, and [How Small Teams Achieve Big Results with AI](/blog/how-small-teams-achieve-big-results-with-ai) shows what that compounding looks like.