Overview

An employee gets promoted. You send them the new job description via email. A month later, they're still doing their old job because they haven't properly ramped into the new role. Their old team is understaffed because nobody is doing their original work. They feel unsupported and are questioning whether the promotion was a mistake. Their manager is frustrated because the new person isn't independent yet. The company is asking "Did we promote the wrong person?"

Internal transfers and promotions are one of the highest-leverage HR activities. People stay longer when they see a path to growth. Institutional knowledge is retained. Institutional culture is preserved because people aren't constantly leaving. Development is visible and purposeful. But transitions have to be managed like external hires: clear preparation, explicit expectations, structured onboarding, support at key milestones. Without this, promotions become failures, good people get discouraged, and internal mobility breaks down.

This lesson covers managing internal transitions so promoted people succeed, old roles get backfilled, other employees see a successful transition and feel motivated to grow, and the organization sees internal movement as the standard path forward.

Why Internal Transitions Matter: The Cost of Getting It Wrong

Internal transitions are different from external hiring in critical ways. The person already knows the company, the culture, the business, the people. You have a track record of how they work. You know their strengths and gaps. But they might not know the new team, might not have the skills needed for the next level yet, might not understand why the company thinks they're ready now, might feel like they're being set up to fail.

Poorly managed transitions lead to a cascade of negative outcomes. New role feels like punishment, not opportunity: "I got promoted to a harder job with less support and more pressure." The person does both their old and new job for months: "I'm still fielding requests from my old team while trying to learn my new role. Nobody's helping me figure out what's the priority." Old role doesn't get covered because nobody planned for it: "My team lost a person but nobody was hired or promoted to replace me. Now they're running a 20% understaffed team." Failure in new role is visible: "After three months, it's clear I wasn't ready. Everyone knows it. I'm demoralized." Regret and questioning: "Did we promote the wrong person? Should we have hired externally?" Exodus: Other good people see internal transitions don't work and start updating their LinkedIn profiles.

Well-managed transitions produce a completely different outcome. Person succeeds in new role. They understand expectations. They have a clear plan. Their new manager knows how to support them. Old team gets backfilled quickly because the company planned for it. Company retains talent: the promoted person stays, but also the people on their old team because the transition wasn't disruptive. Other employees see a successful transition and feel motivated: "I want that path forward. The company invests in people's growth."

The difference between success and failure is planning and communication. Not skill, the promoted person usually has the skills or can develop them quickly. The issue is clarity and support.

Pro Tip: Internal promotions have a success rate of 60-70% without planning. With structured transition plans, success rates jump to 85-90%. The difference is time spent on planning (1-2 hours), not additional training budget.

Why Companies Get Transitions Wrong

Most organizations underestimate the complexity of internal transitions. They think "This person has been here for years. They know the company. They'll figure out the new role." This is backwards. External hires are given extensive onboarding. Internal hires are assumed to be self-sufficient. That's the mistake.

A director of HR at a 500-person B2B SaaS company shared this story: "We had a senior engineer who was brilliant technically. We promoted her to tech lead. We sent her the job description, introduced her to her new team, and said 'You know the engineering practices here.' Huge mistake. Six months later, she was miserable. She was still coding (didn't know when to stop and how much to delegate). She wasn't providing direction to her team (didn't know what that looked like). She had no relationship with product leadership (didn't know the politics). We almost lost her. Only when we assigned a mentor (a more experienced tech lead) and structured her ramp-up did she succeed. We should have done this from day one."

The irony: internal transitions need MORE structure than external hires, not less. External hires expect onboarding. Internal promotions are assumed to be easy because they're already here.

The Three Types of Internal Transitions

Before you can manage a transition, you need to understand what kind it is.

Type 1: Promotion (Person Moves Up One Level)

Examples: Account manager → Senior account manager. Engineer → Senior engineer. Team lead → Manager. Individual contributor → Team lead.

What's changing:
- Scope of responsibility (usually bigger)
- Complexity (usually more strategic, less tactical)
- Leadership requirement (managing people and/or projects, not just execution)
- Stakeholder management (now talking to bigger leaders, external people, etc.)

Challenges:
- Person might still want to do the work they love (coding, managing accounts) instead of the new role (strategy, hiring, mentoring)
- Relationships with peers are changing (now you manage some of your former peers)
- Expectations are higher; tolerance for mistakes is lower
- Person needs to develop new skills (management, strategy, communication) quickly

