{"id":"cs-risk-slide-three-lines-honest","audience":"executives","category":"support-work","technique":"tone","track":"support","level":"intermediate","title":"Write an honest risk slide in three lines without blame","free":false,"task":"Write the text for an EBR risk slide with exactly three lines starting \"What happened:\", \"What we did:\" and \"What's next:\". Include dates and one number. Do not blame the vendor or the customer. Plain text, under 75 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"EBR RISK SLIDE: Ashby Retail (audience: customer's COO)\nINCIDENT: On Aug 8, the platform's scheduling feature was unavailable for 3 hours 20 minutes (9:40 AM to 1:00 PM). About 260 store managers could not publish schedules that morning.\nCAUSE: a database upgrade by our hosting vendor failed and our rollback took longer than planned.\nOUR ACTIONS: Aug 9 root-cause report shared; Sep 1 added a second database replica; Sep 15 tested failover (completed in 4 minutes).\nNEXT: quarterly failover test on Dec 1 and Mar 1; status page alerts sent to the 12 admin contacts.\nInternal: 'The vendor's engineers made a mistake on the upgrade.' (Do not blame the vendor.)\nCustomer-side: their managers had not subscribed to alerts. (Do not blame the customer.)","rules":[{"type":"plainText"},{"type":"maxWords","max":75}],"mistakes":[{"title":"Blaming the vendor","why":"The internal note says the vendor made a mistake.","fix":"Add: \"Do not blame the vendor or the customer.\"","checks":["r2"]},{"title":"Missing numbers and dates","why":"The AI writes 'an outage occurred in the summer'.","fix":"Say: \"Include the dates and the 3 hours 20 minutes.\"","checks":["r1"]},{"title":"Wrong layout","why":"The AI writes slide bullets with headings.","fix":"Name the three labels.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"Names the labels","patterns":["what happened:","what we did:","what.s next:"]},{"label":"Bans blame","patterns":["do not blame","no blame"]}],"hint":"An honest risk slide is specific and blame-free. Name the lines, the facts to include and what not to say.","rubricLabels":["The output is exactly three lines starting What happened:, What we did: and What's next:","What happened gives the Aug 8 outage of 3 hours 20 minutes affecting about 260 store managers, and What we did gives the Aug 9 report, the Sep 1 replica and the Sep 15 failover test","What's next gives the Dec 1 and Mar 1 failover tests, and nothing blames the vendor, the customer's managers or their alert settings"]}