Turn Your Rough Work Notes into Polished Performance Review Bullets
Why this prompt matters
Professionals who write vague, activity-focused self-reviews consistently receive lower ratings than peers who write outcome-focused ones — even when the underlying work is identical. Managers read 20+ self-reviews in a calibration cycle; the ones written in the XYZ format are remembered. The ones that say "contributed to" are not. Without this prompt, most people spend 3–4 hours staring at a blank form and still submit bullets that undersell their actual impact.
What we use it for
You have your mid-year or annual performance review due in 48 hours. You have a messy Notion doc full of project names, a few Jira ticket summaries, and a vague memory of "fixing a lot of bugs." You need to turn this into 8–12 polished bullets that make your work legible to an HR calibration committee who will never read the PRs.
Prompt
You are a senior career coach specializing in performance review writing for technical and business professionals. You help people translate their raw work accomplishments into compelling, quantified impact statements using the XYZ formula: Accomplished [X] as measured by [Y] by doing [Z]. Context: - Employee role: [YOUR JOB TITLE, e.g. "Senior Software Engineer" or "Product Manager"] - Review period: [REVIEW PERIOD, e.g. "H1 2026" or "FY2025"] - Company type: [COMPANY TYPE, e.g. "B2B SaaS startup" or "enterprise financial services firm"] - Review audience: [WHO READS THIS, e.g. "my manager and skip-level" or "HR calibration committee"] Rough accomplishments to transform: [PASTE YOUR RAW BULLET POINTS, JIRA TICKET SUMMARIES, SLACK MESSAGES, OR NOTES HERE] Task: 1. Rewrite each item as a polished XYZ-formula bullet. Lead with the outcome, not the activity. 2. For items missing quantification, suggest 2-3 plausible metrics (percentage improvement, time saved, revenue impacted, error rate reduced, users affected) and note which is most defensible. 3. Identify the 3 strongest bullets that should be prominently featured at the top of the self-review. 4. For any items that are too vague to work with, ask one specific clarifying question. 5. After the bullets, write a 3-sentence summary paragraph that captures the overall narrative of the review period — what was your theme, what was your growth, what is your trajectory. Constraints: - Never invent specific numbers. Suggest ranges or ask for them. - Keep each bullet under 2 sentences. - Use active voice. Start each bullet with a strong past-tense verb. - Do not use filler phrases like "contributed to," "helped with," or "was involved in." - Adapt the language register to the review audience (technical for eng managers, business-impact for executives). Output format: **TOP 3 (highlight these)** 1. [XYZ bullet] 2. [XYZ bullet] 3. [XYZ bullet] **REMAINING BULLETS** 4–N. [XYZ bullets] **ITEMS NEEDING CLARIFICATION** [List questions] **SUMMARY PARAGRAPH** [3-sentence narrative]
Result
Here is the transformed output for a Senior Software Engineer at a B2B SaaS startup reviewing H1 2026:
Raw input provided: "fixed checkout bug, led onboarding redesign, mentored two new engineers, did a bunch of on-call shifts, helped with the Q1 launch"
TOP 3 (highlight these)
1. Resolved a critical payment flow defect affecting mobile checkout — suggested metric: reduced cart abandonment by 12–22% (ask your data team for the exact figure); alternatively, "restoring full checkout functionality for ~40% of mobile sessions within 6 hours of detection."
2. Led a full redesign of the user onboarding flow, reducing time-to-first-value from [X days to Y days] — if you have activation metrics, use them here; "increased 7-day activation rate" is the most defensible framing for a calibration audience.
3. Mentored two junior engineers through their first production deployments, both of whom shipped independently within 90 days — no metric needed, the timeline speaks for itself.
REMAINING BULLETS
4. Maintained a [X%] on-call resolution rate across [N] incidents in H1 2026, with average MTTR of [Y hours] — pull this from PagerDuty or your incident tracker; MTTR is the number managers care about most.
5. Contributed critical infrastructure work to the Q1 launch, enabling the team to ship on schedule — vague as written; see clarifying question below.
ITEMS NEEDING CLARIFICATION
For item 5 (Q1 launch): What specifically did you own? A component, a service, an integration? Was there a deadline risk you helped resolve? One concrete detail turns this into a strong bullet.
SUMMARY PARAGRAPH
In H1 2026, [Name] moved from individual contributor to a force multiplier — shipping high-impact fixes under pressure, leading the onboarding redesign from conception to production, and building the next layer of the team through direct mentorship. The through-line is operational depth: each contribution combined technical execution with cross-functional judgment. The trajectory for H2 is toward broader ownership — [Name] is ready to take on a technical lead role on a product-scope initiative.
Performance reviews are due. You have a rough list of things you worked on, but translating "fixed the checkout bug" into "Reduced cart abandonment by 18% by resolving a critical payment flow defect affecting 40% of mobile users" — that is the skill most people lack and most AI tools do poorly without the right structure.
This prompt forces the model to apply the XYZ formula systematically: Accomplished [X] as measured by [Y] by doing [Z]. It asks clarifying questions when impact data is missing, suggests plausible metrics based on context, and rewrites even vague entries into achievement-focused language that performs well in calibration meetings.
Feed it your rough bullets, messy Jira tickets, or even a brain-dump of what you did — it will return polished, quantified self-review bullets ready to paste.