This essay expands on the “alignment” thread in Management Retrospective.

Pasting a long status update into a group chat does not mean the information sync is done. In the early days of leading collaborations, I kept falling into this trap: I thought I had “explained everything clearly,” but the recipients couldn’t see the conclusion, couldn’t assess the risk, and didn’t know whether they needed to act. The more information there is, the harder the key content can sometimes be to find.

The goal of sync is not to “send out everything you know,” but to give a specific reader, at the right time, the information needed to judge, collaborate, or act. This standard sounds simple, but it is harder to meet than one might think.

First ask what decision the reader needs to make

The same update should be written differently for different readers:

  • Syncing to an owner, the focus is results, risks, and the choices that need support;
  • Syncing to collaborators, the focus is interfaces, dependencies, and next steps;
  • Syncing to executors requires a scope, standards, and a schedule concrete enough to act on.

The same project update does not have to be written as three completely different sets of facts, but it should have different layers. Leading with the three to five most important conclusions, then linking to the data, records, and details, serves both reading efficiency and traceability — and it forces the writer to think clearly first: what is it, exactly, that the reader most needs to know?

Make numbers and conclusions checkable

Writing “response speed improved a lot” is not helpful. A better way is to state what was measured, what time range was used, what calculation method was applied, and what baseline it was compared against; and to say whether this is enough to support the current conclusion.

Numbers alone are not an explanation. The reader still needs to know what the change might come from, what uncertainties remain, and what to verify next. Separating facts, explanations, and hypotheses-to-be-tested can significantly reduce later disputes of “you didn’t make it clear at the time” — many arguments of “but I did say it” are really two sides talking about completely different definitions.

Leave an entry point for action in the sync

At the end of a sync, it should be clear: who needs to decide what now, who owns the next step, and when to revisit. A sync without an entry point for action tends to become an archive; conclusions without detailed sources tend to become slogans.

My self-check is simple: after writing a sync, I ask myself — can the reader state, within a minute, the conclusion, the risks, the required action, and where the evidence is? If not, the answer is usually not to add more information, but to reorganize the layers and the definitions.

A good sync is not a dump of information, but a bridge built for shared judgment — short enough, and sturdy enough.