{"id":"pm-launch-retro-action-items","audience":"product-managers","category":"meetings","track":"productivity","technique":"constraints","title":"Turn a rough launch retro into blameless action items","free":false,"task":"After a bumpy launch, you're posting retro action items in the team channel. You want exactly 3 numbered lines in the form 'Owner: action by date', under 60 words, plain text. Skip anything already fixed, name no one as the cause of a problem, and use only owners and dates people agreed to in the retro.","materialLabel":"Retro notes (attached to your prompt automatically)","material":"Launch retro - Group booking (Bookly), Apr 9\n\nWhat went wrong:\n- Help center articles went live 2 days after launch. Support got 140 tickets. (Bea said she was waiting on final screenshots; Ivy sent them late.)\n- Launch email went to all customers, including 300 on the Basic plan who can't use group booking. Angry replies.\n- Pricing page showed the old price for 4 hours. Lena fixed it on launch day. DONE.\n- Load test was skipped because staging was booked.\n\nAgreed actions:\n- Bea: help center articles ready 3 days before every launch, starting with the May release. Due Apr 30 for the May articles.\n- Chris: add a plan filter to the launch email checklist by Apr 16.\n- Omar: book staging for load tests 2 weeks ahead, first booking by Apr 19.\n- Someone should probably look at the pricing page process? (no owner agreed)\n\nMood: tense. Ivy felt blamed for the screenshots. Lena asked that we keep the follow-up blameless.","rules":[{"type":"numberedItems","count":3},{"type":"maxWords","max":60},{"type":"plainText"}],"mistakes":[{"title":"Asking for 'retro notes'","why":"The AI rewrites the whole retro with What went well/wrong headings.","fix":"Be exact: \"Exactly 3 numbered lines like 'Owner: action by date'. Plain text.\"","checks":["numberedItems","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 16 words.\"","checks":["maxWords"]},{"title":"Including done or unowned items","why":"The AI lists every problem, including the one already fixed and the one nobody took.","fix":"Add: \"Only the agreed actions with owners. Skip anything already done.\"","checks":["r0","r1"]},{"title":"Repeating the blame","why":"The notes mention who was late, and the AI carries it into the post.","fix":"Add: \"Blameless: no one is named as the cause of anything.\"","checks":["r2"]}],"promptHints":[{"label":"Shows the line shape","patterns":["owner:? ?action","by date","owner.{0,15}date"]},{"label":"Asks for blameless","patterns":["blameless","no blame","don'?t blame","not blame"]},{"label":"Skips done items","patterns":["done","already fixed","skip","only.{0,20}agreed"]},{"label":"Sets the number of items","patterns":["\\b(3|three)\\b.{0,15}(line|action|item)"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"A good retro follow-up is short, owned and blameless. Show the AI the line shape, tell it which items are already handled, and that nobody gets named as a cause.","rubricLabels":["The 3 actions are Bea (help center articles ready 3 days before launch, by Apr 30), Chris (plan filter in the launch email checklist, by Apr 16) and Omar (book staging 2 weeks ahead, by Apr 19)","Skips the already-fixed pricing page and the unowned pricing-process idea, and invents no owners or dates","Blameless: never says or implies that anyone (especially Ivy) caused a problem, and has no intro, recap of what went wrong, or closing"]}