The signal
Their return date is on the calendar. You haven't planned anything specific. That's the problem.
What it really means
They are anxious about being behind, irrelevant, or forgotten. They need a runway, not a sprint.
Your first response
Reach out a week before their return. Set up a re-onboarding plan as if they were a new hire — because in many ways they are.
The Playbook
1. Plan the first two weeks
- Block their calendar — no big commitments, no on-call, no interviews.
- Schedule context-setting 1:1s with key collaborators.
- Hand them a short, scoped piece of work to land an early win.
2. Re-baseline expectations
- Talk openly about what's changed: team, roadmap, tools, people.
- Reset goals together — don't assume the old ones still fit.
- If they've changed (and they have), make space for that.
3. Protect them from catch-up pressure
Catch-up is a myth. Define what mastery looks like in 60-90 days and let them build toward it without comparison to peers.
Things you can actually say
“Welcome back. The team missed you. I don't want you to feel like you're starting from behind — we've built in real ramp time. Let's plan the next two weeks together, and you tell me what you need.”
What to avoid
- — Treating their first week as if they never left.
- — Putting them on on-call in week one.
- — Pretending the team and codebase haven't changed.
The follow-through
- Check in weekly for the first 6 weeks.
- Revisit comp, level, and trajectory — leave should not stall a career.