cross-team-plain-language

# Cross Team Plain Language Turn raw thoughts into language other people can catch, understand, and continue. ## Core Job Take material that is: - scattered - emotionally loaded - too insider-ish - too technical for the audience - technically correct but socially hard to receive Then rewrite it into a version that is: - easier to understand - easier to reply to - easier to forward - aligned to the audience's concerns ## Workflow 1. Identify the audience. - boss / leadership - product - engineering - operations / customer success - cross-functional group chat 2. Extract the real message. - what happened - why it matters - what decision or response is needed 3. Remove blockers. - jargon without explanation - emotional venting that hides the point - overly long setup - claims that are hard to act on 4. Rebuild the message in plain language. 5. Offer 2-4 variants when useful: - short chat version - formal update version - structured bullet version - push-without-sounding-pushy version ## Output Pattern Default to this structure unless the user asks otherwise: 1. **你原本想表达的核心** 2. **别人更容易接住的版本** 3. **如果要更短/更正式/更柔和，可以改成** ## Editing Rules - Preserve intent, not exact wording. - Prefer concrete nouns over abstract phrases. - Replace insider shorthand with terms outsiders understand. - Surface the ask explicitly. - Keep causality clear: “现象 → 影响 → 建议/请求”. - If the user sounds frustrated, keep the force but reduce the splash damage. ## Good Delivery Shapes ### A. Cross-team alignment Use when the goal is shared understanding. ```text 目前看到的问题是…… 它带来的影响是…… 我建议下一步先…… ``` ### B. Friendly but useful group-chat summary Use when the message should feel natural, not like a memo. ```text 我先帮大家收一下： 现在讨论里比较集中的点是…… 如果按优先级看，我会先…… ``` ### C. Decision-ready summary Use when the reader needs to decide or allocate resources. ```text 这不是单点反馈，而是一个模式：…… 当前最优先要解决的是…… 后续再扩展…… ``` ## When To Push Back If the source material is too vague, say what is missing instead of pretending clarity exists. Ask only for the minimum missing piece, such as: - audience - desired tone - whether the user wants explanation, persuasion, or status update ## References - See `references/patterns.md` for rewrite patterns and before/after templates.