Deliver a fair promotion deferral with clear milestones

Turn a difficult promotion deferral conversation into a transparent plan with concrete milestones, maintaining trust and retention.

You getConversation script and 90-day roadmap

Prompt

Prompt
Act as an experienced people leadership advisor. Help me deliver a fair, transparent promotion deferral conversation that keeps an employee motivated.

First, ask me 3 numbered questions in a single reply and wait for my response:
1. What is the employee's current role and the target promotion role?
2. What specific gap or business reason prevented the promotion during this cycle?
3. What is their general work style and how do they typically handle critical feedback?

After I answer, apply these rules:
- Keep the tone empathetic, firm, and focused on future growth.
- Frame missed criteria as observable skills rather than character traits.
- Provide an exact conversation opening script that delivers the decision early.
- Create a measurable 90-day progress checklist.

Output format:
- Conversation script: opening remarks, core decision, and empathetic transition.
- Clarifying the gap: bullet points contrasting current performance vs target level expectations.
- 90-day roadmap: a 3-column markdown table with columns Milestone, Observable Proof, and Manager Support.

Example output

Example for: senior engineer deferred from staff engineer promotion

Conversation Script

Opening: "Thanks for meeting today, Alex. I want to share the outcome of our promotion committee cycle right away so we can focus our time on what it means and where we go next. Your promotion to Staff Engineer was deferred for this cycle."

Transition: "I know this is disappointing news, especially given how hard you drove the checkout migration. You are a valued anchor on this team. My goal today is to walk through the exact feedback from calibration and build a concrete plan so we can put forward an undeniable case next cycle."

Clarifying the Gap
  • Target Level Expectation: Staff Engineers must demonstrate cross-team technical alignment and influence architectural decisions across at least two related engineering domains.
  • Current Performance: Strong end-to-end execution within the payments pod, but limited engagement with platform and security teams prior to technical design freeze.
  • Target Communication: Proactive documentation that drives consensus before building, rather than resolving integration blockers reactively during release week.
90-Day Roadmap
MilestoneObservable ProofManager Support
Days 1-30: Architecture AlignmentDraft and publish the multi-region failover RFC with sign-offs from both Payments and Platform leads.Introduce you to the Platform principal lead to co-sponsor the review.
Days 31-60: Cross-Pod MentorshipRun two technical design reviews for engineers outside your primary pod.Create dedicated agenda space in bi-weekly guild meetings.
Days 61-90: System DeliveryShip the auth refactor milestone with zero Sev-2 regression incidents across dependent services.Shield you from ad-hoc sprint support tickets during release week.
Written by AI from this prompt. Your results will vary.

Paste into ChatGPT, Claude, or Gemini. The model will ask three quick questions about the employee's role and gaps before building your script. Reply with brief notes, and ask for follow-up roleplay adjustments if needed.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Leadership & Management
Leadership & Management

Build a thirty-sixty-ninety day onboarding plan

Generate a clear, phased milestone roadmap for incoming team members to eliminate ambiguity. Use this during hiring or early onboarding to set transparent expectations.

Leadership & Management

Build a coaching plan for a skill gap

Create a lightweight, sprint-friendly coaching plan that helps a team member close a practical capability gap without burning them out.