{"id":"lead-team-update-after-outage-plain","audience":"managers","category":"leadership-work","track":"leadership","level":"intermediate","technique":"audience","title":"Write an internal outage update in plain words with a next date","free":false,"task":"Write the internal update to the whole company after Tuesday's outage. Plain text, under 110 words, subject first. Use the labels What happened, Who was affected, What we did, What's next, each on its own line with one sentence. Use only confirmed facts. Do not give a root cause that is not confirmed, and do not name individuals. End with the date of the next update.","materialLabel":"Incident notes (attached to your prompt automatically)","material":"Incident: Tuesday Nov 12, internal tools outage\n\n- 10:05 am: the scheduling and time-off tools became unavailable. 10:50 am: restored. Total 45 minutes.\n- Affected: all 380 employees could not request time off or check shifts; payroll was unaffected.\n- What we did: restarted the service and moved the tools to a second server; confirmed with 12 employees that things worked.\n- Suspected cause: a failed update (not confirmed); the vendor is investigating. Possibly a certificate issue. Don't state either.\n- Initial message at 10:20 said \"about 20 minutes\" - that was wrong.\n- Next: a review with the vendor on Thursday Nov 14; next update to staff Friday Nov 15 by noon.\n- Deployment was done by Alex; don't name.","rules":[{"type":"maxWords","max":110},{"type":"plainText"}],"mistakes":[{"title":"Stating a suspected cause","why":"The AI says a failed update caused it.","fix":"Say: \"Don't state a cause that isn't confirmed.\"","checks":["r2"]},{"title":"Using the early estimate","why":"The AI says 20 minutes.","fix":"Say: \"The outage was 45 minutes.\"","checks":["r1"]},{"title":"Naming a person","why":"The AI mentions Alex.","fix":"Say: \"Name no individual.\"","checks":["r2"]},{"title":"Missing labels","why":"The AI writes a narrative.","fix":"Say: \"Four labeled lines.\"","checks":["r0"]},{"title":"Markdown","why":"The AI bolds labels.","fix":"Say: \"Plain text.\"","checks":["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: \"each under 25 words.\"","checks":["maxWords"]},{"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 part instead, for example: \"each line under 12 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Labels","patterns":["what happened","who was affected","what we did","what'?s next"]},{"label":"Confirmed only","patterns":["confirmed"]},{"label":"No names","patterns":["no names","don'?t name"]},{"label":"Next update","patterns":["next update","friday"]},{"label":"Plain","patterns":["plain text"]}],"hint":"Give the four labels, limit to confirmed facts, and ask for the next update date at the end.","rubricLabels":["After the Subject line there are four labeled lines: What happened, Who was affected, What we did and What's next, each one sentence","What happened says the tools were unavailable for 45 minutes on Tuesday Nov 12 (10:05 to 10:50 am, not about 20 minutes), and Who was affected says all 380 employees could not request time off or check shifts while payroll was unaffected","The update states no unconfirmed cause (failed update or certificate), names no individual, and ends with the next update on Friday Nov 15 by noon"]}