written-communication

To draft asynchronous Slack messages that land, use a three-step framework: Prepare your intent, Write Simply, and Run a Garbage Collector to trim excess. This produces concise, goal-oriented updates calibrated for your specific audience.

Your written communication may be misunderstood due to over-compression or over-explanation. A compression/decompression diagnostic model helps identify whether your message lacked necessary context or included too much noise, allowing you to adjust the wording accordingly.

The best way to announce a policy change is to return a draft containing intent, audience calibration, concise wording, rationale, and risk checks. This structured approach aligns teams and reduces avoidable friction in async updates.

To respond to missed messages without shaming, apply the Async Re-Explanation Trap guidance. This provides tactics for re-explaining your intent clearly and preventing repeated misreads in async communication channels.

Yes, you can use this framework for stakeholder updates and team announcements. It applies to engineering managers drafting messages across various contexts, ensuring updates are concise, audience-calibrated, and structurally sound.

You should avoid over-compressing written updates when the audience lacks context, as diagnosed by the compression/decompression model. If a message fails due to missing critical details, a more explanatory approach is needed to prevent misunderstandings.