Construye tu caso de promoción en 30 minutos con este Prompt de autodefensa
Why this prompt matters
Most capable people lose promotions not because they underperform but because they cannot translate their work into the language their organization uses to make advancement decisions. A manager advocating for your promotion needs a business case — not a list of tasks. Without a structured document, a year of strong work gets compressed into a 10-minute conversation and forgotten before the calibration meeting ends. The difference between a promotion and "strong performer at current level" is often entirely about how the case is framed.
What we use it for
You have a performance review or promotion conversation coming up in the next 4-8 weeks. You have a mental list of things you have accomplished this year, but no structured way to present them as a case for advancement — and no idea how to frame your future value in the language your organization uses to make level decisions.
Prompt
Act as a senior career strategist and executive coach specializing in corporate advancement. Context: I am a [YOUR JOB TITLE] at [COMPANY TYPE, e.g., a 500-person SaaS company] with [X YEARS] in this role. My manager is [MANAGER'S LEVEL, e.g., a VP of Engineering]. The review cycle happens [TIMING, e.g., in Q3]. The promotion I am seeking is to [TARGET TITLE]. Here are my key achievements from the past 12 months: [PASTE YOUR ACHIEVEMENTS — bullet points, rough notes, or rough descriptions are fine] Here is the job description or competency framework for the target role: [PASTE JD OR LEVEL GUIDE — or describe the key expectations if you do not have one] Task: Write a complete promotion case document I can share with my manager or use in a self-review submission. The document should: 1. Open with a 2-sentence executive summary of why I am ready for this promotion 2. Map each of my key achievements to a specific competency expected at the target level 3. Quantify impact wherever the raw data allows; flag gaps with [ADD: ...] 4. Include a future value section: what I will deliver at the next level that I cannot deliver in my current role 5. Anticipate and pre-empt the 2 most likely objections (e.g., "not enough scope", "too early") Constraints: - Write in first person, confident but not arrogant - Keep the total document under 800 words — managers skim - Do not invent numbers; flag where I need to add data with [ADD: ...] - Avoid filler phrases like "passionate about" or "strong communicator" - Tone should be factual and evidence-led, like a business case, not a cover letter Output Format: ## Promotion Case: [MY NAME] → [TARGET TITLE] ### Executive Summary (2 sentences) ### Demonstrated Readiness: Key Achievements [Achievement → Competency mapping, 4-6 bullets with brief explanation of each] ### Business Impact at the Next Level [2-3 concrete forward-looking statements] ### Addressing Likely Questions [Q: ... / A: ... format, covering the 2 most likely objections]
Result
Promotion Case: Jordan Rivera → Principal Engineer
Executive Summary
Over the past 16 months, I have operated at Principal scope — leading the architecture of our fraud detection pipeline, directing cross-team technical decisions across three product squads, and mentoring two engineers who were subsequently promoted to Senior. I am ready to formalize that scope as Principal Engineer.
Demonstrated Readiness: Key Achievements
Fraud Detection Pipeline Redesign → Systems Architecture at Scale
Designed and shipped a real-time fraud scoring system processing 18,000 transactions per minute, replacing a batch system with 4-hour detection lag. The new system detects fraudulent patterns within 90 seconds. Estimated fraud loss reduction: [ADD: pull from Finance — approximately $2.1M in Q1 based on declined chargeback claims]. Required coordinating with Data Science, Payments, and Compliance — three separate team managers.
Zero-Downtime Database Migration → Technical Risk Management
Led migration of a 340GB production database from single-region PostgreSQL to a multi-region setup with zero downtime during a peak traffic period. Authored the migration plan, ran three full dry runs, and managed a 6-hour cutover window. Post-migration uptime: 99.97% (up from 99.82%).
Engineering Standards Ownership → Organizational Leverage
Wrote the company's first API versioning policy, now mandatory for all external-facing services. Reduced breaking-change incidents from 7 in H1 last year to 1 in H1 this year. The policy is referenced in 4 ongoing architectural reviews.
Cross-Team Mentorship → Multiplier Effect
Ran weekly design reviews for two Senior Engineers, both of whom were promoted in Q2. One is now leading her own squad. Estimated investment: 3 hours/week over 8 months. Estimated organizational value: two engineers operating one level higher.
Business Impact at the Next Level
As Principal Engineer, I will establish the technical strategy for the Payments platform as we enter two new markets in H2 — work that currently has no single owner. I will chair the Architecture Review Board we have discussed but not yet created, reducing the ad-hoc architectural decisions that have caused three production incidents this year. I will represent Engineering in quarterly OKR planning, a gap the VP Engineering has flagged as a priority for the second half.
Addressing Likely Questions
Q: Is 16 months in the Senior Engineer role too fast for promotion?
A: The level framework does not specify a minimum tenure — it specifies competency and scope. I can document three Principal-level deliverables completed during this cycle. I am not asking for an exception; I am demonstrating that the criteria are already met. I am happy to formalize this in writing for your skip-level conversation.
Q: Does Jordan have the organizational influence expected at Principal level?
A: The fraud pipeline migration required aligning Data Science, Payments, and Compliance without direct authority over any of them. I drove that alignment through documentation, structured reviews, and escalation design — not through hierarchy. The zero-downtime migration is a second example of managing technical risk across organizational lines. [ADD: ask manager to add a supporting sentence here from their perspective.]
Las promociones rara vez se ganan en las evaluaciones de desempeño. Se ganan en las semanas previas, cuando tu manager está construyendo el caso de negocio para ti — a menudo usando exactamente los materiales que tú le entregas. El problema: la mayoría de la gente le da a su manager una lista de cosas que hizo. Lo que los managers necesitan es un argumento estructurado que mapee tu trabajo al lenguaje de competencias del siguiente nivel, anticipe las objeciones que su propio manager planteará, y termine con una declaración clara de valor futuro.
Este Prompt genera ese documento en una sola pasada. Está diseñado para ciclos de revisión de mitad de año y anuales, pero funciona igualmente bien cuando quieres iniciar una conversación de promoción antes de que se abra un ciclo formal.
Por qué funciona este Prompt
El Prompt está estructurado como un briefing de estrategia profesional, no como un generador de cartas de presentación. Cada sección tiene un propósito deliberado:
- La sección de resumen ejecutivo obliga al modelo a comenzar con la conclusión — lo único que tu manager necesita poder repetir textualmente cuando abogue por ti hacia arriba.
- El mapeo de logros a competencias traduce tu trabajo al lenguaje de tu marco de niveles. Este es el paso que más se omite: la gente enumera lo que hizo, no el nivel de habilidad que demuestra.
- La sección de valor futuro responde a la objeción más común de niveles superiores: "¿Qué hará esta persona de manera diferente en el siguiente nivel?" La mayoría de los candidatos no pueden responder esto claramente. El Prompt fuerza una respuesta concreta.
- La anticipación de objeciones aborda las dos preguntas que casi con seguridad hará el manager de tu manager. Darle a tu manager una respuesta preescrita significa que nunca será tomado por sorpresa.
Cómo usarlo
Pega tus notas de logros en bruto — no necesitan estar pulidas. El modelo identificará el encuadre más defendible. Los marcadores [ADD: ...] en la salida indican los lugares donde necesitas insertar datos reales antes de compartir el documento con tu manager. Ejecútalo una vez con tus notas aproximadas, luego edita la salida para precisión. Todo el proceso toma menos de 30 minutos.
Errores comunes a evitar
- No envíes la salida tal cual. Los marcadores [ADD: ...] son marcadores de posición intencionales — complétalos con números reales antes de compartir con tu manager.
- No pegues la descripción del puesto si no tienes una. Si tu empresa usa una matriz de competencias o una guía de niveles, pega eso en su lugar. Si no existe ninguna, describe en lenguaje sencillo lo que sabes que espera el siguiente nivel.
- Usa esto de 6 a 8 semanas antes de que comience el ciclo de revisión formal, no durante el mismo. El mejor uso es iniciar la conversación con tu manager temprano — no para entregar el formulario en la fecha límite.
El objetivo no es escribir tu propia evaluación. Es darle a tu manager las palabras para abogar por ti — porque la persona que toma la decisión final rara vez es tu manager directo.