Timeline: 4-8 weeks to ramp, depending on how big the level jump is.

Type 2: Lateral Move (Same Level, Different Team or Function)

Examples: Sales in US → Sales in EMEA (same job, different region). Engineer → Product Manager (different function, same seniority). Customer Success → Sales Engineering.

What's changing:
- Context (new team, new domain, new customers maybe)
- Skills might transfer directly, or require some development
- Relationships (new team, new stakeholders)
- Processes (how does this team work?)

Challenges:
- Person might carry culture from old team ("We do things differently here")
- If moving functions, gap between expertise and role
- Integration with new team (acceptance, trust)

Timeline: 2-4 weeks to ramp for familiar moves, 4-8 weeks for function changes.

Type 3: Stretch Role or Expanded Scope (Same Level, Additional Responsibility)

Examples: Engineer leading one feature area → Engineer leading two feature areas. Account manager → Account manager + team lead (for a portion). Individual contributor → Individual contributor + project lead.

What's changing:
- Addition of responsibility without a formal title change
- Person does two jobs (old work + new work)
- Usually temporary (6-12 months), then becomes a formal promotion or resets

Challenges:
- Person might feel used ("I'm doing extra work without a title change")
- Old role work suffers because they're splitting focus
- Timeline is ambiguous ("How long is this stretch assignment?")

Timeline: 6-12 months. Then decision: promote formally, or refocus on original role.

The Complete Transition Workflow: From Decision to Success

Phase 1: Identify and Decide

Before a transition happens, someone makes the decision: "This person is ready for the next level" or "We need to move this person to a different team."

Decisions to make upfront:

• 
  Is the person actually ready? Not just "We need someone to fill this role." Is this person ready to succeed? Do they have the core skills? Do they understand the gap they need to fill? Have they shown growth potential?
• 
  What's the new role exactly? Not just "Senior role" or "Team lead." What are the specific responsibilities? Who do they report to? How is success measured? What's the scope (team size, budget, customers, products)?
• 
  Who will manage them? Is this their current manager (who now manages them in a new role) or a new manager? Either way, this manager needs to be set up for success in supporting the transition.
• 
  When? Transition date. Is it immediate? Two weeks out? A month? This affects how much time you have to prepare.
• 
  What about their old role? Who covers it? When? This decision is made NOW, not after the transition. Options: hire new, promote someone, redistribute work, hire a contractor.

Input to transition planning system:
- Current role, new role, level change
- Candidate's background, strengths, gaps
- New manager
- Start date for new role
- Backfill plan for old role

Phase 2: Generate Transition Plan

The transition plan is the blueprint for success. It documents expectations, creates a ramp-up schedule, identifies skill gaps and how to address them, and most importantly, shows the person they're not on their own.

