{"id":"pm-go-no-go-criteria","audience":"product-managers","category":"decisions","track":"data","technique":"verification","title":"Make a go/no-go call that follows the launch criteria","free":false,"task":"Launch review is in an hour. Write a first line 'Decision: Go' or 'Decision: No-go', then exactly 3 numbered lines, one per launch criterion, each ending in 'Met' or 'Not met' with the number that proves it, plain text, under 75 words. The decision must follow the rule that all 3 criteria must be met, using the latest numbers.","materialLabel":"Launch readiness notes (attached to your prompt automatically)","material":"Launch readiness - Group booking (Bookly), review Thu 3pm\n\nLaunch criteria (agreed Feb 1): ALL must be met to launch.\n1. Booking error rate under 0.5% in beta.\n2. Help center articles published (all 6).\n3. Support team trained: at least 90% of agents.\n\nStatus:\n1. Error rate: 0.3% (last 14 days of beta). Met.\n2. Help center: 6 of 6 published Tuesday.\n3. Training: 85% of agents trained as of Monday.\n   UPDATE Thu 11am (Bea): two more sessions done this morning. Now 94% trained (31 of 33 agents).\n\nOther chatter:\n- Marketing: \"Launch email is ready to go, we really don't want to slip!\"\n- Eng: one cosmetic bug (button color in dark mode). Not a criterion.\n- Sales VP asked if we can launch to Business plan only. Not on the table today.","rules":[{"type":"numberedItems","count":3},{"type":"maxWords","max":75},{"type":"plainText"}],"mistakes":[{"title":"Asking 'are we ready to launch'","why":"The AI writes a long readiness report and hedges on the call.","fix":"Be exact: \"First line 'Decision: Go' or 'Decision: No-go', then 3 numbered criteria. Plain text.\"","checks":["numberedItems","plainText","r0"]},{"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 14 words.\"","checks":["maxWords"]},{"title":"Using the old number","why":"85% appears first and fails the bar, so the AI may call No-go.","fix":"Add: \"Use the latest numbers (training is 94% as of Thursday).\"","checks":["r1","r0"]},{"title":"Including the noise","why":"The AI mentions the bug and the marketing pressure as if they matter.","fix":"Add: \"Only the 3 criteria. No chatter.\"","checks":["r2"]}],"promptHints":[{"label":"Shows the decision line","patterns":["decision:","go.{0,5}no.?go"]},{"label":"Uses the latest numbers","patterns":["latest","94","update","thursday"]},{"label":"Applies the rule","patterns":["all (3|three)","criteria","rule"]},{"label":"Proves each line","patterns":["met","number","proves?"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"A go/no-go call should follow the criteria, not the loudest voice. Tell the AI the decision line, to show proof per criterion, and which numbers are current.","rubricLabels":["The first line is 'Decision: Go'","The 3 criteria lines show error rate 0.3% Met, help center 6 of 6 Met, and support training 94% (31 of 33) Met, using the Thursday update rather than 85%","Mentions none of the chatter (marketing pressure, dark mode bug, Business-plan-only idea) and has no intro or closing"]}