First-Time Engineering Manager: Your 90-Day Plan

For a first-time engineering manager, the initial 90-day period is critical for transitioning from an individual contributor to an effective leader, establishing credibility, and building a foundation for long-term success. This strategic onboarding phase demands a deliberate shift in focus, prioritizing active listening, relationship building, and understanding team dynamics over immediate technical contributions. A structured 90-day plan provides a practical framework to navigate this fundamental change, ensuring the new manager can effectively lead their team and manage stakeholder expectations.

The Fundamental Shift: From Individual Contributor to Leader

The transition from an individual contributor (IC) to an engineering manager demands a fundamental shift in mindset and operational focus. As an IC, success is largely measured by personal technical output—code contributions, design documents, and project completion. As a manager, the core job is to deliver results through people, necessitating a pivot from individual output to team enablement and performance. This involves five key responsibilities: setting direction, building systems, developing talent, communicating effectively, and removing obstacles.

A significant change lies in communication and stakeholder management. While an IC might spend 80% of their time with their engineering team, an engineering manager often dedicates only 50% of their time to engineers. The remaining 50% is spent engaging with cross-functional stakeholders such as product, design, UX, QA, people operations, and customer support. This expanded network requires building trust and rapport quickly across various disciplines to ensure team success. The initial 90 days are crucial for this reorientation, helping new managers navigate the increased scope and the shift from technical problem-solving to leadership and team building.

Laying the Foundation: Days 1-30 for the New Manager

The initial 30 days are dedicated to active listening, observation, and building foundational relationships. A new engineering manager's primary goal is to "Own Your Education," understanding the team's existing dynamics and the organizational landscape before proposing significant changes. This involves conducting structured 1:1 meetings with every direct report to understand their background, career aspirations, frustrations, and ideas. Key questions during these 1:1s should include: "What's going well?", "What's frustrating or slowing you down?", and "What do you need from me to succeed?" This approach helps identify individual motivations, strengths, and preferred working styles, while also assessing the team's psychological safety.

Beyond direct reports, the new manager must meet with key stakeholders such as Product Managers, Design Leads, QA, other Engineering Managers, and senior leadership. During these interactions, inquire about what's working well, areas needing improvement, and their expectations for your team. Concurrently, immerse yourself in the technical and product context by requesting product demos, reviewing architecture documentation, and shadowing engineers to grasp workflows. Evaluate current processes, including sprint rituals, code review practices, and deployment procedures. Identifying and removing small blockers, such as tooling access issues or meeting clutter, can serve as "quick wins," demonstrating immediate value and building trust without heavy-handed intervention. By the end of this period, the manager should have a clear picture of team health, strengths, gaps, and alignment with broader company goals, which should be shared with leadership.

Building Momentum: Days 31-60 for the New Manager

Having completed the initial learning phase, the new engineering manager now shifts focus to "Find Your Rhythm," influencing team operations and clarifying expectations. The primary goal for this period is to align the team's vision and goals with broader organizational objectives. This involves collaborating with product leadership to translate company objectives into actionable team-level OKRs or specific goals. For instance, if a company objective is "Increase user engagement by 15%," the team's OKR might be "Launch A/B tested feature X leading to a 5% uplift in daily active users."

Establishing clear working agreements is crucial for team cohesion and performance. This includes defining norms around communication channels (e.g., expected Slack/email response times), meeting etiquette (e.g., starting and ending on time, clear agendas), and technical practices such as code review standards and testing methodologies. These agreements foster a predictable and psychologically safe environment, which is vital for team building and career development. By proactively defining these expectations, the new manager, now a technical leader, ensures that individual contributions align with collective goals, moving beyond the individual contributor mindset to one of team enablement. This phase is critical for solidifying the manager's leadership and setting the stage for sustained success.

Consolidating Impact: Days 61-90 for the New Manager

The final phase of the 90-day plan, "Assessing Yourself," focuses on solidifying gains and strategizing for future growth. By this point, the engineering manager should have a clear understanding of team dynamics and established initial working agreements. The primary task is to conduct a comprehensive review of the progress made and provide constructive feedback to direct reports. This involves revisiting the initial 1:1 discussions from days 1-30 to assess individual and team growth against identified goals and aspirations.

Managers should prepare for continuous career development discussions, moving beyond immediate tasks to long-term professional trajectories. This includes identifying specific areas for skill enhancement within the team, such as advanced testing methodologies or new architectural patterns, and aligning these with project needs. Strategically, this period is crucial for refining team processes, perhaps by implementing a new retrospective format or streamlining the deployment pipeline based on observations and team feedback. The manager, now a more seasoned technical leader, also needs to prepare a summary of their observations and initial impact for senior leadership, outlining key achievements, ongoing challenges, and a strategic roadmap for the next quarter. This proactive communication reinforces credibility and demonstrates a clear vision for the team's future.

Essential Tools for Success: 1:1s and Stakeholder Management

Effective 1:1 meetings are paramount for a new engineering manager, fostering psychological safety and understanding individual motivations. These should be structured, consistent, and safe spaces for direct reports to discuss career development, frustrations, and ideas. A simple format includes asking: "What's going well?", "What's frustrating or slowing you down?", "What should we stop/start doing?", "What do you need from me?", and "What are your goals for the next 3-6 months?". Taking detailed notes and identifying patterns across these conversations is crucial. Common 1:1 mistakes to avoid include canceling frequently or allowing the conversation to become a status update.

Beyond direct reports, stakeholder management is critical. As an individual contributor, an engineer might spend 80% of their time with their engineering team; as an engineering manager, this shifts to approximately 50%, with the remaining time dedicated to cross-functional stakeholders. These include product managers, designers, QA, other EMs, and leadership, as well as teams like people ops, recruiting, platform, and customer support. Building rapport and trust with these diverse groups is essential, as team success hinges on alignment toward common goals. Proactively meeting these stakeholders to understand their expectations, what's working well, and what isn't, provides invaluable context and builds crucial alliances for the new manager.

Frequently Asked Questions

Conclusion

Navigating the first 90 days as an engineering manager is a critical period for establishing trust, understanding team dynamics, and setting the stage for future success. By focusing on active listening, strategic questioning, and consistent feedback, new managers can effectively transition from individual contributor to impactful leader. This foundational work is essential for building a high-performing and motivated engineering team.

Sources & References

• Engineering Manager 90 day plan - Andy Hansen
• The First 90 Days as an Engineering Manager: A Technical Leader's ...
• This 90-Day Plan Turns Engineers into Remarkable Managers
• Your First 90 Days as a new Engineering Manager - Udemy
• 90 days as Engineering Manager | LeanIX Engineering
• eBook - First 90 Days as Engineering Manager
• The 30–60–90 Day Plan for New Managers (A Practical ... icpm.net https://icpm.net › Blog/News
• American Society for Engineering Management - Key Focuses For New Engineering Managers
• A Checklist For First-Time Engineering Managers - The Pragmatic Engineer