We've just launched plato for individuals

🔥

login


Google Sign inLinkedIn Sign in

Don't have an account? 

Maintaining Direct, Clear Engineering Feedback While Becoming Less Hands On

Feedback
New Manager of Manager
Underperformance

2 August, 2019

Michael Marano is the technical director in the office of the CTO at Google. He offers two alternatives to the inevitable absence of thorough feedback that comes as a manger begins to relinquish control over the day to day responsibilities of teams.

Problem

There are three parts to a job with people management - managing their career development, supporting them as a human, and supporting their technical skills. As you become less hands on in the day to day routines of those that you manage, your capability to give very direct, clear engineering feedback will become harder over time. As you grow and your team grows, it will continue to be the case.

Actions taken

Based on whether or not you can or cannot manage your time or on your technical desires and curiosities, there are really two paths. The decision point is to either hand off people or find ways to get more directly involved.

  • If you can carve out time for it, be totally committed to staying hands on in some way and mentor earlier stage engineers. The way I would do that is always have one project where I am hands on some percent of the time on a day to day basis. It can be a small thing like a hackathon, but do not completely give up on them completely.
  • If it doesn't feel like you either have a technical topic that you want to stick close to or have the time and space to create that buffer, think about how you are going to create a support structure for those individuals to have that. The way I have managed that, especially with earlier stage engineers is by finding a mentor or technical leads that can give them more direct engineering feedback because they are in the day to day process with them. This can be formally through the software process, one on ones with technical leads, and/or by the changing of project partners.

Lessons learned

  • Staying hands on with at least one project is important for two reasons. To stay close to the project in order to keep yourself relevant and current, but also to allow yourself a way to directly interact and provide clear feedback for those individuals. This is especially important for earlier stage engineers, where some investment from you will go a long way, even if it's just time and attention.
  • You have to have something to do in order to stay hands on and close. If you don't, then you have to have a structure to be able to hand it off. It is beneficial to make sure somebody else can help fill the gap where you can't as a manager. Then, you can personally still kind of support more career focus stuff and long term growth, but you need someone that can be close in the details with them on an ongoing basis.
  • Backing off from the day to day know about is usually a level up and you have to be careful about the messaging of that. It is true though, that part of it, is that as you grow in your career and take on larger teams/responsibilities, you will be able to contribute technically in small ways on things in order to stay close. Not so close or continuous however, that you can give as relevant, deep, ongoing feedback to the individuals as someone who is truly on the inside.
  • I have found in my past experience that staying involved comes from the desire to start a new initiative and getting technically hands on to understand new things in order to push the team. Usually when I do that, I am pulling in more senior folks to help pickup and transition that because they will need someone in the middle to translate things.
  • Staying involved in some way or another is a way to help build muscle for you, as well as, build a relationship with and drive feedback for the other person.

Related stories

Limits of Too Much Trust
30 September

Brian Guthrie, VP of Engineering at Meetup, explains where are the limits of too much trust and why verifiable trust is the only trust befitting the workplace.

Underperformance
Feelings aside
Managing Expectations
Brian Guthrie

Brian Guthrie

VP of Engineering at Meetup

Driving Clarity of Charter in a Large Organization
27 September

Jeffrey Wescott, Director of Engineering at Splunk, describes how he introduced clarity on ownership between four disparate teams by drafting a charter that precisely demarcated who owned what.

Ownership
Reorganization
Team reaction
New Manager of Manager
Managing Up
Jeffrey Wescott

Jeffrey Wescott

Director of Engineering at Splunk

Managing Managers: The Three Don’ts
21 September

Adam Bauman, Engineering Manager at Quizlet, shares his Three Don'ts for successful managing managers.

New Manager of Manager
Adam Bauman

Adam Bauman

Engineering Manager at Quizlet

Managing Managers: A Lesson in a Mindset Shift
30 August

Ashish Agrawal, Senior Director of Engineering at Medallia, highlights key differences between managing managers and managing ICs emphasizing the importance of a mindset shift.

New Manager of Manager
Different Skillsets
Ashish Agrawal

Ashish Agrawal

Sr. Director of Engineering at Medallia

Managing a Manager for the First Time: Things I Learned the Hard Way
28 August

Catherine Miller, VP of Engineering at Flatiron, taps into her own experience of managing a manager for the first time and shares some key lessons from her concerted effort.

Managing Expectations
New Manager of Manager
Delegate
Catherine Miller

Catherine Miller

VP of Engineering at Flatiron Health

You're a great engineer.
Become a great engineering leader.

Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.