liveBook · Manning

30-60-90-day plan

As explained in Think Like a Software Engineering Manager

A staged plan defining objectives, activities, and milestones for a person's first thirty, sixty, and ninety days in a role or transition.

Moving from individual contributor (IC) to engineering manager (EM) takes more than a change in title. A 30-60-90-day plan gives you and your manager achievable milestones for the transition. Agree on the plan before stepping into the role, then use the roughly 90-day period to assess your fit, identify skill gaps, and discuss how you are adapting. section 2.4.1

Keep the plan grounded in conversations and achievable goals:

  • Discuss your motivations, strengths, and weaknesses with your manager before setting time-bound goals. section 2.6
  • Meet regularly to review milestones, share feedback, and recognize progress. section 2.6
  • Clarify how performance will be evaluated and what happens if the transition is not a fit, including whether returning to an IC role is possible. section 2.4.1

An early relationship-building activity

Write down the names of the engineers you will manage and arrange a one-on-one with each. Ask what is working, what hurts, and whom else you should meet. Those conversations can reveal team strengths and areas for improvement. They are a useful activity to consider for a plan, not a prescribed day-30 milestone. section 2.6

The same time frame can structure a new hire’s onboarding plan. In that setting, pair the plan with an onboarding buddy, frequent one-on-ones, and access to training materials. What achievable milestone would help you judge progress in your own transition? section 7.1.5

Figure 7.1 Sample onboarding plan for new hires
figure

A sample onboarding-plan template provides an artifact for considering the new-hire version of this time frame. section 7.1.5

How Think Like a Software Engineering Manager covers it

How deep it goes
Outlines collaborative goals and milestone reviews without prescribing separate objectives for days 30, 60, and 90.
Examples
Illustrates early relationship-building through one-on-ones with engineers and their suggested contacts, and provides a sample onboarding-plan template.
What you can do after
Practice/perform it by agreeing on achievable, time-bound milestones and reviewing progress with a manager.
How it connects
Connects the plan to gap analysis, one-on-one meetings, feedback, and onboarding.

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.