{"id":"pm-okrs-outcomes-not-tasks","audience":"product-managers","category":"planning","track":"productivity","technique":"constraints","title":"Draft OKRs that measure outcomes, not tasks","free":false,"task":"You're drafting Q2 OKRs for the Reporting team. You want one 'Objective:' line with no numbers, then exactly 3 numbered key results, each written as a measurable outcome 'from [baseline] to [target]' using the figures in your notes, plain text, under 80 words. No key result can be a task like 'launch', 'ship' or 'build', and use the corrected baseline.","materialLabel":"Your Q2 planning notes (attached to your prompt automatically)","material":"Q2 planning - Reporting team (Tallyroom)\n\nStrategy from leadership: reporting should be a reason customers stay. Renewal interviews keep mentioning \"we can't get answers out of the data.\"\n\nNumbers we have:\n- Weekly report usage: 18% of paying accounts open a report at least once a week. Goal for end of Q2: 30%.\n  CORRECTION (data team, Mar 28): baseline is 15%, not 18%. Bot traffic from a partner integration was being counted.\n- Report load time (p75): 9 seconds today. Target: 3 seconds.\n- Reporting satisfaction (in-app survey, 1-5 scale): 3.2 average. Target: 4.0.\n\nThings we plan to do this quarter:\n- Launch scheduled email reports.\n- Redesign the dashboard builder.\n- Ship 10 new report templates.\n- Hire a data visualization designer.\n\nLast quarter's OKRs got feedback from our VP: \"These are a to-do list. Tell me what changes for customers.\"","rules":[{"type":"numberedItems","count":3},{"type":"maxWords","max":80},{"type":"plainText"}],"mistakes":[{"title":"Asking for 'OKRs'","why":"The AI writes several objectives with bold headings and adds an initiatives section.","fix":"Be exact: \"One Objective line, then exactly 3 numbered key results. 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 key result under 14 words.\"","checks":["maxWords"]},{"title":"Turning tasks into key results","why":"The planned work is in your notes, so the AI writes 'Launch scheduled reports' as a key result.","fix":"Add: \"Key results are outcomes, from baseline to target. No launch, ship or build.\"","checks":["r2","r0"]},{"title":"Missing the correction","why":"The old baseline comes first in the notes, so the AI uses 18%.","fix":"Add: \"Use the corrected baseline of 15%.\"","checks":["r1"]}],"promptHints":[{"label":"Asks for outcomes","patterns":["outcome","not (a )?task","no (launch|ship|build)","measurable"]},{"label":"Shows the from-to shape","patterns":["from .{0,15} to","baseline","target"]},{"label":"Uses the corrected baseline","patterns":["15%","correct"]},{"label":"Sets the number of key results","patterns":["\\b(3|three)\\b.{0,15}(key result|kr)"]},{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]}],"hint":"Key results should say what changes for customers. Tell the AI to write outcomes from baseline to target, to ignore the task list, and which baseline is correct.","rubricLabels":["The three key results are weekly report usage from 15% to 30%, p75 report load time from 9 to 3 seconds, and reporting satisfaction from 3.2 to 4.0","The usage key result uses the corrected 15% baseline, not 18%","No key result is a task or deliverable (no launch, ship, build, redesign or hire), the Objective line has no numbers, and there is no list of initiatives or other extra section"]}