The data on managers is clear and consistent across every major study: the manager is the single highest-leverage role for team performance. Gallup says 70% of the variance in team engagement stems directly from the manager (Gallup). Google's Project Oxygen proved that teams with strong managers performed better, were happier, and stayed longer (Google re:Work). Employees in companies with ineffective management are nearly 60% more likely to experience stress.
And yet. Most new engineering managers receive zero training before or during their first year. They are promoted because they were great individual contributors, then left to figure out a completely different skill set on their own. 60% of new managers fail within their first two years. The gap between "knowing what good management looks like" and "doing it consistently" is enormous.
This article is about closing that gap. Here are the specific practices that research says separate great engineering managers from the rest.
Practice 1: High-Quality Weekly 1:1s
This is the single most important habit. Gallup found that employees with regular meaningful one-on-ones are almost three times as likely to be engaged as those without them. 86% of highly engaged organizations use regular 1:1s, compared to only 50% of disengaged companies (PerformYard).
The standard: 30 minutes, weekly, employee-driven. The employee prepares the agenda and sends it in advance. The manager leaves time for their own topics but lets the report set the direction. This is a coaching conversation, not a status update. If you are spending the entire 30 minutes on project updates, you are wasting the highest-leverage meeting on your calendar.
What to cover: blockers and workload (5 minutes), growth and development (10 minutes), feedback in both directions (10 minutes), action items (5 minutes). The key principle from Gallup: 80% of employees who received meaningful feedback in the past week are fully engaged. Weekly 1:1s are where that feedback happens.
We go deep on the specific template and question structure in the 1:1 meeting template for engineering managers.
Practice 2: Structured Delegation With Context
Delegation is where most engineering managers struggle first. The IC-to-manager transition means letting go of the work you were best at and entrusting it to people who will do it differently than you would. Research shows effective delegation requires entrusting authority along with responsibility, giving team members actual decision-making power (DEV Community).
Use the Task Readiness Maturity (TRM) framework. For team members with low task readiness: be prescriptive about how, provide detailed instructions, check in frequently. For medium readiness: shift from prescribing to facilitating, provide support and advice as the task progresses. For high readiness: share the outcome and constraints, set high standards, then step back (The Engineering Manager).
The critical difference between bad delegation and good delegation: context. Share why the work matters, who cares about the outcome, and what could go wrong. When people have context, they make better decisions and need less oversight. When they only have the task, they come back to you for every judgment call, and you end up doing the work by proxy.
Practice 3: A Regular Feedback Cadence
Most managers give feedback twice a year during performance reviews. That is like a coach who only gives notes at the end of the season. Research on skill development is clear: shorter feedback loops produce faster improvement.
Google's Project Oxygen identified "is a good coach" as the number-one behavior of great managers (Medium/WorkMatters). Coaching requires timely, specific feedback delivered in the context of the work. A weekly 1:1 creates the container. The practice of giving one piece of positive and one piece of constructive feedback per week creates the habit.
The framework: SBI (Situation, Behavior, Impact). "In yesterday's architecture review (situation), you pushed back on the proposed schema change with a clear alternative (behavior), which caught a performance issue before it hit production (impact)." Specific, timely, anchored to observable behavior. Not "you are doing great" or "you need to improve your communication."
Feedback also needs to flow upward. Teams with high psychological safety have a 34% lower rate of emotional exhaustion than those without it (APA, 2024). If your reports cannot give you feedback, you have a psychological safety problem, and you are flying blind on your own performance as a manager.
Practice 4: Team Health Visibility
Most engineering managers have real-time dashboards for code velocity, deployment frequency, and incident counts. Almost none have equivalent visibility into team health. This is a massive blind spot, because Gallup's data shows that engagement (a proxy for team health) predicts performance outcomes more reliably than any engineering metric.
What to track: participation patterns (who is contributing, who has gone silent), energy levels (are people showing up engaged or going through the motions), workload distribution (is the work spread evenly or concentrated on a few), and relationship quality (are people collaborating or siloed). These signals are hard to read through code metrics alone. They surface in 1:1s, in team interactions, and in behavioral patterns over time.
Global manager engagement fell from 30% to 27% in Gallup's 2025 data, with managers under 35 dropping five points and women managers dropping seven (Inclusion Geeks, 2025). Managers cannot address problems they cannot see. Building systematic team health visibility is how you catch disengagement, burnout, and trust erosion before they become resignations.
Practice 5: Skip-Level Conversations
Skip-levels (meetings between a manager and their reports' reports) serve two purposes: they give you ground truth about what is happening on the team, and they give individual contributors access to leadership context they would not otherwise have.
Run them quarterly, 20 to 30 minutes each. The format is simple: "What is going well? What is not? What should I know that I might not?" The signal-to-noise ratio is high because people in skip-levels are often more candid than they are with their direct manager. You will hear things in skip-levels that never surface in your regular 1:1 chain.
The caveat: never use information from skip-levels to undermine the middle manager. The purpose is to calibrate your understanding of team health, not to micromanage. If you hear a concern, coach the middle manager on addressing it, do not address it yourself over their head.
Practice 6: Decision Delegation Frameworks
Beyond task delegation, great engineering managers are explicit about how decisions get made. Ambiguity about who owns a decision creates paralysis, resentment, and rework.
A simple framework: for each significant decision, declare whether it is a Type 1 (irreversible, high-stakes, needs consensus) or Type 2 (reversible, can be made quickly by whoever is closest to the problem). Most engineering decisions are Type 2, but most teams treat them as Type 1, which slows everything down.
For each decision, be explicit: "You own this. Make the call and inform the team." Or: "This needs broader input. Let us discuss in the next architecture review." The clarity itself is the value. Research shows that lack of control is one of Maslach's six drivers of burnout (PMC, 2016). Giving people clear authority over defined decisions directly addresses the autonomy need.
Practice 7: Invest in Your Own Development
Manager engagement is in freefall. Gallup's 2025 data shows managers had the steepest decline in engagement of any worker category. You cannot pour from an empty cup, and the data says most managers' cups are draining fast.
What helps: peer cohorts (other engineering managers you can learn from), coaching (see our analysis of when you need a leadership coach), structured learning (the best leadership courses for new managers), and practice environments.
The gap in most manager development is the last one: practice. A meta-analysis by Lacerenza et al. (2017) of 335 studies found that leadership training with practice-based components significantly improves outcomes, while classroom-only approaches have limited impact. You can read every management book and still be bad at the 1:1 where someone tells you they are burned out, the meeting where two engineers are in conflict, or the conversation where you need to deliver hard feedback to a strong performer.
The Practice Gap: Why Reading Is Not Enough
Here is the core problem. Every practice in this article is well-documented. The research is available. The frameworks are published. And yet, Gallup's engagement numbers are declining. Google published Project Oxygen's findings a decade ago, and most companies still promote engineers to managers without training.
The reason is that management is a performance skill, not a knowledge skill. Knowing that you should give timely feedback does not make you good at delivering it when the moment is emotionally charged. Understanding delegation frameworks does not prepare you for the anxiety of letting go of the work you were best at. Reading about psychological safety does not equip you to rebuild it after a trust breach.
Performance skills improve through practice: simulated scenarios, real-time feedback, repeated reps in a low-stakes environment. Pilots use flight simulators. Surgeons use cadaver labs. Athletes scrimmage. Managers, until recently, had nothing equivalent.
QuestWorks fills that gap. It is the flight simulator for team dynamics: a cinematic, voice-controlled platform where managers and teams practice the skills that matter most. Delegation under pressure. Communication during conflict. Decision-making with incomplete information. The quests run on QuestWorks' own platform (it integrates with Slack for onboarding and coaching). HeroGPT provides private AI coaching that never shares upstream. QuestDash gives you team health visibility between 1:1s. It is the practice layer that turns management knowledge into management skill.
Where to Start
If you are reading this and thinking "I need to improve at all seven of these," do not try to change everything at once. Start with the highest-leverage practice: your weekly 1:1. Restructure it using the template in our companion article. Run the new format for four weeks. Then add one more practice per month.
The data is consistent: manager quality is the single biggest lever for team outcomes. Investing in yourself as a manager has a larger impact on your team than any tool, process, or methodology you could adopt. The practices are learnable. The research is clear. The only variable is whether you put in the reps.
Check out the best tools for new engineering managers for tactical recommendations on what to pair with these practices. And if you are feeling overwhelmed by the transition, know that the feeling is normal. 60% of new managers struggle. The ones who improve are the ones who practice.
Try it free
