{"id":"pm-roadmap-status-execs","audience":"product-managers","category":"summarizing","track":"productivity","technique":"audience","title":"Give executives a roadmap status they can read in 30 seconds","free":false,"task":"The VP of Product wants a roadmap status for Monday's exec staff meeting. You need exactly 3 numbered lines, one per initiative, each starting with On track, At risk or Late, under 60 words in total, plain text. Put any Late or At risk items first, use the newest status for each initiative, and keep out engineering detail like service names and ticket counts.","materialLabel":"Engineering status notes (attached to your prompt automatically)","material":"Roadmap status - week of Nov 10 (from eng standups)\n\n1) Self-serve onboarding (target Dec 5)\nStatus Mon: green. Wizard UI done, auth-service changes merged, 14 tickets left, 9 in review.\nStatus Thu: still green, 6 tickets left. QA starts Nov 17.\n\n2) Usage-based billing (target Dec 15)\nStatus Mon: green.\nStatus Thu: Payments vendor delayed their metering API until Dec 8. We can't finish integration and testing in one week. New realistic date: Jan 12. Moving to red.\n\n3) Admin audit log (target Nov 30)\nStatus Mon: yellow, events-pipeline backlog.\nStatus Thu: Kafka consumer lag fixed. Still yellow: export to CSV needs 1 more week, so likely Dec 7 instead of Nov 30. Everything else done.\n\nSide notes:\n- Rahul out Nov 24-28.\n- Retro moved to Friday.\n- Design wants to rename \"Workspaces\" to \"Teams\" - not decided.","rules":[{"type":"numberedItems","count":3},{"type":"maxWords","max":60},{"type":"plainText"}],"mistakes":[{"title":"Asking for 'a status update'","why":"The AI writes a section per initiative with headings, tickets and side notes.","fix":"Be exact: \"Exactly 3 numbered lines, one per initiative. Plain text.\"","checks":["numberedItems","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 line instead: \"each line under 16 words.\"","checks":["maxWords"]},{"title":"No status labels","why":"The AI describes progress in sentences, so execs must read everything to find the problem.","fix":"Add: \"Start each line with On track, At risk or Late, and put Late first.\"","checks":["r0","r1"]},{"title":"Using the Monday status","why":"Each initiative has two updates, and the AI may report the older green one.","fix":"Add: \"Use the Thursday status for each initiative.\"","checks":["r0","r1"]},{"title":"Keeping engineer detail","why":"The AI keeps ticket counts and service names because they're in the notes.","fix":"Add: \"For execs: no ticket counts, no system names, no side notes.\"","checks":["r2"]}],"promptHints":[{"label":"Says who reads it","patterns":["exec","vp","leadership"]},{"label":"Asks for status labels","patterns":["on track","at risk","late","label"]},{"label":"Puts problems first","patterns":["first","lead with","late.{0,20}(top|first)"]},{"label":"Uses the newest status","patterns":["thursday","thu","latest","newest","most recent"]},{"label":"Drops engineering detail","patterns":["no (ticket|technical|engineering|jargon)","ticket counts","leave out"]}],"hint":"Executives want the problem first and the label before the detail. Tell the AI who reads it, which label goes on each line, which status is current, and what detail to drop.","rubricLabels":["Usage-based billing is labeled Late (new date Jan 12, vendor delay) and appears first, and admin audit log is labeled At risk (likely Dec 7) before self-serve onboarding","Self-serve onboarding is labeled On track for Dec 5, using the newest status for every initiative","Contains no engineering detail (no ticket counts, service or tool names like auth-service or Kafka) and none of the side notes, with no intro or closing line"]}