Napoleon of technical leaders
Posted: August 15th, 2008 | Author: Greg Gigon | Filed under: development, stuff | Tags: leader, project, team, tech | 3 Comments »There is no I or Me in a team. There is only the team. But team needs a leader. It’s a well known fact, human psychology, we need leaders. It is something we might not admit to or not even know about it. We will look up at a guide or a inspiration that will lead our work, correct our mistakes or give advice.
Sometimes team leaders are developing during the process of team formatting (beginning of the team) as a natural process, sometimes they are being assigned to do the job.
Us developers need a technical lead, someone who will guide us while we are doing our job. After few years of IT experience, I can say that I have worked with few good and few bad team leaders.
What makes a good team/technical leader then? Whatever makes a good leader plus strong technical capabilities.
Good listening skills.
It means that you will be listened and your opinion will be taken seriously. I have worked on few occasions with people who just couldn’t listen to any proposition and everything had to be done their way. It ended up usually in waste of time and slide in project delivery. I do have to admit that some of them took all the blame and did extra hours to work out the problem.
Flexibility and openness.
This one is a brother to good listening skills. I have worked with a tech lead whose openness and flexibility lead to many great technical discussion with entire team and brilliant ideas.
Ability to make a decisions in difficult moments and change any decision if necessary.
As much as flexible and opened team leader can be, she/he always needs to make a decisions when it’s necessary. All the discussion we had as a team about technical and non technical issues on a project will never end if someone did not put his feet down at some point.
Point out mistakes and appreciate good job in person.
When talking to a bigger forum or entire team should not discuss individual success or mistakes. Taping someone in a back in front of the entire team will only tell others that they have not worked hard enough to deserve it. Same with criticising anyone, will make everybody else on a team feel better then the one poor geek that got earfuls. All that destroys team spirit and integrity.
Be good motivator.
People need motivation. I do. If there is no other driver in the team at least team leader should inspire and motivate.
Have vision and approach things with passion.
Passion works like a motivation sling. It gives extra boost to entire team if there is at least one person that is so passionate about the tasks that team is facing. I’m damn convinced that at least team lead should be that person.
Presence and appearance.
Technical skills.
Last on this list but equally important. I was working with team leaders that were making bad decisions because they lacked technical skills. They were also to proud to listen to the team and take suggestions on a board. It ended in a massive disaster.
I’m sure this is not the complete set. It contains some of the important factors I could think of and I’m looking for in a leaders. You are more then welcome to complete this set in comments.
The list is not in any specific order. I believe all the points are very important and you can’t have great team leader without all the skills. I am also aware that in real life this will be far away from true. Even great leaders in the world history had their flaws. After all we’re all humans 
Cheers, Greg
