communication-patternslisted

# Communication Patterns > Auto-fires on: documentation work, presentations, executive memos, board / investor decks, all-hands prep, written incident reports, public blog posts, RFCs / ADRs, status updates, performance reviews, technical proposals, conference talks, customer-facing copy, public statements, crisis comms, internal change announcements, hiring decisions communication, layoff / RIF comms, partnership communications, PR / press communications, training materials, onboarding content, slack threads in #incident or #leadership, email to senior stakeholders. Sister to `negotiation-patterns` (substance), `comms-reviewer` agent (Council Division 16), `doc-updater` agent, `documentation-requirements` rule, `ux-research` (audience understanding). Standards: Minto 1987/2009, Strunk + White 1959/2000, Heath + Heath 2007/2010, Duarte 2008/2010, Reynolds 2008/2019, Bezos 2017, Tufte 1983/2001/2006, Patterson + Grenny + McMillan + Switzler 2002/2022, Stone + Patton + Heen 1999/2010, Carnegie 1936/1981, Pinker 2014. ## Purpose Communication is the discipline of getting an idea from your head into somebody else's head with high enough fidelity that they can act on it. Engineering work is judged largely on whether other people understand it; the most brilliant technical insight that nobody can decode produces no value. Most people communicate badly because they write or speak from their own perspective: they convey what they want to say, in the order they thought of it, in t