Manager Onboarding: The Missing Program in Most Companies
Companies onboard individual contributors with care and onboard new managers with a one-pager. The result is two quarters of avoidable team damage.
On this page▾
- A new manager is doing a different job; they need a different onboarding.
- Three priorities for the first 90 days: listen, stabilise, set the bar.
- Skip-levels in weeks 2–4 are the most valuable single ritual.
- Set the first change after day 60, not day 7.
When a senior engineer becomes a manager, or an external hire takes over a team, the team has a productivity cliff that lasts roughly two quarters. Most of it is avoidable. The cause is not lack of skill — it is lack of structure. Companies spend weeks designing onboarding for an individual contributor and ship new managers a Slack channel and a wish of luck.
Why managers need a separate program
An IC onboards into a defined scope: a codebase, a territory, a process. A manager onboards into people — and people are not a codebase. The job is to understand a system of relationships, history, capabilities, and trust before changing anything. Treating that as 'figure it out' is the most common cause of team damage from a leadership change.
The first-90-days operating model
- 1Days 1–30: listen1:1 with every direct, a skip-level with every direct's direct, meetings with cross-functional partners. No changes. Pure intake.
- 2Days 31–60: stabiliseDocument what you have learned. Confirm the team's existing commitments. Fix any genuinely broken process (1:1s not happening, no roadmap visible).
- 3Days 61–90: set the barIntroduce the first deliberate change. Communicate the operating model you intend to run. Begin performance conversations.
Re-orging the team in week 2. The new manager has not yet earned the right to make that move and does not have the data to make it well. Even when the re-org is correct, the timing kills its legitimacy.
Three rituals that compound
- Skip-levels in weeks 2–4 with every indirect report — the highest-fidelity intake the manager will ever do.
- A written 'how I work' document shared in week 4: decision style, meeting expectations, what they want to be told vs left alone.
- A 60-day retrospective with their own manager: what they have learned, what they will change, what support they need.
Where HR adds the most value
- Brief them on the team's people history before day 1 (recent attrition, ER cases, pending PIPs).
- Pair them with a peer manager mentor for the first 90 days.
- Run a manager cohort onboarding program if you hire more than 4–5 managers a year.
- Block the first calibration meeting from being their first performance decision — they need data first.
Read next
All playbooksA blueprint for pre-boarding, week one, and the first 90 days — built around the moments that decide whether someone stays.
The structural reasons VP+ hires fail at 18 months, the listening tour vs. quick-win debate, and the founder's role in the first 30 days.
The honest field manual for engineers stepping into leadership — first-time tech leads, engineering managers, CTOs, and founder-CEOs.