New Manager's 30-Day Blueprint
Anton Martyniuk shared actionable first-30-days tips for new engineering managers to build credibility quickly. The blueprint includes scheduling 1:1s, shipping small wins, studying postmortems, understanding decision-making processes, and defining success metrics. Discussions focus on transitioning from individual contributor to leader with emphasis on building trust fast.
The transition from individual contributor to engineering manager is notoriously challenging, with some industry leaders estimating that at least half of newly-promoted managers leave the role. This high failure rate is often attributed to the shift from a technical "maker" mindset to a people-focused "multiplier" mindset, a transition for which many engineers receive little formal training. A new manager's calendar reflects this seismic shift in responsibilities. Time spent on coding and deep technical work decreases significantly, replaced by a schedule dominated by meetings. Some reports show engineering managers spend 25-35% of their time in one-on-one meetings and up to 50% in other meetings with peers and stakeholders, leaving little time for hands-on technical tasks. The emphasis on regular one-on-one meetings is a cornerstone of effective management, directly impacting team stability and engagement. Research has shown that employees who have weekly check-ins with their managers are three times more likely to be engaged at work. Furthermore, consistent 1:1s can reduce employee turnover by as much as 30%, highlighting their importance in building trust and open communication. "Shipping small wins" is a tactic to build momentum and team morale. These wins don't have to be major feature releases. They can include process improvements like reducing build times, resolving a recurring bug, or enhancing documentation. Celebrating this incremental progress can trigger dopamine releases that reinforce positive behaviors and boost team engagement. Studying postmortems is a key practice for building a "blameless" culture, which is crucial for psychological safety and continuous improvement. The goal of a blameless postmortem isn't to assign fault to individuals but to identify systemic weaknesses and process gaps that contributed to an incident. This approach encourages open dialogue and learning from failures, which can lead to more resilient systems and better team collaboration. Anton Martyniuk, the author of the blueprint, is a Microsoft MVP and Technical Lead with over a decade of experience in .NET development and software architecture. His advice stems from extensive hands-on experience leading and mentoring engineering teams, giving his 30-day plan a foundation in real-world practice.