What AI can generate (based on your input):
- Role summary: What exactly is the new role? What's staying the same, what's changing?
- Scope definition: Team size, reporting, key stakeholders, key projects
- Key responsibilities (top 5-10 things they'll do)
- Expectations at 30/60/90 days (what should be true at each milestone)
- Development plan: What skills need building? What context do they need?
- Weekly schedule for first 90 days (who to meet, what to learn, what to do)
- Relationship building plan (key stakeholders to build relationships with)
- Success signals (how will we know they're succeeding?)
- Backfill plan (who's covering old role, training timeline)

Example Transition Plan:

INTERNAL TRANSITION PLAN

EMPLOYEE: Sarah Chen
FROM: Senior Software Engineer (Backend), Reports to: Engineering Manager
TO: Engineering Tech Lead (Backend), Reports to: Director of Engineering
TYPE: Promotion (IC → Leadership)
DATE: May 15, 2026

WHAT'S CHANGING:
- Responsibilities: Less coding, more architecture and team enablement.
Still 20-30% coding on critical path items. 70-80% on team leadership,
architecture, mentorship, roadmap planning.
- Team: Will lead 4 backend engineers (was peer with them)
- Reporting: Now reports to Director vs. Engineering Manager
- Scope: Backend systems for 2 products (vs. one product area)
- Context: New leadership responsibilities, new stakeholders (product, ops),
political dynamics

EXPECTATIONS FOR SUCCESS:
- 30-day: Knows team members well (1:1s done), understands team's current
work/backlog, has met key stakeholders (product leads, ops lead, other tech
leads), can articulate the team's 90-day priority
- 60-day: Has made first architecture decision and communicated it clearly,
has completed 1:1s with each report and has development plans for them,
is leading at least one architecture discussion
- 90-day: Team is productive under her leadership, she's comfortable delegating,
she's participating in technical strategy meetings at director level,
she's mentoring reports on their growth

DEVELOPMENT NEEDED:
- Skills to build: People management (delegation, feedback, 1:1 skills),
strategic thinking (seeing beyond current sprint), communication at higher
levels (explaining technical decisions to non-technical stakeholders)
- Context to understand: How product roadmap is set, how technical decisions
are made at company level, org politics and key stakeholders, delegation
patterns (what can she decide, what needs director approval)
- Relationships: Director of Engineering (her new manager), VP of Product,
CTO (if exists), other tech leads, operations lead

30-90 DAY PLAN:
Week 1-2:
- Meet each team member (1:1, understand their strengths/gaps, learn current projects)
- Meet director (understand expectations, decision-making authority, support style)
- Meet key stakeholders (product lead, ops lead)
- Review current backlog and understand roadmap
- Attend all team meetings and leadership meetings
Daily/weekly check-in with director

Week 3-4:
- Complete development plans for each team member
- Lead one team meeting or discussion
- Make and communicate one team decision (what the team will prioritize next)
- Begin architecture review/planning for next quarter
Weekly check-in with director

Week 5-8:
- Lead team through one sprint planning and retrospective
- Provide feedback to each team member (formal or informal)
- Lead one technical decision (architecture, tool choice, process change)
- Meet with director to discuss team performance and any concerns
Bi-weekly check-in with director

Week 9-13:
- Team should be running smoothly under her leadership
- She should feel comfortable making decisions
- She should have provided meaningful feedback to team members
- She should be participating in broader technical strategy
Bi-weekly or monthly check-in with director

BACKFILL PLAN:
- Old role: Senior Backend Engineer (her individual contributor role)
- Backfill approach: Promote mid-level engineer (James) from backend team
- James's transition: 2-week overlap with Sarah where she trains him on her
projects/context, then fully owns role
- Training timeline: Sarah has last 2 weeks of April to train James
- Completion date: James fully independent May 15

MILESTONES & CHECK-INS:
- Week 1: Onboarding complete, all team 1:1s done, stakeholder meetings done
- Day 30: Formal check-in with director: how's the ramp? Any concerns?
- Day 60: Mid-point review: skills developing? Team responding well?
- Day 90: Full review: is promotion working? Path forward?

SUPPORT:
- Manager (Director of Engineering): Weekly check-ins first 4 weeks,
bi-weekly after. Available for questions about people management,
decision-making authority, political context. Will assign a mentor (CTO
or another tech lead) for technical strategy guidance.
- Peer support: Introduce to other tech leads in company who can share
learnings, challenges
- Training: Offer management training course (if company offers it).
Books on technical leadership.
- Resources: Engineering org docs, roadmap, decision-making processes

SUCCESS SIGNALS:
- By day 30: Her 1:1s with team members are happening, she's engaged in
conversations with product/ops about technical tradeoffs
- By day 60: She's made and communicated a technical decision that the team
understands and respects. Each team member knows their development
objectives. She's asking smart questions in leadership meetings.
- By day 90: Team is shipping code, meeting commitments. She's comfortable
delegating. She's gotten feedback from her team (informal check-in) that
they feel supported. Director sees her as a capable tech lead.

This plan is specific, actionable, and sets expectations. The person knows what success looks like. The manager knows how to support them. Everyone knows the backfill plan.

Important Warning: Don't create a transition plan and then not share it. It's worthless if it sits in an email. Make it official. Share with the person, their new manager, their old manager, HR. Make it part of the promotion package.

Phase 3: Announcement Meeting

The promotion is announced in a meeting, not via email. This is a big moment.

Who's in the meeting:
- Promoted person
- Current/former manager (if different from new manager)
- New manager
- HR representative

What to cover:
- Excitement/celebration: "We're promoting you because [specific reasons]. You've demonstrated [specific strengths]. We think you're ready."
- The role: What's the new role? What's the team? Who's the manager?
- The plan: Here's the transition plan we've created to support you. We've thought about what you need to succeed.
- The expectations: Success at 30 days looks like X. At 60 days, Y. At 90 days, Z.
- The support: Here's how we'll support you. Weekly check-ins. Mentoring if needed. Training resources.
- The timeline: You start the new role on [Date]. Between now and then, here's what happens (training backfill if needed, etc.).
- The old role: Here's who's covering your old work. Here's how we'll transition.
- The conversation: What questions do you have? What concerns? What would help?

Tone matters: This should be celebratory but also realistic. Not "You're ready, figure it out." Also not "This will be really hard." More like: "We believe in you. We know this is a stretch. We've created a plan to help you succeed. Let's talk about what you need from us."

Example announcement:

Manager: "We're promoting you to [New Role]. We're doing this because you've
shown strong technical chops, good judgment, and real ability to mentor others.
The team respects you. We think you're ready to take on this expanded scope.

Here's what this means: You'll be leading [number] engineers. Your focus will
shift from hands-on coding to architecture, mentorship, and strategy. You'll
report to [Director]. You'll start on [Date].

We know this is a step up. We've created a transition plan, [Share plan], that
maps out your first 90 days. You'll ramp up gradually. You'll have weekly
check-ins with [Director] and monthly check-ins with me. You'll meet with
[mentor] about technical leadership.

For your old role, [James] is being promoted to cover it, and you'll spend
your last two weeks training him.

Questions? Concerns? What would help you succeed?"

Phase 4: Transition Period (1-2 Weeks Before + Ongoing)

The transition period has two phases: old role wrap-up and new role ramp-up.

Old role wrap-up (1-2 weeks before or during transition):
- Document your work: What are you doing? What projects are in flight? What does each project need?
- Transition knowledge to backfill person: This is critical. The backfill person shouldn't have to figure out what the job is.
- Wrap up or hand off projects: Finish what you can. Hand off what you can't finish.
- Communicate with your old team: "I'm transitioning. [Backfill person] is taking my role. Here's why this is good. Here's how we'll stay connected."
- Key relationships: Brief important external stakeholders (customers, partners, other teams) about the transition.

This should take 1-2 weeks. During this time, the promoted person is often still doing their old role 50%, new role 50%.

New role ramp-up (starts immediately, continues for 90 days):
- Day 1-3: Meet new team, meet manager, understand current state
- Week 1-2: 1:1s with each team member, understand each person, understand backlog
- Week 2-4: Start making decisions, leading meetings, building relationships
- Week 5-8: Running team, making bigger decisions, connecting with broader org
- Week 9-13: Fully ramped, independent, strategic

Weekly activities during ramp-up:
- 1:1 with new manager (first 4 weeks) / bi-weekly after
- Team meeting attendance and participation
- Broader leadership/stakeholder meetings
- Development activity (reading, training, mentoring if offered)
- Documentation of learnings/questions

Phase 5: Structured Check-ins at 30/60/90 Days

These are formal check-ins, not casual conversations. They create accountability and catch problems early.

30-day check-in:
- What's gone well? Surprises?
- Are you on track with the transition plan?
- What's been harder than expected?
- What support do you need?
- Any quick wins or successes?
- What's next for the next 30 days?

60-day check-in:
- Are you becoming independent in the new role?
- How's the team responding to you?
- Skills building? What's progressing, what's still a gap?
- Relationships with new team and broader org?
- Any decisions you've made that you want to revisit or get feedback on?
- How's the old role backfill going? (If person is still supporting it)

90-day review:
- Is the promotion working? Was this the right move?
- What's your confidence level now vs. day 1?
- Where are you strong? Where do you still need to grow?
- What's the path forward? (Next promotion, expanded scope, specialty area?)
- Any ongoing support or coaching needed?
- Formal assessment: Ready to own role independently? Yes/conditional/no

If "conditional" or "no," this is the conversation to have. Either: (1) Continue support for another 30-60 days, (2) Role isn't the right fit and we need to make a change, (3) Person needs more training or mentoring.

Special Case: When Transitions Fail (And How to Fix It)

Failure 1: Person Promoted Before Ready

You promoted Sarah and by month 2 it's clear she's struggling. She's missing meetings. She's not engaging with the team. The team isn't following her direction.

Why it happens: Succession planning was skipped. You needed to fill the role, so you promoted someone, not because they were ready. Or promotions were done based on tenure (they've been here 5 years) instead of capability.

How to fix it: Have an honest conversation. "The transition isn't working as we hoped. Here are some options: (1) We slow down your ramp and give you more support/coaching. (2) We move you back to your previous role with no stigma. This transition just wasn't right. (3) We move you to a different role that might be a better fit." Most people appreciate honesty. Keeping someone in a role they're failing at is worse than moving them.

Failure 2: Old Role Isn't Backfilled Quickly

Sarah promoted May 1. Backfill search takes 6 weeks. Her old team is now 20% understaffed for two months. Work suffers. Team morale drops because they lost a person and got nobody.

Why it happens: Backfill planning was forgotten. You assumed "we'll handle it." Then the business moved on to the next priority.

How to fix it: Backfill plan must be decided before transition. Not during, before. Options: hire new person (need to start search immediately), promote someone else (identify them before Sarah leaves), hire contractor (fast, temporary), redistribute work (accept that other people will be busier for a bit). One of these needs to be the plan.

Failure 3: Transition Plan Isn't Communicated to New Manager

Sarah promoted to new manager. But the transition plan lives in HR's email and the new manager never sees it. They think Sarah should be independent immediately. They don't provide structure or support. Sarah flails.

How to fix it: Transition plan is official. It goes to: promoted person (they know expectations), new manager (they know how to support), old manager (they know the timeline), HR (they track the progress). Make it part of the promotion package, not an HR artifact.

Failure 4: Promoted Person Still Does Old Job

Sarah promoted May 1. Backfill isn't hired until August 1. Sarah does her new role 60% and old role 40% for three months. She's exhausted. She fails at both roles.

Why it happens: No clean cutoff date. Person is trying to be helpful. Manager isn't enforcing the boundary.

How to fix it: Transition plan should include a hard date when old role is handed off. "May 15-31: Sarah does 50/50. June 1: Sarah is 100% new role. [Backfill person] is 100% old role." If backfill isn't ready, that's a staffing problem, not something the promoted person should absorb.

Failure 5: Nobody Celebrates the Promotion

Sarah gets promoted and nobody really acknowledges it. No announcement to the company. No recognition. It feels quiet and anticlimactic.

Why it happens: Promotions are treated as administrative moves. Or there's a culture that success is "just what you do."

How to fix it: Celebrate promotions. Announce to the company. "Sarah Chen has been promoted to Engineering Tech Lead. She's brought great technical insight and mentorship to our team. We're excited to see her grow into this leadership role." This takes 2 minutes but signals that growth is valued.

The Often-Missed Piece: Old Role Backfill Strategy

Here's the most underestimated part of transitions: backfill. Someone leaves their role. Who does that role now?

Options:
1. Hire someone new (external hire): Takes 6-8 weeks. You have time to do a proper search. But you lose the promoted person for 2 weeks of onboarding the new person. And new person doesn't know the company culture. Good if you're building headcount. Bad if you need to fill immediately.

• 
  Promote someone else (internal move): Takes 1-2 weeks to train. Retained person knows the company. Often cheaper than external. But creates a cascade: if you promote Sarah to tech lead and promote James to senior engineer, then who does James's job? Good if you have someone ready to grow.
• 
  Hire a contractor or freelancer (temporary): Fast (1-2 weeks). Temporary (6-12 months). Flexible. But expensive (contractors cost 25-50% more than employees). Good if you need to buy time while hiring.
• 
  Redistribute among current team (no hire): No external cost. Team already knows the work. But overloads other people. Unsustainable long-term. Good if workload is light or temporary.
• 
  Leave it unfilled (accept gap): Often a mistake. Work suffers. Team is stressed. But sometimes acceptable if the role isn't critical or if you're restructuring anyway.

Decision should be made before transition.

Not after. Not during. Before. The conversation: "Sarah's being promoted. Her old role needs to be filled. Here are the options. What do we do?"

Example backfill decisions:

• 
  "Sarah promoted to tech lead. James (mid-level engineer) promoted to senior engineer to cover Sarah's role. Training overlap: 2 weeks. Done by May 31."
• 
  "Sarah promoted to tech lead. We hire new senior engineer. Start recruitment immediately. Target: new person starts June 15. Sarah trains them July 1-15. During June, team absorbs a bit of extra load. Acceptable."
• 
  "Sarah promoted to tech lead. We hire contractor for 3 months while we hire. Start contractor June 1. New hire starts August 1. Bridge the gap."

Practical Application - Plan Your Next Transition

For your next promotion or transfer:

Step 1 (Before the transition): Gather information.
- Who's being promoted/transferred?
- From what role to what role?
- What's the new manager like? (supportive? hands-off? first-time manager?)
- When does it happen?
- What about the old role?

Step 2 (Next day): Create transition plan.
- Gather the info above
- Input to transition planning system (or use template)
- AI generates the plan
- Review and customize (10-15 minutes of your work)

Step 3 (Day 2): Schedule announcement meeting.
- Include: promoted person, current manager, new manager, HR
- 1 hour, discuss the role, the plan, expectations, support
- Get alignment and buy-in

Step 4 (Day 3): Brief the team.
- Announce to old team: "Person X is moving to role Y. Here's who's covering their work."
- Announce to new team: "Person X is joining us. They bring [strengths]. They'll ramp over the next 90 days."
- Frame positively: growth opportunity, not disruption

Step 5 (Transition week): Execute the transition.
- Old role wrap-up: knowledge transfer, project handoff
- New role ramp-up: meet people, understand context, start working

Step 6 (Ongoing): Support with check-ins.
- 30 days: How's it going? On track?
- 60 days: Skills developing? Confidence growing?
- 90 days: Ready to own role independently?

Key Takeaways

• 
  Internal transitions require structured planning. Not less than external onboarding. More, in some ways, because people underestimate the complexity.
• 
  Backfill must be decided before the transition, not after. Otherwise old team suffers and you're left scrambling.
• 
  Expectations should be crystal clear. "Success at 30 days looks like X. At 60 days, Y. At 90 days, Z." Not vague. Specific. Measurable.
• 
  Support should be deliberate and ongoing. New manager should be briefed. Weekly check-ins for first month. Development activities scheduled. Context provided.
• 
  Promotions should feel like opportunity and support, not abandonment. Communicate the "why" (we think you're ready, we see growth). Celebrate the promotion (tell the company). Show path forward (what's next after this role).
• 
  Check-ins at 30/60/90 days catch problems early. If someone's struggling, you want to know at day 30, not day 90. Early support or course-correction saves everyone.
• 
  Not all promotions work. If by 90 days it's clear the transition isn't working, be willing to make a change. Moving someone back or to a different role is better than keeping them in a role they're failing at.
• 
  AI can generate transition plans, track milestones, prepare communication. Humans drive the relationships, support, and honest conversations.

FAQ

Q: How long should a transition take?
A: Depends on the jump. Lateral move (same level, same type of work): 2-4 weeks. Promotion one level: 4-8 weeks. Promotion with major responsibility change (IC to manager): 8-12 weeks. Promotion to significantly different domain: 12+ weeks. Plan for people to be ramping for at least 90 days; don't expect independence before then.

Q: Should we have overlap where the promoted person does both roles?
A: Sometimes. If the person knows both roles well and the work isn't too much, they can train backfill while starting new role. If they're going to struggle in new role, focus entirely on ramping, don't add old role work. Better to hire/promote backfill and let promoted person focus.

Q: What if promoted person wants to go back to old role?
A: Ideally this doesn't happen (means you promoted too early). But if it does, let them. Better to fix it now than have them fail in new role and be bitter. Frame it: "This role isn't the right fit right now. Let's find what is." No stigma.

Q: Do we communicate promotions externally (to customers, partners)?
A: Usually yes, but timing matters. Announce internally first. Then brief external stakeholders. "Sarah has been promoted to Tech Lead. She'll continue supporting your account and will now also help with strategic architecture questions."

Q: What if the person being promoted isn't excited?
A: This is a red flag. "You've been promoted, but you seem hesitant. Talk to me." Maybe they don't feel ready. Maybe they're worried about the people management piece. Maybe they like their old role. Better to have this conversation now than have them succeed reluctantly.

Q: How do we handle pay changes?
A: Promotion usually comes with a raise. Discuss in the announcement meeting. "Promotion includes a [X]% raise, effective [date]." Be clear. Don't make them wonder. If no raise is possible, you should say so and explain why ("We'd love to raise your pay, but we're in a hiring freeze. We'll revisit in 6 months.")

Q: What if we realize the promoted person wasn't the right choice?
A: You have a few options. (1) Extend the transition period and provide more support. Maybe they just need more time. (2) Move them to a different role that might be a better fit. Maybe tech lead wasn't right, but senior IC role is. (3) Move them back to old role with no stigma. "This transition isn't working. Your old role is still open. Let's get you back there and find a better next step." Make this conversation collaborative, not punitive.

What's Next

You've successfully transitioned the person to their new role. They're ramped up and independent by day 90. Now what? Over the next months and years, they might get promoted again. Or they might feel stalled. Or they might decide to leave. The next section covers managing careers long-term: how to create paths, recognize when people are ready to go, and build a culture where people feel seen and developed.