{"id":"prod2-pm-checkout-pre-mortem","audience":"product-managers","category":"decisions","track":"productivity","technique":"format","title":"Run a pre-mortem on a launch with owners and early signs","free":false,"task":"Run a pre-mortem for the new checkout launch: imagine it's 3 months later and the launch failed. Write exactly 5 numbered failure reasons in the form '1. Failure: ... | Early sign: ... | Owner: ...', each based on a risk in the notes. Owners must be people from the team list. Plain text, under 160 words. The payment certification is already done, so it is not a risk anymore.","materialLabel":"Your launch notes (attached to your prompt automatically)","material":"Express Checkout launch - working notes (target: Oct 20)\n\nTeam\n- Priya Nand: engineering lead\n- Tomasz Ek: design\n- Lena Ortiz: customer support lead\n- Dev Rao: data / analytics\n\nThings I'm worried about\n- Address autocomplete fails on rural addresses in testing (about 4% of test orders).\n- Support team hasn't seen the new flow yet. Training not scheduled.\n- We only A/B tested on desktop. 64% of our orders are on mobile.\n- No dashboard yet for checkout drop-off by step.\n- Saved-card feature depends on the payment provider certification (PCI review).\n- The \"Buy again\" button sits right next to \"Place order\" on small screens; 2 testers tapped the wrong one.\n\nUpdates\n- Oct 3: payment provider certification PASSED. Saved cards are cleared to ship.\n- Oct 4: Dev says a drop-off dashboard is \"maybe 2 weeks\" away.\n\nRandom: marketing wants a confetti animation after purchase. Not decided.\n","rules":[{"type":"numberedItems","count":5},{"type":"maxWords","max":160},{"type":"plainText"}],"mistakes":[{"title":"Generic failure list","why":"The AI lists textbook launch risks instead of the ones in your notes.","fix":"Add: \"Base each failure on a worry in my notes.\"","checks":["r1"]},{"title":"Old risks kept","why":"The certification worry is still in the list, so the AI includes it.","fix":"Add: \"The payment certification passed Oct 3. Leave it out.\"","checks":["r1"]},{"title":"No owners or signs","why":"The AI names what could go wrong but not who watches for it or how you'd notice.","fix":"Show the shape: \"1. Failure: ... | Early sign: ... | Owner: ...\"","checks":["r0","r2"]},{"title":"A long risk report","why":"The AI writes headings, mitigations and paragraphs.","fix":"Add: \"Exactly 5 numbered lines, plain text.\"","checks":["numberedItems","plainText","maxWords"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting words, so a total word cap usually lands over.","fix":"Cap each part: \"each part under 10 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Frames it as a pre-mortem","patterns":["pre.?mortem","failed","3 months"]},{"label":"Shows the line shape","patterns":["early sign","owner"]},{"label":"Drops the solved risk","patterns":["certification","passed","pci"]},{"label":"Sets the count","patterns":["\\b(5|five)\\b"]},{"label":"Caps the length","patterns":["\\d+\\s*words"]}],"hint":"A pre-mortem is useful when each failure has a warning sign and a named person. Tell the AI the line format, the team, and what's already solved.","rubricLabels":["Every one of the 5 lines has three parts in order: Failure, Early sign, Owner, separated by '|'","No line treats the payment certification or saved cards as a risk, and each failure matches a worry from the notes (rural addresses, support training, mobile testing, drop-off dashboard, or button placement)","Every Owner is one of Priya Nand, Tomasz Ek, Lena Ortiz or Dev Rao (no other names), and the support training failure is owned by Lena Ortiz"]}