Yesterday someone said to me that the true Engineering Managers job description is: To enable really smart people to make them look good. I think in truth there is a bit more to it than that phrase. I like that they have included the word 'enable' and that they are highlighting really smart people. If I had to try and rewrite this in the same vain perhaps: To empower and enable really smart people to achieve business outcomes and deliver business value. How you empower and enable those is the art of Engineering Management.
May I suggest "To empower and enable all people to be their best so they can achieve business outcomes and deliver business value." I'm not particularly smart. I'd hate to feel left out on that team! 😁
Engineering managers enable the integration of engineers to execute an engineering plan. That is why there is no need for engineering managment where there is no complexity (overhead).
Opinion that I'd appreciate thoughts on: I think the best version of an engineering manager is someone who is a coach and collaborator. They're basically a Sr. Dev who doesn't take on tasks themselves, but at some point in the week engages with pair/mob programming with all of the people under their span of control (6-8 people max). This solves so many problems. It helps maintain alignment around architectural and coding practices. It also solves the issue around needing to monitor developer productivity; just go ask the manager they'll be able to tell you if someone isn't pulling their weight. The thing is this is a fundamental shift from traditional management which views managers as being removed from the work. It means that if managers have an underperforming team member they need to take a coaching approach, not a controlling one. It has to be all carrot, no stick, right up until the moment you decide they're not cutting it. Software is built by a system of humans and as such needs to be a collaborative thing. This is how the software manager engaged with the people on the 2 teams they oversaw at the last place I worked and it was a game changer. Completely supercharged our teams in the best way possible.
I've always been taught that the hardest teams to manage are the ones with most capable people. The temptation is to "dumb" people down to the level of the manager. But true leaders are comfortable not being the smartest person on the team - and they give the members of their team the spotlight to shine and run hard after what they're capable of. EMPOWER and ENABLE. Spot on, my friend!
I like your last statement on "empower and enable". We are meant to maximize the productivity and growth of the team as a whole and also each person on the team. That requires a strong mix of soft and hard skills. An experienced engineer who has spent time in the trenches, has knowledge of the technical details but also a big picture view, and has good people skills are to me the core ingredients of a good manager. And care factor is big too --- if you care about your team you will see their potential and actively try to help them grow and become all that they can be. Because of the nature of the position, engineering managers can either add a lot of value to their team or very little, becoming the oft maligned, do-little, "middle management".
Providing opportunities for professional development will support your team. When your team members see that you invest in their growth, they feel valued and motivated to contribute more effectively.
Look good might be a reference to " achieve business outcomes and deliver business value" because in the eyes of those paying them it will make them “look good” indeed.
Haha, that's a great way to put it! "To enable really smart people to make them look good" is definitely a catchy way to capture part of the role. But yeah, you're right, there's definitely more to it. Empowering and enabling your team to achieve business outcomes and deliver value is spot on.
Agree with the majority but I would have preferred enable people rather than just smart people. As a manager it’s our job to get the best out of every individuals.
Insights for devs and managers → FromTheTrenches.dev | VP of Engineering at Contractbook
6moI love the rewrite. The focus on business outcomes is critical. I'd also extend it with a second part: to help people grow.