{"id":"wri-mgr-meeting-change-announcement","audience":"managers","category":"writing-emails","technique":"format","title":"Announce a team meeting change people will actually follow","free":false,"task":"You're changing your weekly team meeting. Post it in the team channel under 70 words, plain text: the first line says what changes and from when, then at most 3 bullets, and the last bullet says exactly what's due in the new Friday written update and where. Use the final details from your notes. Write a prompt that gets that post.","materialLabel":"Your planning notes (attached to your prompt automatically)","material":"TEAM MEETING CHANGES - planning notes (me, Andre, Client Services team of 9)\n\nToday: Mondays 9:00-10:00 am, 60 min, Conference Room C.\n\nNew plan (approved by my director Friday):\n- Moves to Tuesdays, 10:00-10:30 am. 30 minutes instead of 60.\n- Starts Tuesday, Nov 18. (I first wrote Nov 11 in my draft, but that's Veterans Day and half the team is out. Nov 18.)\n- Location: Zoom only. Conference Room C is being turned into a client room.\n- New: a written update every Friday by 3 pm in the #cs-weekly channel: 3 lines each, wins, blockers, next week.\n- The meeting itself will only cover blockers and decisions, not status.\n\nWhy I'm doing this:\n- People said the Monday meeting was mostly status updates that could be written.\n- Monday mornings are our busiest client-call time.\n\nOther:\n- Zoom link is the same as the old backup link (in the calendar invite).\n- Survey results: 7 of 9 voted for shorter meetings.\n- I'll send the new calendar invite today.","rules":[{"type":"maxWords","max":70},{"type":"maxBullets","max":3},{"type":"plainText"}],"mistakes":[{"title":"Trusting the AI to count words","why":"AI is bad at counting. Ask for \"under 70 words\" and it often lands well over.","fix":"Cap each part: \"First line under 15 words, each bullet under 14 words.\"","checks":["maxWords"]},{"title":"Explaining before announcing","why":"The AI opens with why you're making the change, so the new time is buried.","fix":"Say it: \"First line: Tuesdays 10:00-10:30 am, starting Nov 18.\"","checks":["r0"]},{"title":"Using the draft date","why":"Your notes list Nov 11 before the correction. The AI may copy it.","fix":"Add: \"Starts Nov 18.\"","checks":["r0"]},{"title":"Too many bullets, vague ask","why":"The AI lists every detail, and the Friday update gets a vague line like \"share updates in Slack\".","fix":"Add: \"At most 3 bullets. Last bullet: Friday update due 3 pm in #cs-weekly, 3 lines.\"","checks":["maxBullets","r1","r2"]},{"title":"Forgetting where it gets pasted","why":"AI adds bold and headings by default, which show up as ** and # clutter in Slack.","fix":"Add: \"Plain text, no bold, no headings.\"","checks":["plainText"]}],"promptHints":[{"label":"Sets a word limit","patterns":["\\d+\\s*words","word (limit|count)"]},{"label":"Puts the change first","patterns":["first line","lead with","start with","tuesday"]},{"label":"Uses the right start date","patterns":["nov(ember)?\\s*18"]},{"label":"Limits the bullets","patterns":["\\b(3|three)\\b.{0,15}bullet","bullet.{0,20}\\b(3|three)\\b"]},{"label":"Spells out the Friday update","patterns":["friday","3 ?pm","cs-weekly"]}],"hint":"Changes stick when the first line says what and when, and the ask is exact. Tell the AI the order, the bullet limit and the details of the new update.","rubricLabels":["The first line says the team meeting moves to Tuesdays, 10:00-10:30 am, starting Nov 18 (not Nov 11)","Says the meeting is on Zoom only and will cover blockers and decisions, not status","The last bullet says the Friday written update is due by 3 pm in #cs-weekly with 3 lines (wins, blockers, next week), and nothing comes after it"]}