How do you onboard a new manager?

Give them what nobody usually does: full context on the team they are inheriting (people, history, dynamics, commitments), explicit expectations of the manager role here, training on the company's actual management mechanics (one-on-ones, reviews, comp cycles), and a 30-60-90 built around listening before changing.

Why is manager onboarding usually bad?

Because companies assume seniority means self-sufficiency. A new manager gets a team and a calendar of meetings, but no briefing on the people, no documentation of how management works here, and no support for the identity shift from doing the work to leading it. The cost lands on the whole team, not just the manager.

What should a new manager do in the first 30 days?

Listen. One-on-ones with every report, the manager's own manager, and key peers; learn the team's current commitments and pain points; change almost nothing. Early sweeping changes before context is the classic new-manager failure.

Is onboarding different for promoted versus hired managers?

The gaps differ. A promoted manager knows the company but must renegotiate relationships with former peers and shed the IC identity. A hired manager knows management but not the company's people, history, or mechanics. Both need structured onboarding; they need opposite halves of it emphasized.

Employee onboarding

New Manager Onboarding: The First 90 Days of Leading a Team

Sakha TeamJune 5, 202610 min read

New managers are the most under-onboarded people in most companies. The assumption is that seniority means self-sufficiency, so the new manager gets a team, a calendar full of one-on-ones, and silence, while the company quietly runs an experiment on every person who reports to them. Manager onboarding deserves more structure than IC onboarding, not less, because the blast radius of a struggling manager is the whole team. Here is what the structured version looks like. For the practices the manager will be expected to embody, see our employee onboarding best practices.

Why this onboarding fails by default

Three missing pieces, repeatedly:

No team briefing. The manager inherits people with histories, dynamics, in-flight commitments, and sensitivities, and learns all of it by stepping on it.
No mechanics manual. How one-on-ones, reviews, comp cycles, and promotions actually work here lives in other managers' heads. The new manager improvises in front of their reports.
No support for the identity shift. Especially for promoted ICs: the skills that earned the promotion (doing the work excellently) are precisely what they must now stop leaning on. Nobody says this out loud, so they learn it through the team's frustration.

What the structured version includes

Component	What it covers
Team briefing	Each report's role, history, strengths, growth areas, current work
Commitments map	What the team has promised, to whom, by when
The mechanics manual	How 1:1s, feedback, reviews, comp, and escalation work here
Expectations	What this company means by "manager," stated explicitly
A manager buddy	An experienced peer manager for the how-do-I-actually questions
A listening-first 30-60-90	Structure that prevents the change-everything instinct

The manager's 30-60-90

Days 1 to 30: listen. One-on-ones with every report (their goals, their friction, what to keep doing), the manager's own manager, and key peers. Learn the commitments before touching them. Change almost nothing: early sweeping changes before context is the signature new-manager failure, and the team is watching for it.

Days 31 to 60: calibrate. Settle the operating rhythm (one-on-one cadence, team meetings, how decisions route), give first real feedback in both directions, make the first small, well-explained changes where listening showed clear wins.

Days 61 to 90: own. The team's goals are now the manager's goals, articulated forward; underperformance is being addressed rather than observed; the manager's manager gets a point of view, not just status.

The structure is the standard 30-60-90 with the themes shifted from learn-contribute-own to listen-calibrate-own.

Promoted vs hired: opposite gaps

A promoted manager has the company context and lacks the role: the peer-to-boss renegotiation, the identity shift, the permission to stop being the best IC. A hired manager has the role and lacks the company: the people, the history, the unwritten mechanics. Run the same program, but weight the briefing and mechanics for the external hire, and the expectations and transition support for the internal one. The general hired-manager case also gets the full standard onboarding underneath.

How Sakha onboards managers

Sakha runs a manager-specific flow alongside the standard one: the team briefing delivered before day one, the mechanics manual (how one-on-ones, reviews, and comp actually work here) queryable in Slack the moment a question arises, the listening-first milestones scheduled with check-ins that actually fire, and the expectations of the role stated in writing rather than discovered by friction. The questions new managers are most reluctant to ask out loud ("how do I run a performance conversation here," "what is the promo process") get answered privately, instantly, from your documented knowledge, with the knowledge base doing for managers what it does for every other hire: removing the gap between needing to know and knowing.

Curious how Sakha runs onboarding inside Slack? See how it works.