Library › Data AI › Product managers
Triage six bugs using your team's priority rules
Practice: Giving the right context. About 5 minutes.
About this exercise
You're running bug triage and need each bug labeled using your team's written priority rules, not by how loud the reporter was. Write exactly 6 numbered lines in the form 'P0 - bug - reason', with all P0s first, then P1s, then P2s, each reason under 10 words and naming the rule that applies, plain text.
Common mistakes when you ask AI for this
- Asking 'how should we prioritize these'. The AI writes paragraphs per bug with bold headings and its own opinions. Try: Be exact: "Exactly 6 numbered lines. Plain text."
- Not giving the rules weight. The AI blends your rules with the angry email and may bump bug F to P0. Try: Add: "Label strictly by our rules, not by how urgent the reporter sounds."
- Keeping the list order. The AI goes A to F, so the P0s are mixed in with cosmetic bugs. Try: Add: "List all P0s first, then P1, then P2."
- Vague reasons. The AI writes 'high impact' instead of naming the rule. Try: Show it: "1. P0 - double charge on retry - payments wrong".
What a strong prompt includes
- Uses the team's rules
- Ignores the loud email
- Sorts by priority
- Shows the line shape
- Asks for plain text
Related exercises
- Announce a hybrid work policy change with clear actions (Writing AI · HR and recruiting)
- Announce a new weekend rotation in three clear rules (Productivity AI · Managers and team leads)
- Announce a promotion with the right date and no pay details (Writing AI · HR and recruiting)
- Announce a team change and answer the first question (Writing AI · Managers and team leads)
- Answer a showing request for a home that's under contract (Writing AI · Real estate agents)