3 ms·
Great VPs need to good at two very different things: politics, and their actual job, and for this reason they are rare. They might not be rare if more organiza
by btilly 13y ago
Great VPs need to good at two very different things: politics, and their actual job, and for this reason they are rare.
They might not be rare if more organizations had a smarter idea about the actual job a VP of technology needs to perform.
One of the best VPs of technology that I ever worked for saw it as his job to use his considerable abilities at playing politics to guarantee that no tech person below him had to deal with any political BS. He himself had no ability to work with technology, and everyone knew it. But he knew who did and enabled them to do their job.
Every technical person in that organization understood and valued this about him. As he moved from company to company, they would voluntarily seek him out. And now that he founded his own company, the fact that people who have worked for him wanted to work with him again proved to be one of his biggest assets.
- nairteashop 13y ago> He himself had no ability to work with technology... But he knew who did Agreed, and in fact this is what I meant by the VP's "actual job." As a VP of Engineering, your job is indeed to build a great engineering team and then protect them from the inevitable politics. However, to build this team you need some framework on the technology to understand who is BS'ing you, and who you can actually trust to do the right thing. IMO you can't do this well if your background is in, say, finance. (Similar to how a great engineer would probably make a terrible CFO.) The incompetent VPs I've had to deal with weren't stupid, in fact many were quite smart, and of course politically astute. But they just didn't know enough about the technology to know who to trust to actually deliver a great product as a team.
- btilly 13y agoHowever, to build this team you need some framework on the technology to understand who is BS'ing you, and who you can actually trust to do the right thing. This is where you're wrong. You don't need to understand the technology. You just need to have someone that you can trust who does. And said trust can be based on past experience, not current. Furthermore trust is to some extent transitive. If you trust person X and they say that person Y is competent at tech, odds are that person Y is smarter than your average bear. Couple with a sample project or two, and you're on your way to having another person whose opinion you can lean on for tech matters. What can't be outsourced is judgement of people.