Collection
Write asynchronous messages that can be acted on without a meeting
Structure email, chat, tickets and handoffs around action, ownership, evidence, uncertainty and final state so readers can route, decide and execute without reconstructing the author's mental model.
16 elements · Explore in any order.
2 heuristics · 4 principles · 8 protocols · 2 templates
16 elements
State what the reader must do before giving the history
The action is part of the message, not a conclusion the reader should infer.
Read the idea TemplateMake the subject line carry state and ask
The subject line is the first routing layer.
Read the idea HeuristicLabel the message mode: decision, action, blocker or FYI
Different message modes deserve different reader behavior.
Read the idea ProtocolPut owner, output and deadline on the same line
An action is not complete until someone can point to who delivers what by when.
Read the idea PrincipleSplit a message when it asks for unrelated decisions
Bundling saves sending effort but increases routing ambiguity.
Read the idea TemplateWrite known, unknown and assumed as different states
Uncertainty becomes dangerous when formatting erases it.
Read the idea PrincipleAttach the source next to the claim it supports
A source is most useful where the reader needs to verify the statement.
Read the idea ProtocolName files for identity and state, not for your desktop history
A file name should help the receiver choose the right artifact without opening every version.
Read the idea ProtocolShow the delta when a requirement changes
Change communication should reveal the change.
Read the idea PrinciplePut the caveat beside the decision it can change
A caveat is useful only before the reader commits to the wrong interpretation.
Read the idea ProtocolPreserve the sequence when chronology explains the failure
Some problems are state machines disguised as email threads.
Read the idea ProtocolReset a long thread with a current-state block
Reply history is storage, not a current brief.
Read the idea HeuristicUse a table only when the rows answer the same question
Tables clarify comparison; they can hide narrative dependencies.
Read the idea PrincipleGive technical terms one local definition
Shared words can hide unshared models.
Read the idea ProtocolEscalate asynchronously with impact, clock and failed path
Urgency needs operational evidence.
Read the idea ProtocolClose the thread with the final state and source of truth
Closure is a state transition worth writing down.
Read the idea