liveBook · Manning

Transition period

As explained in Think Like a Software Engineering Manager

A transition period is a bounded interval in which a person or organization moves into a new state and adapts to its responsibilities and expectations.

A transition period is the time set aside to move into a new role or leadership arrangement and adapt to its expectations. For an individual contributor becoming an engineering manager, a defined timeline is typically 90 days to six months. Agree with your manager and company leaders on what success in the new role means. section 2.4.2

Make the transition concrete:

  • Use a company leveling guide to identify the responsibilities you will be measured against. If there is no clear guide, develop a comparable framework with your manager. section 2.4.2
  • Keep a living record of your work and how it meets those responsibilities. Validate it with your manager, especially if expectations are unclear or inconsistent. section 2.4.2
  • Meet team members one-on-one to learn their motivations, aspirations, concerns, and expectations. Build trust before assuming they will share openly. section 2.4.2 section 13.3.1
  • When taking over an existing team, assess its practices before changing them. Coordinate responsibilities, timelines, knowledge transfer, and documentation with the outgoing and incoming leaders. section 13.3.1
  • Communicate goals and expectations clearly, invite questions and feedback, and give people time to adapt. section 13.3.1

Making progress visible

Managing summer interns may count as people-management work. Record that responsibility and check with your manager how it aligns with engineering manager expectations. A typical 90-day probationary period gives you a useful point at which to review that alignment. section 2.4.2

An official move may be delayed by company size or a lack of openings. Use the waiting time for further research and preparation rather than treating it as the transition itself. section 2.4.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides timelines and practical steps for role alignment and leadership handover, without specifying a fixed plan for every organization.
Examples
Uses managing summer interns as evidence of people-management work and joining an existing team as a leadership-handover scenario.
What it assumes
Assumes preparation and information gathering before an engineering manager transition, while spelling out practical steps for a leader joining an existing team.
What you can do after
Practice/perform a transition by agreeing on success criteria, tracking relevant work, building relationships, and planning a leadership handover.
How it connects
Connects role expectations, leveling guides, one-on-one meetings, knowledge transfer, and change management.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.