90‑Day Engineer‑to‑Manager Transition Plan: From Code to Leadership

Why You Need a Plan

David Loftesness, former engineering director at Twitter, argues that a time‑boxed, flexible plan is crucial for engineers transitioning to management because most new managers lack formal training and rely on trial‑and‑error.

Three Independent Phases

The 90‑day plan is split into three stages: Day 0 – Foundations , Day 1‑30 – Build Your Knowledge Base , Day 31‑60 – Find Your Rhythm , and Day 61‑90 – Self‑Assessment . Deciding whether to accept the management role is the hardest part.

Day 0: Things You Must Know

New managers often have deep technical expertise but no leadership experience. Loftesness stresses the importance of honest self‑reflection about motivations and readiness.

Key Questions Before You Start

Can you lead the engineers who were once your peers?

Can you communicate effectively with other managers?

Can you report project status clearly to senior leadership?

Answering these indicates whether you are prepared for the shift from coder to manager.

Day 1‑30: Own Your Education

Reserve dedicated time for management learning, read recommended books (e.g., "Peopleware", "The Mythical Man‑Month", "Break the Rules"), and make this time visible to your team.

Find one or two mentors outside your direct line manager; seek advice from experienced leaders in other groups.

Day 31‑60: Find Your Rhythm

Re‑structure your schedule to protect time, cancel unnecessary meetings, and prioritize one‑on‑ones with engineers early or late in the day to minimize disruption.

Create an “event‑loop” checklist reviewed weekly and monthly to ensure critical tasks are not missed.

Day 61‑90: Self‑Assessment

Evaluate whether you can clearly articulate key reports, whether you truly want to stay in management, and whether you understand each team member’s unique strengths.

Assess software quality, achievement of individual goals, team morale, and your own work‑life balance.

Decision Point at Day 90

After 90 days, decide to continue or step down. If you feel the role aligns with your motivations and you can sustain the workload, move forward; otherwise, treat the transition as a learning experience and consider returning to a technical path.

Beyond 90 Days

Focus on amplifying strengths rather than fixing weaknesses, differentiate personality from performance, and identify trusted advisors who can give candid feedback.

Ultimately, fully commit to management the way you once committed to coding, avoiding the trap of being a jack‑of‑all‑trades.