management-talklisted

# Management Talk (เล่าให้ผู้บริหารฟัง ตามรูปแบบช่องสาร) **Habit**: H4 — Think Win-Win + H6 — Synergize | **Anti-pattern**: Paste a code-heavy JIRA comment into Slack and call it "the update for leadership" Same source material, **shaped for the channel** it's going to. The audience is engineering-savvy non-engineers — they read product / framework names and cross-reference JIRA keys and PRs, but they do not read code. The channel decides length, formatting, and how much structure to leave on the page. ## When to Use - After `/post-mortem` or any engineering writeup, when the content needs to flow up-the-org or sideways into product/release. - User says "write for management / exec / VP / director / PM / release manager". - User asks for "executive summary", "leadership update", "status update", "talking points for [meeting]". - User says "make it less technical / less jargony / less code-heavy". - User asks for "slack version / standup note / email version" of engineering content. If the channel is unclear after the trigger, ask one short question — _"JIRA, Slack, standup, email, or meeting?"_ — and stop. ## When to Skip - Audience is true ELI5 / marketing / finance / customer-facing. Engineering-org leadership has technical vocabulary; those audiences don't. Flag and confirm before producing a different rewrite. - Source content is already non-technical (already a Slack-shape; already an email). - Engineering content is being written for engineers (use `/post-mortem`