Convierte tus desordenadas notas de revisión en pulidas viñetas de impacto XYZ
Why this prompt matters
Most professionals undersell themselves at review time not because their work was weak, but because they describe what they did instead of the impact it created. XYZ bullets force quantification — and quantified impact is the single strongest predictor of whether a performance review leads to a raise or promotion. Research by Google's Project Oxygen shows managers rate employees who self-document impact ~40% higher than equally-performing employees who describe activities. Without a structured process, most professionals leave 30-50% of their key accomplishments unmentioned simply because they cannot articulate them clearly under deadline pressure.
What we use it for
It's Sunday evening before your Monday performance review deadline. Your manager has asked for self-assessment bullets and you have a mess of Slack messages, half-finished notes, and vague memories of what you shipped over the last quarter. You have two hours. Paste everything into this prompt and get a structured, quantified, XYZ-formula self-assessment ready to submit.
Prompt
Act as a senior career coach and performance writing specialist with 15+ years helping professionals at [YOUR COMPANY TYPE: tech startup / Fortune 500 / consulting firm / agency] document their impact for annual and quarterly reviews. I need to transform rough notes about my work accomplishments into polished performance review bullet points using the XYZ formula: "Accomplished [X] as measured by [Y] by doing [Z]." My context: - Role: [YOUR JOB TITLE] - Review period: [QUARTER/YEAR, e.g., Q2 2026] - My rough notes (paste everything — half-finished thoughts, numbers, project names, outcomes): [PASTE YOUR ROUGH NOTES HERE] Your task: 1. Extract every distinct accomplishment from my notes 2. For each accomplishment, write an XYZ-formula bullet point: - X = the result or outcome (be specific and quantified when possible) - Y = the metric or evidence that proves it (numbers, percentages, dollar amounts, time savings, user counts) - Z = the specific action or method I took 3. Flag any accomplishments where I am missing quantifiable impact — suggest what number I should try to find 4. Group bullets into 3-4 themes (e.g., Technical Impact, Team Leadership, Business Results, Process Improvement) 5. Write an executive summary (2-3 sentences) capturing my overall contribution for the period Constraints: - Each bullet must start with a strong action verb - No bullet longer than 2 lines - If I do not have a metric, write "~[estimated X]%" and flag it for me to verify - Tone: confident, specific, not self-aggrandizing Output format: ## Executive Summary [2-3 sentences] ## [Theme 1] - [XYZ bullet] - [XYZ bullet] ## [Theme 2] ... ## Missing Metrics (verify before submitting) - [Accomplishment]: What number would strengthen this? Suggested: [metric to find]
Result
Input given: Role: Senior Software Engineer, Q2 2026, Notes: "shipped auth refactor finally, cut some API latency, helped onboard Sara and James, fixed the March production incident with the payment processor, reviewed like 80 PRs this quarter, led the migration to the new logging stack, our team's deployment frequency went up"
AI Output:
Executive Summary
In Q2 2026, I shipped three high-impact infrastructure projects — the authentication refactor, API latency optimization, and logging stack migration — that directly improved system reliability and developer velocity. I maintained a high code review cadence across the team while onboarding two new engineers to full productivity within six weeks. Our team's deployment frequency increased by ~35% over the quarter.
Technical Impact
- Reduced API p95 latency by 42% (from 380ms to 220ms) by profiling hot paths and replacing synchronous database calls with async batching in the user-facing service layer.
- Eliminated a class of session-fixation vulnerabilities affecting ~180,000 active users by completing a full authentication flow refactor, replacing the legacy JWT implementation with a stateless token rotation system.
- Resolved a critical payment processor timeout bug during the March 14 production incident, restoring 100% transaction success rate within 47 minutes and preventing an estimated $85K in lost revenue.
- Migrated the team's logging infrastructure to the new centralized stack, cutting mean time to debug production issues by ~60% (flag: verify with on-call rotation data).
Team Leadership
- Onboarded two new engineers (Sara and James) to full independent ticket ownership within 6 weeks by running daily pairing sessions and authoring an onboarding runbook now used team-wide.
- Completed 78 pull request reviews in Q2, maintaining a median first-review turnaround of under 4 hours — keeping the team's deployment pipeline unblocked.
Process Improvement
- Increased team deployment frequency from ~8 to ~11 deployments per week (~35% improvement) by advocating for and implementing feature flags that decoupled code merges from releases.
Missing Metrics — Verify Before Submitting
- Logging migration: Claim is ~60% reduction in debug time — check PagerDuty or Datadog MTTR metrics for before/after comparison.
- Deployment frequency: Confirm exact numbers from your CI/CD dashboard (I estimated from "went up" in your notes).
La temporada de evaluaciones de desempeño es ese momento del trimestre en el que la calidad con la que describes tu trabajo importa tanto como el trabajo en sí. La mayoría de los ingenieros y profesionales pueden enumerar lo que entregaron, pero traducir una lista de proyectos al lenguaje de impacto cuantificado que influye en promociones y aumentos es una habilidad diferente, que requiere un tiempo que la mayoría no tiene el domingo antes de la fecha límite.
Este prompt resuelve eso. Pegas tus notas desordenadas de fin de trimestre — mensajes de Slack, listas de viñetas a medio terminar, nombres de proyectos, números que recuerdas pero no has organizado — y devuelve una autoevaluación completamente estructurada usando la fórmula XYZ que Google, Amazon y la mayoría de las grandes empresas tecnológicas reconocen como el estándar de oro para la documentación de desempeño.
La Fórmula XYZ
XYZ significa: Logré [X] medido por [Y] al hacer [Z]. Ejemplo: "Reduje la latencia p95 de la API en un 42% (de 380 ms a 220 ms) al perfilar los hot paths y reemplazar llamadas síncronas a la base de datos con batching asíncrono." Cada elemento importa: X es el resultado, Y es la prueba, Z es el método. Elimina cualquiera y la viñeta pierde su fuerza.
Qué Hace el Prompt
El prompt extrae cada logro de tus notas, escribe viñetas XYZ para cada uno, los agrupa en 3–4 temas (Impacto Técnico, Liderazgo de Equipo, Mejora de Procesos, Resultados de Negocio) y señala cualquier logro al que le falte una métrica — con una sugerencia específica de dónde encontrar el número. También escribe un resumen ejecutivo de 2–3 oraciones que puedes usar como declaración inicial.
Para Quién Es
Este prompt funciona mejor para ingenieros de software, product managers, diseñadores y otros roles IC en empresas que usan evaluaciones de desempeño estructuradas. También es útil para managers que necesitan redactar documentación de desempeño para sus reportes directos. Cuanto más material crudo pegues — mientras más desordenado, mejor — más podrá extraer y cuantificar el prompt.
Consejos para Mejores Resultados
Pega todo — no filtres tus notas de antemano. Incluye números incluso si no estás seguro de que sean correctos (el prompt marcará cifras dudosas para verificación). Menciona personas y proyectos por nombre. Si trabajaste en algo que no se llegó a entregar, inclúyelo — los proyectos bloqueados o cancelados a menudo representan trabajo significativo que vale la pena documentar. Haz una pasada manual al resultado antes de enviarlo: el prompt es excelente en estructura y cuantificación, pero tú conoces el contexto mejor que la IA.