4 ms·
It seems like quite a big jump going from "tech leadership has been part of my work" (sounds like a lead developer role) to VP (all your direct reports are mana
by greenyoda 10y ago
It seems like quite a big jump going from "tech leadership has been part of my work" (sounds like a lead developer role) to VP (all your direct reports are managers/directors). (In a tiny startup, maybe someone who manages developers might be given a VP title, but if the company grows, a VP will eventually end up managing managers.)
I'm not a VP, but I report to a VP of development, so I've observed them up close. The important skills for VPs seem to be:
- People skills - most of their time is spent talking to other people (meetings and one-on-one conversations). They need to be able to communicate effectively with all types of non-technical people: executives, sales, marketing, product managment, customers, etc. - anyone who wants something from their development team.
- Being able to envision the future path of the product. This involves more than knowing technology - you have to know the product you're building very well, and understand how users use it.
- Understanding how the business works and what would make it successful.
- Being able to deal with difficult decisions like laying people off when the company isn't doing so well.
- smtorother 10y agoSo what would be the lessons you've learned if I may ask that are you didn't know when you started your current position? Things along the line of: it's better to make other person think they've come up with the idea so they are committed to it than to show off how intelligent I am.
- greenyoda 10y agoHere are some things I learned: - No matter how busy you are, you should always make time to mentor your employees. Help them grow by delegating increasingly difficult work to them and giving them additional responsibilities. If you can't delegate to your employees with confidence, your own workload will eventually overwhelm you. Also, as your company grows, being able to promote existing employees instead of hiring from the outside means that you'll have managers who have a better understanding of your company's technology and business. (And if you want to be promoted in the company you currently work for, it's easier if you have someone who's ready to step into your current job.) - On the other hand, don't try to shield your employees from tedious or difficult tasks by doing them yourself. Some percentage of work is tedious or difficult, and it can be as much of a learning experience as more interesting work. Don't feel guilty about delegating this kind of work to others. It's part of the job. - Don't be friends with the people you manage - find friends outside of work or in other departments. (I don't mean that you should be unfriendly to them, but don't socialize with them or have deep personal conversations.) This might be a controversial opinion in work cultures where everyone in the office socializes with each other, but it makes it hard to make objective decisions about who should be promoted, who should be laid off, etc. At some point, you'll need to make these kinds of decisions, and they shouldn't be biased by the fact that some of your employees are your drinking buddies. - Learn how to manage your boss's expectations. Saying yes to every request will eventually lead to failure and burnout (of both you and your team). The end result will not be good for your company (projects failing, people quitting). - Pick your battles. Some fights are not worth the trouble it takes to win them.
- smtorother 10y agoThank you, great insights. I see already that 3rd point could be a tricky one for me personally...