{"id":"pm-status-page-incident-summary","audience":"product-managers","category":"customer-replies","track":"writing","technique":"audience","title":"Write a public incident summary for the status page","free":false,"task":"After yesterday's outage, you're posting a summary on the public status page. Write exactly 4 lines labeled What happened:, Who was affected:, What we fixed: and What's next:, in plain words customers understand, plain text, under 90 words. Use times in UTC with the corrected end time, and leave out internal names, blame and unconfirmed causes.","materialLabel":"Internal incident notes (attached to your prompt automatically)","material":"Incident INC-2291 - Notewell, Tue Mar 3 (internal)\n\nTimeline (UTC):\n- 14:05 Sync between the web app and mobile apps stopped. New edits on mobile didn't appear on web and vice versa.\n- 14:20 On-call (Raj) paged.\n- 15:40 Cause found: a config change to the sync service set the wrong queue limit. Rolled back.\n- 16:10 Sync restored, backlog processed. Incident closed.\n  CORRECTION (post-review): backlog fully processed at 16:35 UTC, not 16:10. Some edits appeared late until then.\n\nImpact: about 18% of active users made edits during the window. No data lost; all edits synced by 16:35.\n\nFix: config rolled back; added an automatic check that blocks queue limit changes outside a safe range.\n\nNext: by Mar 17, we'll add a status banner inside the apps during sync delays.\n\nInternal only: Raj's change skipped peer review. A second theory (cloud provider network issue) is unconfirmed. Don't use names or \"human error\".","rules":[{"type":"maxWords","max":90},{"type":"plainText"}],"mistakes":[{"title":"Pasting the internal timeline","why":"The AI rewrites every timestamp and technical detail.","fix":"Show the shape: \"4 lines labeled What happened:, Who was affected:, What we fixed:, What's next:.\"","checks":["r0","plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for a total word limit and it often lands over it.","fix":"Cap each line instead: \"each line under 20 words.\"","checks":["maxWords"]},{"title":"Using the old end time","why":"16:10 appears in the timeline, with the correction below it.","fix":"Add: \"The incident ran 14:05-16:35 UTC.\"","checks":["r1"]},{"title":"Blame and jargon","why":"The AI explains the cause with names, 'human error' or technical terms.","fix":"Add: \"Public page: no names, blame, ticket numbers or unconfirmed causes. Plain words.\"","checks":["r2"]}],"promptHints":[{"label":"Shows the labels","patterns":["what happened","who was affected","what we fixed","what'?s next"]},{"label":"Uses the corrected time","patterns":["16:35","correct"]},{"label":"Says it's public","patterns":["public","status page","customers"]},{"label":"Removes blame and names","patterns":["no (names|blame)","human error","raj","unconfirmed"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"Public incident posts must be clear, honest and blame-free. Give the AI the four labels, the corrected time, and what must stay internal.","rubricLabels":["Has exactly 4 lines labeled What happened:, Who was affected:, What we fixed: and What's next:, in that order","What happened gives 14:05 to 16:35 UTC (not 16:10) and says edits didn't sync between web and mobile; Who was affected mentions about 18% of active users and that no data was lost","No internal names (Raj), no blame or 'human error', no peer-review detail, no unconfirmed cloud provider theory, no ticket number, and jargon like 'queue limit' or 'config' is avoided or explained simply"]}