{"id":"lead-weekly-product-risks-three-plain-lines","audience":"product-managers","category":"leadership-work","track":"leadership","level":"beginner","technique":"audience","title":"Report three product risks in plain words for your VP","free":false,"task":"Report the three biggest product risks to your VP, who is not technical. Write exactly 3 lines in plain text in the form: Risk - what could happen - what I need. Each line is under 22 words, avoids technical terms (API, latency, schema, refactor), and uses only the notes. Order the lines by how soon the problem could hit, soonest first (the cart slowdown is already happening, so it comes first).","materialLabel":"Engineering notes (attached to your prompt automatically)","material":"Product risk notes - Checkout team\n\n1. The payment API version we call will be switched off by the vendor on Jan 31. If we don't update our code, customers cannot pay. Needs 3 engineer-weeks. I need approval to move 1 engineer from the mobile team starting Dec 2.\n2. The database schema for orders is hitting its size limit; at current growth the system slows down for everyone around Feb 20. Needs a refactor of about 4 weeks. I need a decision on budget for a consultant ($18,000) by Dec 15.\n3. Latency on the cart page rose from 0.8 s to 1.4 s. Customers may abandon carts; no measured loss yet. I need analytics to set up tracking, 2 days, by Dec 6.\n4. Some of our email templates use fonts that look odd on old phones. Not a risk.","rules":[{"type":"maxWords","max":75},{"type":"plainText"}],"mistakes":[{"title":"Technical terms","why":"The AI writes 'API deprecation' and 'latency'.","fix":"Say: \"Avoid API, latency, schema, refactor; use plain words.\"","checks":["r1"]},{"title":"Wrong order","why":"The AI orders by importance.","fix":"Say: \"Order by how soon it could hit.\"","checks":["r0"]},{"title":"Including the non-risk","why":"The AI adds the fonts issue.","fix":"Say: \"Only the three real risks.\"","checks":["r2"]},{"title":"Missing asks","why":"The AI omits what you need.","fix":"Say: \"Each line ends with what I need.\"","checks":["r2"]},{"title":"Markdown","why":"The AI uses bullets.","fix":"Say: \"Plain 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 line: \"each line under 22 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":"Line format","patterns":["risk - what could happen - what i need"]},{"label":"Plain words","patterns":["plain","non-technical","avoid"]},{"label":"Order","patterns":["soonest first"]},{"label":"Three lines","patterns":["3 lines","three"]},{"label":"Plain","patterns":["plain text"]}],"hint":"Give the line format, the order, the banned technical terms and what to skip.","rubricLabels":["Has exactly three lines in the form Risk - what could happen - what I need, ordered soonest first: cart page slowness (needs tracking by Dec 6 or sooner), the payment switch-off on Jan 31, then the order system slowing down around Feb 20","The lines avoid the terms API, latency, schema and refactor, and each is under 22 words","The fonts issue is not included, and the asks are the move of one engineer starting Dec 2, $18,000 for a consultant by Dec 15, and tracking set up by Dec 6"]}