Slashdot Mirror


What Qualities are Necessary in a Good Team Lead?

Midnight Thunder asks: "We have all had our share of team leads and some of us have been in the position ourselves. I would be curious to know what things you have appreciated from your team leads and what you didn't like. Also, for those of you who have been in the position how you found it. The main reason I ask is because this offer has been given to me as a carrot and I would like to make the right choice, and if I take it learn from other people's experience how to be a good lead."

1 of 64 comments (clear)

  1. The most important ones by yetanothertechie · · Score: 5, Interesting

    I'm currently a team lead, and have been the lead on many projects over the course of 20 years of software engineering. Here are the qualities I believe are the most important for being an effective team lead:

    1. Technical skills - Very strong in the areas of relevance to the project, and in other surrounding technical areas as well. It's best if you're very good at doing what it is you'll be leading.

    2. People skills - It's critical to relate to your technical team properly. Respect them and listen to their ideas. Explain your ideas to them. Come to a consensus if possible; if impossible, then explain clearly why you're saying it has to be done a certain way. Convince them through the logical application of problem solving, not brute force. Give people flexibility in their jobs, try to find good fits for their skills and interests, and tailor the level of direction you give to how much each individual needs - it's not one size fits all. Communicate clearly, and don't waste peoples time in unnecessary meetings, (some are necessary however).

    3. Organizational skills - You need to be extremely organized. Make sure you yourself clearly understand precisely what's going on with all aspects of the project, and that you keep track of issues and resolutions. Use whatever methods work for you to track tasks and progress, but keep it up to date and accurate.

    4. Buffering - Shield your team from the vageries of upper management. You be the one to deal with the crap that comes from the top, filter it out, and protect your team's work environment. You be the one to set tasks and priorities - don't allow people outside the team to direct the efforts of your team...it just results in confusion and wasted effort.

    There are a lot of others, but I think these are the most important ones. Most technical people simply want to work on interesting tasks in an environment where they have a certain amount of independence as well as respect and consideration. Lead them in this way and you'll have a solid and happy team.

    --
    Facts are stubborn things.