Your Goal: Tell Marcus Chen that there's no Senior Engineer promotion this cycle despite him being performance-ready — and keep him motivated, engaged, and not walking out the door.
The CLEAR Framework (8-10 minute conversation)
1. C — Context & Safety (1-2 minutes)
- Open warmly, acknowledge his impact this year
- Set the stage honestly: "I want to have a real conversation about the promotion cycle"
- Create safety before delivering the news
- Key: Marcus came in expecting a promotion. The gap between his expectation and reality is massive — handle with care.
2. L — Listen (1 minute)
- Before sharing the decision, ask what he's been hearing and hoping for
- "I know you've been thinking about the Senior role — tell me where your head's at"
- This surfaces the skip-level promise early so you can address it head-on
3. E — Explain with Data (2 minutes)
- Lead with validation: "You ARE ready for Senior — I want to be clear about that"
- Explain the structural constraint: headcount freeze, budget, band limits
- Be honest about the skip-level miscommunication — own it as a leadership failure
- Never make it sound like a performance issue when it isn't one
4. A — Acknowledge Feelings (1-2 minutes)
- Name what happened: "You were told you were ready and now the system isn't delivering. That's frustrating."
- Don't minimize the skip-level promise — address it directly
- Let him be frustrated without getting defensive
- Handle his objections one at a time — he'll escalate
5. R — Roadmap Forward (2-3 minutes)
- Written development plan with quarterly milestones — not verbal promises
- Specific timeline: "Q1 next year" not "sometime next cycle"
- Immediate value: stretch assignment, tech lead on a visible project, title adjustment
- Offer to involve skip-level in the commitment: "Let's get this documented with your skip-level too"
- Make it clear he's first in line when headcount opens
What Scores High
- Validating readiness explicitly: "You're ready for Senior — this is a structural issue, not you"
- Owning the skip-level miscommunication: Don't throw the skip-level under the bus, but acknowledge the breakdown
- Specific timeline: "Q1 review" or "I'm pushing for out-of-cycle in October" — not "next cycle"
- Written plan: "I'll draft a development plan with quarterly checkpoints and share it this week"
- Immediate value: Stretch assignment, project leadership, conference speaking slot, title tweak
- Empathy under pressure: Staying calm and non-defensive when Marcus escalates
- Addressing the market reality: Acknowledging that he has options without being threatened by it
What Kills Trust
- Denying he's ready: "Well, there are still some gaps..." (when there aren't)
- Blaming the skip-level: "That wasn't my call, talk to them"
- Vague timeline: "Probably next cycle, we'll see"
- Dismissing market comparison: "Well, grass isn't always greener"
- Getting defensive: "I'm doing my best here too, you know"
- No concrete plan — just words and good intentions
- Making him feel like he has to prove himself again