{"id":"mgr-x-incident-recap-vp","audience":"managers","category":"summarizing","track":"productivity","technique":"verification","title":"Recap a customer incident for your VP, facts only","free":false,"task":"Your VP wants a recap of yesterday's shipping incident before talking to the customer's executive. Write exactly 4 lines labeled What happened:, Customer impact:, Fix:, and Prevent:, plain text, under 80 words. Use only confirmed facts with the corrected number, and leave out the unconfirmed cause that's still being investigated.","materialLabel":"Your incident notes (attached to your prompt automatically)","material":"Incident notes - Brightwater Logistics shipment, Tue Mar 10 (prepared by Kim, Fulfillment Ops)\n\nTimeline (confirmed):\n- 6:00am: Wave 2 picking started for Brightwater's weekly order.\n- 9:40am: Packing found the wrong SKU (12-pack instead of 24-pack) on 38 pallets.\n  CORRECTION 2pm: recount shows 31 pallets, not 38. 7 were counted twice.\n- 11:15am: Truck held. Correct product re-picked.\n- 4:30pm: Correct shipment left. Arrived Wed 8am instead of Tue 6pm (14 hours late).\n\nCustomer impact (confirmed): Brightwater's Thursday promotion is still on track; their ops manager confirmed by phone.\n\nFix (done): wrong pallets pulled back to stock; re-pick completed.\n\nPrevent (agreed): scan check at pallet wrap for all Brightwater orders starting Mar 12.\n\nNot confirmed / under investigation:\n- Possible cause: a new hire may have used last week's pick list. Do NOT share until HR and I finish the review.\n- Possible cause #2: label printer glitch. Unverified.\n\nOther: team stayed 2 hours late to fix it. Pizza ordered.","rules":[{"type":"maxWords","max":80},{"type":"plainText"}],"mistakes":[{"title":"Asking for 'an incident summary'","why":"The AI writes a full report with a timeline, headings and root-cause speculation.","fix":"Be exact: \"4 lines labeled What happened:, Customer impact:, Fix:, Prevent:. Plain text.\"","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 18 words.\"","checks":["maxWords"]},{"title":"Using the first count","why":"38 pallets appears first, and the correction is easy to miss.","fix":"Add: \"Use the corrected 31 pallets.\"","checks":["r1"]},{"title":"Repeating unconfirmed causes","why":"The AI likes to explain why, so it shares the new-hire theory.","fix":"Add: \"Only confirmed facts. No possible causes.\"","checks":["r2"]}],"promptHints":[{"label":"Shows the labels","patterns":["what happened:?","customer impact:?","prevent:?"]},{"label":"Uses the correction","patterns":["31","correct"]},{"label":"Facts only","patterns":["confirmed","no (speculation|cause|guess)","unconfirmed","only facts"]},{"label":"Says who reads it","patterns":["vp","executive"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"Your VP will repeat this to a customer, so every line must be confirmed. Give the AI the labels, the corrected number, and tell it to leave out unproven causes.","rubricLabels":["Has exactly 4 lines labeled What happened:, Customer impact:, Fix: and Prevent:, in that order","What happened uses 31 pallets (not 38) and the shipment arrived 14 hours late (Wed 8am); Customer impact says the Thursday promotion is still on track","Mentions no unconfirmed cause (no new hire, last week's pick list or label printer), and Prevent is the scan check at pallet wrap starting Mar 12, with no pizza or overtime chatter"]}