Becoming a manager of managers is one of the biggest transitions in an engineering leadership career. The skills that made you a successful front-line manager - close relationships with individual engineers, hands-on involvement in technical decisions, and direct team facilitation - are no longer sufficient. This guide helps you develop the strategic, coaching, and organisational skills needed to lead through other leaders.
Understanding the Fundamental Shift
As a manager of managers, your impact is multiplied through the managers who report to you. Every improvement you make in their leadership capability cascades to their entire team. Conversely, every problem you fail to address in a manager affects dozens of engineers. This leverage is both the greatest opportunity and the greatest responsibility of the role.
Your relationship with the technical work changes fundamentally. You are no longer making day-to-day technical decisions - your managers are. Your role is to ensure they have the context, skills, and support to make good decisions. Resist the urge to skip levels and make technical calls directly; it undermines your managers and does not scale.
Your time horizon shifts from weeks to quarters and years. While front-line managers focus on sprint-level execution, you need to think about organisational structure, capability building, strategic alignment, and long-term team health. This shift in perspective is essential for effectiveness at this level.
Developing Your Direct Report Managers
Your primary job is to develop your managers. Spend the majority of your one-on-one time coaching them on their management challenges: how to give difficult feedback, how to navigate organisational politics, how to build team culture, and how to make strategic decisions.
Provide frameworks and principles rather than prescriptive solutions. When a manager brings you a problem, guide them through the thinking process rather than telling them what to do. 'What have you considered?' and 'What are the trade-offs you see?' are more developmental than 'Here is what I would do.'
Create learning opportunities for your managers. Cross-functional projects, exposure to senior leadership, conference attendance, and management peer groups all help them develop the skills they need. Invest as deliberately in their growth as you expect them to invest in their engineers' growth.
Embracing Strategic Responsibilities
At this level, you are responsible for the overall health and direction of your engineering organisation. This includes team structure, hiring strategy, technical roadmap alignment, cross-team collaboration, and culture. These are not tasks to be completed but ongoing responsibilities that require constant attention.
Build strong relationships with your peers in product, design, and other engineering groups. At the manager-of-managers level, cross-functional alignment becomes a significant part of your job. The decisions you make about team structure, priorities, and resources need to be coordinated with the broader organisation.
Develop a point of view on where your organisation needs to go. What capabilities need to be built? What structural problems need to be addressed? What culture shifts are necessary? Your managers are focused on execution - you need to be focused on direction.
Maintaining Connection Without Micromanaging
Skip-level meetings, team demos, and architectural reviews keep you connected to the work without bypassing your managers. These touchpoints give you direct insight into team health, technical quality, and individual talent that complement the information you receive from your managers.
Trust but verify. Give your managers autonomy to lead their teams, but use metrics, skip-levels, and your own observations to ensure that things are going well. If you notice issues, raise them with your manager as coaching opportunities rather than intervening directly.
Be visible and accessible to the broader organisation. Engineers who never see their skip-level manager feel disconnected from leadership. Attend team events, drop in on standups occasionally, and be present in organisational communications.
Common Pitfalls for New Managers of Managers
The most common pitfall is continuing to operate as a front-line manager - making detailed technical decisions, having one-on-ones with individual engineers, and managing projects directly. This prevents you from doing the strategic work the organisation needs and undermines your managers.
Another pitfall is losing touch with the ground truth. If you only hear about team health through your managers' reports, you miss problems they do not see or choose not to share. Maintain independent channels of information through skip-levels, metrics, and direct observation.
Failing to address underperforming managers is perhaps the most damaging pitfall. A struggling manager affects their entire team, and the impact compounds over time. Have difficult conversations early, provide support and coaching, and make hard decisions when coaching is not enough.
Key Takeaways
- Your impact is now multiplied through your managers - developing them is your primary job
- Shift your focus from sprint-level execution to quarterly and annual strategic thinking
- Coach your managers by providing frameworks and guiding their thinking rather than prescribing solutions
- Maintain connection to ground truth through skip-levels, metrics, and direct observation without micromanaging
- Address underperforming managers quickly - their impact on the organisation is outsised
Frequently Asked Questions
- How do I handle a situation where my manager is making a decision I disagree with?
- Share your perspective and reasoning, but if the decision is within their authority and not clearly wrong, let them make it. Your managers need room to make decisions - and occasionally mistakes - in order to grow. If the decision carries significant risk, ask probing questions that help them see the risks without overriding their judgement. Reserve your override authority for decisions that could cause serious harm.
- How do I stay technically relevant as a manager of managers?
- Accept that your technical depth will naturally decrease, and that this is appropriate for your role. Stay technically aware through architecture reviews, technical strategy discussions, and reading your teams' design documents. You do not need to be able to write code in your teams' codebases - you need to understand the technical landscape well enough to ask good questions and evaluate proposals.
- How many managers should I directly manage?
- Three to six managers is a typical range. Fewer than three may not justify the role; more than six makes it difficult to provide adequate coaching and support. The right number depends on the complexity of each manager's scope, how experienced they are, and what other responsibilities you have. New managers need more support; experienced managers need less.
Explore Leadership Development Resources
Access our field guide for engineering leadership development, including manager coaching frameworks, organisational design principles, and strategic planning templates.
Learn More