Convierte tus notas de logros en puntos pulidos para la revisión de rendimiento con este prompt de IA
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
TOP 3 IMPACT BULLETS
- 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.
- 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.
- 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.
LEADERSHIP & INFLUENCE
- 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.
- 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].
GROWTH EVIDENCE
- 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.
- 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.
SUMMARY PARAGRAPH
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.
GAPS TO ADDRESS NEXT CYCLE
- 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.
- 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.
- 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.
El error más común en las revisiones de rendimiento es describir actividad en lugar de impacto. «Lideré el proceso de planificación del roadmap para Q2» le dice al evaluador lo que hiciste. «Reduje el tiempo del ciclo de entrega de funcionalidades en un 34 % durante seis meses al reestructurar el proceso de planificación del roadmap de sprints mensuales a quincenales» le dice qué cambió gracias a ti. Esa distinción es la diferencia entre una revisión estándar y una que merece una promoción.
La fórmula XYZ — «Accomplished X as measured by Y by doing Z» — existe precisamente para forzar esa distinción. X es el resultado, Y es cómo se mide, Z es la acción. La fórmula es simple, pero aplicarla de forma consistente a todo un período de revisión es donde la mayoría lucha. Este prompt lo hace por ti.
Qué produce el prompt
Pega notas toscas y desordenadas — incluso fragmentos como «arreglé lo del pago lento» o «ayudé a incorporar nuevos miembros al equipo» — y el prompt devuelve cinco secciones estructuradas:
- Top 3 impact bullets en formato XYZ, con recordatorios entre corchetes para que rellenes métricas desconocidas.
- Leadership and influence evidence — momentos en que influiste en otros sin autoridad formal.
- Growth evidence — habilidades desarrolladas y nuevas capacidades demostradas.
- Un párrafo resumen en tercera persona, listo para que un manager lo copie directamente en un paquete de promoción.
- Gaps to address — observaciones honestas sobre áreas poco desarrolladas para seguir en el próximo ciclo.
Por qué importa la restricción de métricas desconocidas
Una razón por la que la gente evita el formato XYZ es que no tiene los números exactos. El prompt maneja esto encerrando entre corchetes las métricas desconocidas con sugerencias sobre dónde encontrarlas: [check analytics dashboard], [confirm with PM — target was 20%], [estimate based on hours saved × team size]. Esto mantiene la salida honesta mientras te incita a reunir la evidencia antes de presentar, en lugar de omitir las métricas por completo.
Las métricas inventadas son un riesgo de credibilidad — los evaluadores a menudo conocen los números reales y detectan discrepancias. Reconocer lo desconocido con una nota de origen es mucho mejor que estimaciones con apariencia de certeza que luego resultan incorrectas.
Cómo usar este prompt
- Abre una app de notas y dedica 15 minutos a un brain dump de todo lo que hiciste en el período de revisión — proyectos, reuniones que lideraste, incendios que apagaste, feedback que recibiste, métricas que moviste, código que enviaste, decisiones que influiste. No filtres; la cantidad importa en esta etapa.
- Completa los tres campos de contexto (rol, período de revisión, equipo) y pega tus notas crudas dentro del prompt.
- Ejecútalo en Claude Opus 4.7 o GPT-4o para mejores resultados — estos modelos son mejores para inferir impacto implícito a partir de descripciones casuales.
- Revisa la salida con cuidado. El modelo acertará la estructura, pero podría malinterpretar el contexto técnico específico — trátalo como un borrador sólido, no como la versión final.
- Completa los espacios entre corchetes para métricas antes de enviar. El tiempo invertido en encontrar esos números vale la pena.
El caso de uso del paquete de promoción
El párrafo resumen — escrito en tercera persona — es la salida más subestimada del prompt. Muchos managers escriben paquetes de promoción para sus reportes y les cuesta articular el impacto de manera que resuene con evaluadores de niveles superiores que no tienen contexto directo. Un resumen en tercera persona bien estructurado, que comience con impacto cuantificado, le da al manager material para trabajar directamente, sin tener que sintetizar todo desde cero.
Si estás gestionando tu propia campaña de promoción, puedes compartir el resumen generado con tu manager y ofrecerlo como punto de partida para el paquete. La mayoría de los managers agradecen tener material concreto.
Ejemplo de transformación
Nota original: «ayudé con el rediseño del dashboard, recibí buen feedback»
Salida XYZ: «Reduje el volumen de tickets de soporte al cliente en un estimado del 18–22 % [confirm with support team] al rediseñar el analytics dashboard para mostrar por defecto las cinco vistas más solicitadas, eliminando los pasos de configuración que generaban la mayoría de los escalamientos de soporte.»
La nota original no daba al evaluador nada que evaluar. El punto XYZ le dice qué cambió, aproximadamente cuánto, y exactamente por qué. Esa es la brecha que cierra este prompt.