Team Lead Advice
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
- Build professional trust with your team, and learn to trust them. When many managers are in over their heads, they don't ask for help, rather they start to micro-manage and make snap decisions, which just makes the problems worse. - The positive attitude that Pete suggested is also a must. It's fun and easy to use self-deprecating humor, make fun of how crappy the code you're still using from 6 years ago is. However that actually sets a tone that the employees tend to follow. After time, everyone becomes complacent. I think you'll do fine for two reasons: 1) You're already looking how to be a good leader. 2) You get to ease into the position as the team is starting small. Good Luck!
All of my software is powered by a single Watt.
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
The answer starts with a quesiton: Do you want to lead your team to produce the best product or do you want to move up the management ladder? This means either managing up, or down. If you manage down, you will look after your team. Praise them for good work, as Pete says, publicly. If they screw up, try to find out why without criticising them, rather criticise the lack of information they received, or the lack of understanding of the problem, or the lack of tools or training they needed. Alwsys criticise the process, never the person. Of course if they are useless sack them, Immediately. If you want to manage up, then you need to kiss ass. And take credit for your teams work. And generally be a twat. :) I always managed down, and with good design and good communication, and many good laughs, totally nailed our part of the product. Oh, and dont micro manage. Let your team express its creativity. Give guidance when asked, keep a close eye on progesss, but dont ride them. Create an easy going, go for it atmosphere, and they will love you and reward you with commitment and hard work.
============================== Nothing to say.
-
Listen to those around you. Rinse, repeat.
Panic, Chaos, Destruction. My work here is done. Drink. Get drunk. Fall over - P O'H OK, I will win to day or my name isn't Ethel Crudacre! - DD Ethel Crudacre I cannot live by bread alone. Bacon and ketchup are needed as well. - Trollslayer Have a bit more patience with newbies. Of course some of them act dumb - they're often *students*, for heaven's sake - Terry Pratchett
You should always listen, but do not feel you always have to obey. Doing what the group wants is not leadership. Sometimes some of my team members will lobby for a particular design direction or new feature because they think it will be more fun (challenging). For example, they always want to rewrite code instead of reusing what we have or use a snazzy new technology instead of what we know works. Sometimes they are right, but often the cost/reward ratio is bad and you have to say "no".
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
Document everything!!!
Everything makes sense in someone's mind
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
Listen to people, Do not pretend to know everything! If you don't know the answer find someone who does. Last but not least: Don't try to be a nice guy (not try to be a bad guy either). Most people rather have a fair leader that tells them the truth than a nice guy who lets the project fly to hell. Did I mention listen already? Listen and repeat back what people said in different words to make sure you're on the same page. A misunderstanding can lead to many nasty things. Sounds like a open door but: Don't try to lead but be a leader and expect to be treated as such. Hope this helps you. Cheers, AT
Cogito ergo sum
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
I can't write a book here and there is no single answer. The invariant in all cases is having a group of people that are all different and have different additions to the team. So who are they, what do they want, what are their abilities and what are they willing to commit to the common thing. And then you, having a feel for all of that trying to enable and combine them into a smoothly working team moving forward. I do so in a cooperative way but I do lead.
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
Yell at them. A lot. They respect strength. Bryce *chortle* (check out the Entre leadership podcast)
MCAD --- To paraphrase Fred Dagg - the views expressed in this post are bloody good ones. --
Our kids books :The Snot Goblin, and Book 2 - the Snotgoblin and Fluff The Snotgoblin for the Ipad -
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
Like anything - at least start with some research. To start with there are many books on management. Probably should look into project management as well. And if the team does grow you had better be willing to live with the reality that you are not going to be programming as much. Figure at least 50% of your time will no longer be coding/designing yourself.
-
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
Always remember that, while you are the Team Leader, you are also a Team Member - It is, after all, a Team. I echo what Pete says above but would comment on the 'being one of the lads' comment. It's a very fine line but if you're not their manager then I would err on the side of being 'one of the lads'; a manager must be more removed, but I think of a team leader as being a member of the team with some added responsibility.
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
-
Always remember that, while you are the Team Leader, you are also a Team Member - It is, after all, a Team. I echo what Pete says above but would comment on the 'being one of the lads' comment. It's a very fine line but if you're not their manager then I would err on the side of being 'one of the lads'; a manager must be more removed, but I think of a team leader as being a member of the team with some added responsibility.
MVVM# - See how I did MVVM my way ___________________________________________ Man, you're a god. - walterhevedeich 26/05/2011 .\\axxx (That's an 'M')
bollox, the solution is to yell at them. Lots. :) B :laugh:
MCAD --- To paraphrase Fred Dagg - the views expressed in this post are bloody good ones. --
Our kids books :The Snot Goblin, and Book 2 - the Snotgoblin and Fluff The Snotgoblin for the Ipad -
I've been a web developer for about 7 years now and will soon be placed in a role where I would be considered the team lead. The group will start off small but will eventually get much larger. I've never had this type of experience before as I've only really worked on projects with one other developer or by myself. I know I am going to make mistakes in this role as I am inexperienced at it but would anyone be willing to offer up some advice or suggestions? For instance, things you would like your team leader to do. Or, if you have experience. what you did that you felt worked very well? Thanks in advance!
Brett A. Whittington Application Developer
Take them to the pub at least once per week
==================================== Transvestites - Roberts in Disguise! ====================================