Turn your rough accomplishment notes into polished performance review bullets with this AI prompt
Why this prompt matters
Most people understate their value at review time — not because they didn't deliver, but because describing impact accurately is a different skill from doing the work. The XYZ formula forces specificity that generic activity bullets lack, and the structured output gives managers something to lift directly into promotion packets. One session with this prompt typically surfaces impact that the person didn't realize they could articulate.
What we use it for
Mid-year or annual performance review is due in two weeks. You have a year's worth of accomplishments scattered across Slack messages, tickets, and half-remembered meetings. You need polished, metrics-grounded bullets that make your impact undeniable — without spending a weekend on it.
Prompt
Act as a senior career coach who specializes in helping professionals articulate their impact in performance reviews and promotion packets. **Context:** Most performance reviews fail not because the person did poor work, but because they describe their work rather than their impact. The XYZ formula — "Accomplished X as measured by Y by doing Z" — forces specificity that generic bullet points lack. Your job is to transform rough, vague notes into polished, metrics-grounded review bullets that make impact undeniable. **Your information:** Role/title: [YOUR JOB TITLE] Review period: [e.g., "H1 2026", "Q2 2026", "Annual 2025"] Your team/department: [e.g., "Growth Engineering", "Product Marketing", "Customer Success"] **Raw accomplishment notes:** [PASTE YOUR ROUGH NOTES HERE — can be messy, incomplete, and unquantified. Include anything you remember: projects, outcomes, feedback you received, problems you solved, initiatives you led, metrics you moved, processes you improved. Even vague notes like "helped with the big launch" or "fixed the thing that kept breaking" are fine starting points.] **Task:** Transform my raw notes into polished performance review content with these five sections: **1. Top 3 Impact Bullets (XYZ format)** The three strongest accomplishments, each written as: "Accomplished [X] as measured by [Y] by doing [Z]." - X = the outcome or result - Y = how it's measured (quantify if possible; estimate with a range if exact data isn't available) - Z = the specific actions taken If a metric is unknown, note it in brackets and suggest how to find or estimate it: [find exact number — check analytics dashboard]. **2. Leadership & Influence (2–3 bullets)** Moments where you shaped others' work, drove alignment, mentored, or led without authority. Format as direct statements of what you did and what resulted. **3. Growth Evidence (2–3 bullets)** Skills you developed, new domains you learned, or capabilities you demonstrated for the first time this period. Frame each as: "Expanded [skill/area] by [specific action], demonstrated by [outcome or recognition]." **4. Summary Paragraph (3–5 sentences)** A polished summary suitable for a manager to copy into a promotion packet or to use as the opening of a verbal review. Write in third person using [YOUR NAME]. Emphasize trajectory and impact, not just activity. **5. Gaps to Address Before Next Review** Based on what's missing from my notes: 2–3 honest observations about impact areas that seem underdeveloped or undocumented. Frame constructively as what to track or pursue in the next period. **Constraints:** - Never invent specific numbers — if a metric is unknown, bracket it with [estimate needed] and suggest a source - Avoid weak verbs: "helped with", "assisted", "worked on", "participated in" — replace with specific action verbs - Each bullet should be self-contained: a reader who doesn't know your context should understand what you did and why it mattered - If raw notes are too thin for a section, say so explicitly rather than padding
Result
<p><strong>TOP 3 IMPACT BULLETS</strong></p>
<ol>
<li>Reduced feature delivery cycle time by 34% over H1 2026 [verify in Jira — target was 30%] by restructuring roadmap planning from monthly milestone reviews to bi-weekly sprint ceremonies with explicit dependency mapping.</li>
<li>Improved API response time for the checkout flow from 1.4s to 340ms average [confirm with infrastructure team], directly reducing cart abandonment by an estimated 12% [check analytics] by profiling and optimizing three N+1 query patterns identified during the Q1 performance audit.</li>
<li>Decreased customer support escalations related to billing confusion by approximately 40% [confirm with support lead] by rewriting 23 error messages and adding contextual help tooltips across the billing module — a project completed in three weeks with no additional engineering headcount.</li>
</ol>
<p><strong>LEADERSHIP & INFLUENCE</strong></p>
<ul>
<li>Drove alignment between Product, Engineering, and Customer Success on the Q2 roadmap prioritization by facilitating three cross-functional working sessions that resolved a six-week prioritization standoff — the final roadmap was approved unanimously by all three VPs.</li>
<li>Mentored two junior engineers through their first production deployments, establishing a code review practice within the team that reduced post-deployment bugs by an estimated 25% in Q2 vs Q1 [check incident log].</li>
</ul>
<p><strong>GROWTH EVIDENCE</strong></p>
<ul>
<li>Expanded expertise in database performance optimization by leading the checkout flow profiling project, demonstrated by independently identifying and resolving three N+1 patterns that the team's senior engineers had not previously investigated.</li>
<li>Developed facilitation skills by running seven cross-functional planning sessions with 8–12 stakeholders, receiving direct positive feedback from the VP of Product on the improved meeting structure.</li>
</ul>
<p><strong>SUMMARY PARAGRAPH</strong></p>
<p>In H1 2026, [Your Name] delivered measurable impact across engineering performance, cross-functional collaboration, and team development. By restructuring the team's roadmap process and leading a high-priority performance optimization project, [Your Name] contributed to a 34% improvement in delivery velocity and a significant reduction in customer-facing errors. Beyond individual execution, [Your Name] demonstrated leadership by resolving a multi-week cross-functional prioritization conflict and establishing mentorship practices that are already reducing incident rates. [Your Name] is operating consistently above the requirements of their current level and is well-positioned for the next step.</p>
<p><strong>GAPS TO ADDRESS NEXT CYCLE</strong></p>
<ul>
<li>Documentation: The work done is strong but not well-documented — invest in writing up the performance optimization findings as an internal tech blog post or RFC to increase visibility with senior engineers outside the immediate team.</li>
<li>Quantification habit: Several strong impact areas (mentorship, meeting facilitation) lack before/after metrics. Start tracking a few leading indicators (junior engineers' deployment frequency, meeting resolution time) so the next review has harder numbers.</li>
<li>Scope expansion: No evidence of cross-team project ownership yet — consider raising your hand for a project that requires coordinating with teams outside your department to demonstrate readiness for a senior role.</li>
</ul>
<p>The most common mistake in performance reviews is describing activity instead of impact. "Led the Q2 roadmap planning process" tells a reviewer what you did. "Reduced feature delivery cycle time by 34% over six months by restructuring the roadmap planning process from monthly to bi-weekly sprints" tells them what changed because of you. That distinction is the difference between a standard review and a promotion-worthy one.</p>
<p>The XYZ formula — "Accomplished X as measured by Y by doing Z" — exists specifically to force that distinction. X is the outcome, Y is how it's measured, Z is the action. The formula is simple, but applying it consistently to a full review period's worth of work is where most people struggle. This prompt does it for you.</p>
<h2>What the prompt produces</h2>
<p>Paste in rough, messy notes — even fragments like "fixed the slow checkout thing" or "helped onboard new team members" — and the prompt returns five structured sections:</p>
<ul> <li><strong>Top 3 impact bullets</strong> in XYZ format, with bracketed reminders to fill in any unknown metrics</li> <li><strong>Leadership and influence evidence</strong> — moments where you shaped others without formal authority</li> <li><strong>Growth evidence</strong> — skills developed and new capabilities demonstrated</li> <li><strong>A summary paragraph</strong> in third person, suitable for a manager to lift directly into a promotion packet</li> <li><strong>Gaps to address</strong> — honest observations about underdeveloped areas to track in the next cycle</li> </ul>
<h2>Why the "metrics unknown" constraint matters</h2>
<p>One reason people avoid the XYZ format is that they don't have the exact numbers. The prompt handles this by bracketing unknown metrics with suggestions for where to find them: <code>[check analytics dashboard]</code>, <code>[confirm with PM — target was 20%]</code>, <code>[estimate based on hours saved × team size]</code>. This keeps the output honest while prompting you to gather the evidence before submission rather than leaving the metrics out entirely.</p>
<p>Invented metrics are a credibility risk — reviewers often know the actual numbers and catch discrepancies. Acknowledged unknowns with a sourcing note are far better than confident-sounding estimates that turn out to be wrong.</p>
<h2>How to use this prompt</h2>
<ol> <li>Open a note-taking app and spend 15 minutes doing a <strong>brain dump</strong> of everything you did in the review period — projects, meetings you led, fires you put out, feedback you received, metrics you moved, code you shipped, decisions you influenced. Don't filter; quantity matters at this stage.</li> <li>Fill in the three context fields (role, review period, team) and paste your raw notes into the prompt.</li> <li>Run on <strong>Claude Opus 4.7 or GPT-4o</strong> for best results — these models are better at inferring implicit impact from casual descriptions.</li> <li>Review the output carefully. The model will get the structure right but may misinterpret specific technical context — treat it as a strong first draft, not a final submission.</li> <li>Fill in the bracketed metric gaps before submitting. The time spent finding those numbers is worth it.</li> </ol>
<h2>The promotion packet use case</h2>
<p>The summary paragraph — written in third person — is the prompt's most underappreciated output. Many managers write promotion packets for their reports and struggle to articulate impact in a way that lands with skip-level reviewers who have no direct context. A well-structured third-person summary that leads with quantified impact gives a manager something to work from directly, rather than requiring them to synthesize everything from scratch.</p>
<p>If you're managing your own promotion campaign, you can share the generated summary with your manager and offer it as a starting point for the packet. Most managers will appreciate the concrete material.</p>
<h2>Example transformation</h2>
<p><strong>Raw note:</strong> "helped with the dashboard redesign, got good feedback"</p>
<p><strong>XYZ output:</strong> "Reduced customer support ticket volume by an estimated 18–22% [confirm with support team] by redesigning the analytics dashboard to surface the five most commonly requested views by default, eliminating the configuration steps that generated the most support escalations."</p>
<p>The raw note gave the reviewer nothing to evaluate. The XYZ bullet tells them what changed, roughly how much, and exactly why. That's the gap this prompt closes.</p>