> This is an authoritarian model that makes the local despot the bottleneck for the team: Decisions end up being routed through the "leader", individual growth and development and team value is constrained within the scope of the "leader".
This isn't an absolute conclusion, I don't think. I can speak for my own organization -
I lead 2 functionally-aligned teams, meaning they own internal product/systems for two different partner orgs. I also have a technical program management function which owns initiatives related to the above when they span more than a single team or are company-wide initiatives. I also have an engineering team with its own EM who roughly cover the scope of whatever my organization is doing - could be single-function, could be company-wide.
In my model, decisions from Principal/Director/Manager team members don't wait on me. They can if they want extra eyes or extra air cover, but otherwise, my job these days is less about setting technical direction and more about unblocking via executive alignment, budget, people, etc.
So far you might be thinking this is uninteresting and just means that my individual managers are the local despot, but I've done two things to (so far) eliminate that -
1. The TPM is responsible for getting us through the design stage, and they manage no one (or maybe other TPMs). This means they herd the cats and work with engineers and SMEs to get aligned on whatever design will make us functionally and technically successful.
2. This one is more on my qualities as a leader, but I also ask the managers on my team to err on the side of delegating more and letting their staff impress them, and being there as a resource when they need help. I think this is called servant leadership, but I don't read a lot of management stuff.
Team composition (experience and horsepower) plays a large role in whether this model can be successful and how hands on you'll have to be, but in trying to distill a decade+ of experience into a couple of paragraphs, this is generally how I like to run things. YMMV of course, I don't hold myself out as an authority, just offering a counterpoint.
> The best managers don't have a hard time finding talent for open positions on their teams: They already have networks of former employees and peers that they can use. Indeed, the employees of the best managers recruit for their teams as soon as positions open up.
If you adhere to the standard 1 year non-solicit, this isn't true right away. Hiring in my first year at a new company is one of the hardest parts of my job. But I'm probably a bit of a rule follower when it comes to the non-solicit - moreso than others, I've observed.
This isn't an absolute conclusion, I don't think. I can speak for my own organization -
I lead 2 functionally-aligned teams, meaning they own internal product/systems for two different partner orgs. I also have a technical program management function which owns initiatives related to the above when they span more than a single team or are company-wide initiatives. I also have an engineering team with its own EM who roughly cover the scope of whatever my organization is doing - could be single-function, could be company-wide.
In my model, decisions from Principal/Director/Manager team members don't wait on me. They can if they want extra eyes or extra air cover, but otherwise, my job these days is less about setting technical direction and more about unblocking via executive alignment, budget, people, etc.
So far you might be thinking this is uninteresting and just means that my individual managers are the local despot, but I've done two things to (so far) eliminate that -
1. The TPM is responsible for getting us through the design stage, and they manage no one (or maybe other TPMs). This means they herd the cats and work with engineers and SMEs to get aligned on whatever design will make us functionally and technically successful.
2. This one is more on my qualities as a leader, but I also ask the managers on my team to err on the side of delegating more and letting their staff impress them, and being there as a resource when they need help. I think this is called servant leadership, but I don't read a lot of management stuff.
Team composition (experience and horsepower) plays a large role in whether this model can be successful and how hands on you'll have to be, but in trying to distill a decade+ of experience into a couple of paragraphs, this is generally how I like to run things. YMMV of course, I don't hold myself out as an authority, just offering a counterpoint.
> The best managers don't have a hard time finding talent for open positions on their teams: They already have networks of former employees and peers that they can use. Indeed, the employees of the best managers recruit for their teams as soon as positions open up.
If you adhere to the standard 1 year non-solicit, this isn't true right away. Hiring in my first year at a new company is one of the hardest parts of my job. But I'm probably a bit of a rule follower when it comes to the non-solicit - moreso than others, I've observed.