{"id":"lead-delay-announcement-spoken-script","audience":"executives","category":"leadership-work","track":"leadership","level":"intermediate","technique":"tone","title":"Announce a product delay in a 6-sentence spoken script with no spin","free":false,"task":"Write a spoken script announcing the delay of the new app, for the all-hands. Plain text, exactly 6 sentences, under 110 words. Sentence 1 states the new date. Sentence 2 states the old date. Sentences 3-4 give the cause in plain words. Sentence 5 says what customers will be told. Sentence 6 says when the next update comes. Do not use the words unfortunately, exciting, journey or rest assured, and do not blame a team.","materialLabel":"Your notes (attached to your prompt automatically)","material":"Delay notes - Mobile app 3.0\n\n- New release date: Tuesday March 25. Old date: Tuesday March 4.\n- Cause: the payment-sheet integration failed security testing on Feb 17; fixes need about 3 weeks. QA found 4 high-severity issues.\n- A different cause rumor: that the design team missed their deadline. Not true; design finished on time.\n- Customers: we'll email enterprise customers on Feb 24 with the new date; support has a short FAQ.\n- Next update to staff: Friday Feb 28 in the weekly newsletter.\n- The CEO wants it known we are \"still excited\". Don't use.\n- Do not promise the March 25 date is final; say \"our current plan\".","rules":[{"type":"maxWords","max":110},{"type":"maxSentences","max":8},{"type":"plainText"}],"mistakes":[{"title":"Blaming a team","why":"The AI repeats the design rumor.","fix":"Say: \"Don't blame any team.\"","checks":["r1"]},{"title":"Spin words","why":"The AI says 'unfortunately' and 'exciting'.","fix":"Say: \"Ban unfortunately, exciting, journey, rest assured.\"","checks":["r2"]},{"title":"Promising the date","why":"The AI says March 25 is final.","fix":"Say: \"Call it our current plan.\"","checks":["r2"]},{"title":"Wrong order","why":"The AI starts with the cause.","fix":"Say: \"Sentence 1 is the new date, sentence 2 the old date.\"","checks":["r0"]},{"title":"Too many sentences","why":"The AI writes 10.","fix":"Say: \"Exactly 6 sentences.\"","checks":["maxSentences"]},{"title":"Markdown","why":"The AI adds headings.","fix":"Say: \"Plain spoken text.\"","checks":["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 sentence: \"each under 18 words.\"","checks":["maxWords"]},{"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 part instead, for example: \"each line under 12 words.\"","checks":["maxWords"]}],"promptHints":[{"label":"Six sentences","patterns":["6 sentences","six"]},{"label":"Each job","patterns":["sentence 1","new date"]},{"label":"Bans","patterns":["unfortunately","exciting","ban"]},{"label":"No blame","patterns":["don'?t blame","no blame"]},{"label":"Current plan","patterns":["current plan"]}],"hint":"Give each sentence a job, ban the spin words and blame, and say how to describe the date.","rubricLabels":["Sentence 1 gives the new date Tuesday March 25 and sentence 2 gives the old date Tuesday March 4","Sentences 3-4 give the cause as the payment-sheet integration failing security testing on Feb 17 with fixes needing about 3 weeks, and do not blame the design team","Sentence 5 says enterprise customers are emailed on Feb 24, sentence 6 gives the next update on Friday Feb 28, March 25 is called the current plan, and none of the banned words appears"]}