{"id":"cs-yoy-metrics-table-better-worse","audience":"executives","category":"support-work","technique":"verification","track":"support","level":"advanced","title":"Build a year-over-year table that marks better or worse correctly","free":false,"task":"Build a year-over-year table with the header row exactly \"Metric | Last year | This year | Change | Direction\" and four rows. Change is a percent for the first three metrics (whole numbers, with sign) and points for NPS. Direction is Better or Worse; for resolution time, lower is better. Plain text, table only, under 70 words.","materialLabel":"Your material (attached to your prompt automatically)","material":"YEAR-OVER-YEAR, Calder Group\nWeekly active users: 200 last year, 250 this year. (More is better.)\nSupport tickets per month: 400 last year, 320 this year. (Fewer is better.)\nAverage resolution time (hours): 20 last year, 25 this year. (Fewer hours is better.)\nNPS: 40 last year, 46 this year. (Higher is better; the change is in points, not percent.)\n\nPercent change = (this year - last year) / last year x 100. Whole numbers. NPS change = this year minus last year, in points.\nAnalyst draft: 'Resolution time +25% is a good thing, more time spent on each ticket.' (Wrong: more hours is worse.)","rules":[{"type":"plainText"},{"type":"maxWords","max":70}],"mistakes":[{"title":"Marking resolution time Better","why":"The analyst says more time per ticket is good.","fix":"Say: \"Fewer hours is better; +25% is Worse.\"","checks":["r2"]},{"title":"Using percent for NPS","why":"The AI writes +15% for NPS.","fix":"Say: \"NPS change in points: +6 points.\"","checks":["r1"]},{"title":"Wrong table","why":"The AI adds a column or notes.","fix":"Give the exact header; four rows; table only.","checks":["r0"]},{"title":"Getting markdown back","why":"AI adds bold and headings by default, which show up as stray symbols where this is pasted.","fix":"Say \"plain text, no bold, no headings, no asterisks\".","checks":["plainText"]},{"title":"Trusting the AI to count words","why":"AI is bad at counting and usually runs long, so a vague \"keep it short\" lands well over the limit.","fix":"Cap each part instead of the total, for example \"each line under 15 words\".","checks":["maxWords"]}],"promptHints":[{"label":"Asks for plain text","patterns":["plain","no bold","no markdown","no formatting","no headings"]},{"label":"Sets a length limit","patterns":["\\d+\\s*words","word (limit|count)","under \\d+"]},{"label":"States the direction rules","patterns":["fewer","lower is better","more is better"]},{"label":"Names the NPS unit","patterns":["points","nps"]}],"hint":"Year-over-year tables need a direction rule per metric and the right unit for each change. State both and the header.","rubricLabels":["The header row is exactly \"Metric | Last year | This year | Change | Direction\" with four rows and nothing outside the table","The changes are weekly active users +25%, tickets -20%, resolution time +25%, NPS +6 points","Directions are Better for users, tickets and NPS, and Worse for resolution time"]}