Days 1-30: Listen and Learn
Your instinct will be to fix things immediately. Resist it. Spend the first month understanding: team dynamics, existing processes, technical landscape, stakeholder relationships, and unspoken cultural norms. Schedule 30-minute 1:1s with every team member. Ask: "What's working well? What's broken? What would you change?" Take detailed notes. You'll spot patterns — usually 2-3 themes emerge that everyone mentions. These are your first priorities.
Running Effective 1:1s
1:1s are your most important tool. Weekly, 30 minutes, never canceled. This is their meeting, not yours — let them set the agenda. Listen more than you talk (aim for 70/30 split). Ask open-ended questions: "How are you feeling about the project?" "What's your biggest blocker?" "What would make your job easier?" Track action items and follow through — nothing destroys trust faster than forgotten promises. Over time, 1:1s should cover career growth, not just project status.
Days 31-60: Build and Adjust
Based on your listening tour, identify 1-2 process improvements. Propose changes collaboratively: "I noticed X is a pain point. Here's an idea — what do you think?" Don't impose changes top-down. Start setting expectations: response times for code reviews, sprint commitments, on-call responsibilities. Create a team working agreement — written norms that everyone agrees to. Small wins build credibility: fix a broken CI pipeline, resolve a long-standing blocker, or remove an unnecessary meeting.
Days 61-90: Drive Outcomes
By now you should have trust, context, and initial process improvements. Focus on: (1) Aligning team work with business objectives, (2) Establishing a sustainable sprint cadence, (3) Creating growth plans for each team member, (4) Building relationships with product, design, and other engineering teams. Start representing the team in cross-functional planning. Shield the team from unnecessary interruptions while keeping them informed of important decisions.
The IC-to-Manager Transition
The hardest shift: your dopamine now comes from others' achievements, not your own code. Reduce coding to 20% — enough to stay technical, not enough to become a bottleneck. Never take critical path work — you'll get pulled into meetings and block the team. Review PRs to stay connected to the codebase. It's okay to feel less productive — your job changed from producing output to multiplying it. A team of 5 doing 10% better is worth more than your individual contribution.
Common New Manager Mistakes
Hero coding: Taking on the hardest tasks yourself instead of growing your team. Avoiding tough conversations: Feedback doesn't get easier with time — address issues early. Being everyone's friend: You need trust, not friendship. Sometimes you'll make unpopular decisions. Micromanaging: Define outcomes, not how to achieve them. Ignoring your own development: Read management books, find a mentor, join EM communities. Management is a skill that requires deliberate practice.
Resources for New Managers
Books: "The Manager's Path" by Camille Fournier, "An Elegant Puzzle" by Will Larson, "Radical Candor" by Kim Scott. Communities: Rands Leadership Slack, Engineering Managers Slack. Podcasts: "Engineering Culture" by InfoQ, "Level Up Engineering" by Coding Sans. Find a management mentor — someone who's been an EM for 3+ years at a similar-sized company. The first year is the hardest; it gets better with experience and practice.