Library › Customer Support & Success AI › Managers and team leads
Build a Q2 vs Q3 metrics table with signed changes
- For Managers and team leads
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
- Level Intermediate
About this exercise
Build a QBR metrics table with the header row exactly "Metric | Q2 | Q3 | Change" and four rows. Change is the Q3 number minus the Q2 number with a sign, in the same unit, like "+12 users" or "-3 points". Use the corrected Q2 number where the notes give one. Plain text, table only, under 70 words.
Common mistakes when you ask AI for this
- Using the uncorrected Q2. The export shows 120 and the AI uses it. Try: Say: "Use the corrected Q2 number: 112."
- Using percentages. The analyst draft says 10% and the AI adds percent changes. Try: Say: "Signed change in the same unit. No percentages."
- Wrong table. The AI adds a commentary column. Try: Give the exact header row; table only.
- Getting markdown back. AI adds bold and headings by default, which show up as stray symbols where this is pasted. Try: Say "plain text, no bold, no headings, no asterisks".
- Trusting the AI to count words. AI is bad at counting and usually runs long, so a vague "keep it short" lands well over the limit. Try: Cap each part instead of the total, for example "each line under 15 words".
What a strong prompt includes
- Asks for plain text
- Sets a length limit
- Gives the header
- Uses the corrected number
Related exercises
- Accrue unpaid wages for the working days after the last pay period (Finance AI · Accountants)
- Acknowledge an accessibility bug without a promised date (Customer Support & Success AI · Customer support teams)
- Acknowledge an executive escalation within the hour (Customer Support & Success AI · Executives)
- Age a returns queue in business days and flag the ones over the limit (Customer Support & Success AI · Customer support teams)
- Alert sales to a competitor's price change, facts only (Research & AI Search · Product managers)