Translate engineering updates for leadership

--- name: translate-engineering-updates-for-leadership description: "Use when an engineer-to-engineer update needs to reach managers, product leads or executives: rewrites it in plain cause-and-effect language, sized for the channel (chat post, email, standup line, ticket comment, talking points)." --- Apply this whenever you are asked to turn technical work notes, bug analyses or incident details into an update for managers, product owners, release managers or executives, or to make something less technical. Identify the channel first. A chat post, a standup line, an email, a ticket comment and meeting talking points need different lengths. If the channel is not clear, ask one short question and wait. Build the update around four answers, in this order: what the current state is, what it means for customers or the release, who owns it, and what happens next and when. Translate carefully: - Keep the names leadership tracks: product and component names, ticket numbers, customer or workload names, version numbers. - Remove what they cannot act on: function names, file paths, code snippets, commit identifiers, configuration keys, line numbers. - Explain the mechanism in one or two sentences of cause and effect. Keep real technical concepts such as race condition, memory leak or regression when they matter; replacing them with vague words sounds condescending. - Never soften the facts. A regression stays a regression and a missed date stays missed. - State confidence plainly: confirmed, likely, or still being investigated. Sizing guide: a standup line is one or two sentences. A chat post is 3-6 lines with the status first. A ticket comment is short paragraphs ending with the next action and owner. An email has a subject line that states the outcome, then under 200 words. Talking points are 3-5 bullets plus one line on likely questions. Avoid jargon dumps, long background before the point, stacked hedges, blame, and dates nobody has committed to. End with a clear ask if a decision or help is needed.

Chat post version: Status: The fix for export timeouts (TICKET-482) is ready and in testing; release 4.2 stays on track for Thursday. What happened: two background jobs were writing to the same file at once (a race condition), so large exports hung instead of finishing. Customer impact: about 30 accounts saw failed exports last week; support has a workaround. Owner: Data platform team. Next: confirm the fix under load tomorrow; I will post the result by noon. Ask: Product, please hold the help-center note until Thursday.