{"id":"pm-go-no-go-launch-memo","audience":"product-managers","category":"decisions","technique":"format","track":"leadership","level":"intermediate","free":true,"title":"Make the call on Thursday's launch when the beta data is mixed","task":"The Boards 3.0 launch is Thursday, Nov 12, and the beta results are mixed. Write the go/no-go memo from you, Dana Cho (PM), to your VP, Marcus Webb, who decides tomorrow. Plain text, under 280 words, with these capitalized labels on their own lines, in this order: CALL, RULE, CRITERIA, RISKS, CASE AGAINST. CALL is one verdict in one sentence, with no hedging. RULE restates the VP's launch rule. CRITERIA has one line per criterion, marked MET or NOT MET, with the number. RISKS gives each open risk a named owner and a date. CASE AGAINST argues against your own verdict.","materialLabel":"Beta results and notes (attached to your prompt automatically)","material":"BETA RESULTS (3 weeks, 1,250 users: 750 iOS, 500 Android)\n- Activation (created a first board within 24 hours): 62%. Beta goal was 45%.\n- Crash-free sessions: 99.4%.\n- Open bug: \"login loop\" on Android. 3% of Android users (15 of 500) get stuck on the sign-in screen after the app updates. Mei Tran, Android lead, has a fix in review; QA needs one day to verify it. She expects it ready Tue, Nov 10. iOS is not affected.\n- Support: 0 of 8 agents are trained on Boards 3.0. Luis Ortega, support lead, has training booked Tue, Nov 10, 2 hours.\n\nVP'S LAUNCH RULE (Marcus, set Oct 20): Launch only if (1) activation is at least 45%, (2) crash-free sessions are at least 99%, (3) no open bug affects more than 1% of users on any platform, and (4) support is trained.\n\nRELEASE TOOLING: can roll out by platform and by percentage. Can pause a rollout in minutes.\n\nOTHER NOTES\n- Marketing has an email to 40,000 customers scheduled for Thursday 9am.\n- The CEO mentioned Boards 3.0 in last week's all-hands as shipping this week.\n- Two beta users on iOS asked for dark mode. Not planned for this release.","rules":[{"type":"maxWords","max":280},{"type":"plainText"}],"mistakes":[{"title":"Cheerleading or hedging","why":"The AI writes \"ship it, results are great\" or \"it depends on your risk appetite\", and the VP gets no call.","fix":"Add: \"CALL is one verdict in one sentence, with no hedging.\"","checks":["r0"]},{"title":"Ignoring the launch rule","why":"The AI judges the launch by feel and never restates or applies the VP's four conditions.","fix":"Add: \"RULE restates the VP's launch rule. CRITERIA marks each one MET or NOT MET with the number.\"","checks":["r0","r1"]},{"title":"Burying the unmet criteria","why":"The AI praises the 62% activation and softens the Android bug and the untrained support team into \"minor items\".","fix":"Add: \"One line per criterion, marked MET or NOT MET, with the number.\"","checks":["r1"]},{"title":"Risks with no owner or date","why":"The AI lists risks as general worries instead of tying each to a person and a date from the notes.","fix":"Add: \"RISKS: each one with a named owner and a date. CASE AGAINST argues against your own verdict.\"","checks":["r2"]},{"title":"Trusting the AI to count words","why":"AI writes a long memo with markdown headings and tables when you only say \"short memo\".","fix":"Say \"under 240 words, plain text\" and cap each section, like \"one line per criterion\".","checks":["maxWords","plainText"]}],"promptHints":[{"label":"Says who it is for","patterns":["vp","marcus","go/no-go","memo"]},{"label":"Asks for one clear call first","patterns":["one verdict","no hedging","call","first line"]},{"label":"Applies the VP's rule","patterns":["rule","criteri","met or not met","launch rule"]},{"label":"Gives each risk an owner and date","patterns":["owner","named","risks?","date"]},{"label":"Argues against its own call","patterns":["case against","against your own","plain text","under \\d+ words"]}],"hint":"A VP has to act on this. Ask for one verdict first, the launch rule applied line by line with MET or NOT MET, risks with owners and dates, and the strongest case against your own call.","mission":"Make a clear go/no-go call the VP can approve tomorrow.","musts":["One clear call, no hedging","The launch rule applied: MET or NOT MET with numbers","Risks with owners, and the case against your own call"],"rubricLabels":["CALL is one clear verdict (such as go, no-go, or go with a staged rollout) that is not hedged with \"it depends\", the five labels appear in the required order, and RULE restates the VP's four conditions (activation at least 45%, crash-free at least 99%, no bug over 1% on any platform, support trained)","CRITERIA marks all four correctly with numbers: activation 62% MET, crash-free 99.4% MET, the Android login bug at 3% (15 of 500 Android users) NOT MET, and support at 0 of 8 agents trained NOT MET","RISKS names Mei Tran for the Android fix and Luis Ortega for the support training, each with the date Tue, Nov 10, and it does not say the bug is already fixed; CASE AGAINST argues against the memo's own verdict with a fact from the material"]}