{"id":"pro-pm-launch-day-run-order","audience":"product-managers","category":"planning","technique":"constraints","title":"Sequence a launch day so nothing goes out too early","free":false,"task":"You're the PM launching a new savings goals feature in a budgeting app, and you're posting the launch-day run order. You want exactly 6 numbered lines in time order, each as time - task - owner, under 80 words, plain text. Nothing customer-facing can go out before the feature is live in both app stores, so use the app store's actual approval time, not the planned one. Write a prompt that gets you exactly that.","materialLabel":"Your launch notes (attached to your prompt automatically)","material":"Savings Goals launch - Tue Dec 2 - Penny Wise app\n\nOriginal plan (assumed app store approval by 8:00am):\n- 8:00 Turn on feature for all users - Mateo\n- 8:30 Publish help center article - Grace (support)\n- 9:00 Send launch email to customers - Hana (marketing)\n- 9:30 Post on social channels - Hana\n- 10:00 Support team briefing on common questions - Grace\n- 11:00 Exec update in #leadership - me\n\nRule from our launch checklist: no customer-facing communication (help article, email, social) before the feature is live in BOTH app stores.\n\nUpdate Mon night from Mateo: \"Apple approved, but Google Play review won't finish until 10:30am Tuesday. I'll turn the feature on at 10:30 right after.\"\n\nInternal stuff can happen any time. Support briefing should still be BEFORE customers hear about it.\n\nAlso: launch cake at 3pm in the kitchen!","rules":[{"type":"numberedItems","count":6},{"type":"maxWords","max":80},{"type":"plainText"}],"mistakes":[{"title":"Copying the original plan","why":"The planned times look final, and the AI keeps the 9:00 email.","fix":"Add: \"Google Play approves at 10:30, so the feature goes live then.\"","checks":["r1"]},{"title":"Not stating the rule","why":"The AI shifts some times but sends the help article before launch.","fix":"Add: \"Nothing customer-facing before the feature is live in both stores.\"","checks":["r1"]},{"title":"Losing the briefing order","why":"The AI moves the briefing after the email, so support hears last.","fix":"Add: \"Support briefing before any customer communication.\"","checks":["r2"]},{"title":"Letting the AI pick the layout","why":"The AI builds a table or bold headings.","fix":"Be exact: \"Exactly 6 numbered lines like '1. 10:00 - Support briefing - Grace'. Plain text.\"","checks":["numberedItems","plainText","r0"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for \"under 80 words\" and it often lands well over.","fix":"Cap each part instead: \"each line under 9 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Says how many lines","patterns":["\\b(6|six)\\b"]},{"label":"Uses the real approval time","patterns":["10:30","google play","approv","update"]},{"label":"States the rule","patterns":["customer.facing","before .{0,20}live","both (app )?stores"]},{"label":"Keeps support first","patterns":["briefing","support (before|first)"]},{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]}],"hint":"One late approval moves everything after it. Give the AI the real live time and the rule about what can't go out before it.","rubricLabels":["Lines are in time order, each giving a time, a task and an owner","The feature turns on at 10:30 and the help article, launch email and social post are all at or after 10:30, with nothing customer-facing before the feature is live","The support briefing comes before the help article, email and social post, and the cake is left out"]}