Structure the first 90 days of the new manager transition

The first thirty days are defined by the shift in relationship dynamics. New managers must openly address the transition with former peers rather than pretending nothing has changed. They also need to establish 1:1s that go beyond simple status updates, listening for early signals of burnout or misalignment before they escalate.

• →Coach managers to explicitly name the transition in their first 1:1 with a former peer
• →Audit early 1:1 agendas to ensure they cover development and blockers, not just ticket updates
• →Have managers agree working preferences and development priorities with each direct report

By month two, the temptation to fall back into IC work peaks, especially under deadline pressure. The new manager must learn to hand off the work they used to own to their team. This requires briefing clearly, delegating the outcome rather than the keystrokes, and resisting the urge to step in and fix things themselves.

• →Identify the IC tasks the manager is still holding and agree a practical handoff plan
• →Practice briefing a capable report on a new project without dictating the exact execution steps
• →Review team capacity to ensure the manager is not becoming the bottleneck for approvals

In the final month of the onboarding window, the manager faces their first real tests of authority. They must deliver specific, kind, and early corrective feedback to a report whose work is slipping. Simultaneously, they must learn to protect their team's focus by pushing back on scope creep from insistent staff engineers or product managers.

• →Rehearse delivering a piece of corrective feedback without softening the core message
• →Establish a framework for evaluating inbound requests against the team's current OKRs
• →Practice offering a concrete tradeoff when saying no to a senior stakeholder's request