Current Articles | RSS Feed RSS Feed

Why isn't a Good Team Player good for a team?

Posted by Andy Singleton on Mon, Dec 15, 2008 @ 10:47 AM
 

A candidate described himself as a“good team player” in a resume he sent me last week. While the angel on my right shoulder was saying to me “We have teams. We need a good team player,” the devil on my left shoulder was jumping up and down and screaming “Stay away. He's a loser. You want someone who can do the whole damn job by himself.” Statistically, the devil is right. We have found that if someone puts “good team player” on a resume, the probability that he will succeed in a trial is low.

 

Even stranger, it often happens that someone who describes himself as a good team player will not deliver on something that his teammates need, frustrate the other team members, lower team morale, and actually provoke a request for removal.

 

It seems to me that “good team player” means that the applicant is reliable and co-operative from a management point of view, not from a team point of view. It means he will do what the boss tells him to do. It doesn't mean that the other team members can rely on him to carry their burden.

 

My friend Doug Smith in “The Wisdom of Teams” makes three points that will explain what is happening.

 

1) He observes that high performance teams are not necessarily composed of people who like each other. Instead, they are composed of people who share the same goal. In pursuing the goal, they can achieve high performance even if they might be described as bad team players. Winning at work is great positive feedback to keep them going and support their relationships.

 

2) He points out that in a high performance team, leadership moves from person to person. When challenges arise in the area where one team member is working, he will step forward to lead an effort, point out the need for change,or finish something important. This type of team rewards people that are good at their jobs.

 

3) If you have a “single leader”who tells everyone what to do, it's not a team by the definition of“Wisdom of Teams”. It's a bunch of relatively interchangeable people following instructions. This can be a good management model if the leader/manager is sure he knows what to do. The “single leader” is the target of the “good team player” line, not the team.

 

I am reminded of the story of Patroclus, the sidekick of Achilles. Patroclus was a definitely not a team player. He grabbed Achilles armor, and ran onto the battlefield under a false identity. For one glorious afternoon, the sidekick was the leader, pulling the Achaeans forward, driving the Trojans back. Then, by not following instructions, he got himself killed. In doing so he turned the tide of the war and united his teammates.

 

The team fielded by the Achaeans in the Illiad is a management nightmare, showing off, arguing over women,carrying baggage from past gigs, fighting violently, and threatening to walk off the job. But they win the war. I will not allow someone to threaten to walk off the job. Someone who does that is surely not going to support the team, and I have to take him off the job pre-emptively. But I have come to believe if you keep your heroes motivated with a clear goal, which suppresses disagreement, you can have a winning team.

Tags: 

COMMENTS

Having created several startups, and worked with scores of developers, a team player IMHO is an individual that 1) sets correct expectations; 2) delivers what he/she commits to deliver; 3) takes initiative to understand their company and industry to develop beyond what has been mapped out (i.e. taking pride in his/her work to create something that brings further benefits to the common goal of the company); and 4) does not make demands upon the company when he/she has become integral to the company's success. 
 
Disagreements and even heated arguments are a natural part of working in close community on difficult and time consuming projects and thus, are not the problem by themselves. The problem comes when the disagreeing parties do not work towards reconciliation, understanding and compromises. If this happens, this is when the "nightmare" begins, and the only way to stop and recover from it is to fire the individual creating disharmony from the company at the earliest possible time, no matter how key the individual is.

posted @ Monday, December 15, 2008 11:46 AM by S. Ellis


You state: "Statistically, the devil is right. We have found that...". This is a terrible way to present your argument. You make a statement about what is "statistically" the case, with the only evidence to back up that conclusion being "We have found...". 
 
You need to work on your presentation skills. Your argument boils down to nothing but opinion... which is just fine, especially in a blog. But opinion pieces containing zero empirical evidence probably shouldn't use the word "statistically."

posted @ Monday, December 15, 2008 12:59 PM by Stewart Bryson


Those are indeed statistics Andy, and they are the kind of statistics I would need to see in your blog posting before I took your claims seriously. That was my only point.

posted @ Monday, December 15, 2008 2:48 PM by Stewart Bryson


it all comes down to attitude and i'll take attitude any day over skills, as you can't teach/improve one's attitude, but you can always refine their chops. getting to the heart of one's attitude is tuff and takes time/observation. my advice is to hire folks on a trial basis, or have them work part-time on small projects for a period of time first b/c invariably there will be a small hiccup and how the individual responds will illustrate their attitude. But, make sure not to confuse their inability to work under pressure with their attitude, as those are two separate issues.

posted @ Monday, December 15, 2008 9:00 PM by Sam


I have to agree with Stewart’s comment earlier. I don’t think anybody could make any valid assumptions of the character of a person based on the use of a three word colloquialism (“good team player”) within their resume. 
 
 
 
I think that a lot of the modern warm fuzziness on effective teams, is really media material created for corporate consumption and subsequent profit. It should therefore be taken with a grain of salt. Teams often fracture because the goal is just not that important to the team members and no modern management techniques will negate that. 
 
 
 
I like your use of Achilles, and I think the best team and leadership knowledge comes from history and to a large extent military endeavours. 
 

posted @ Wednesday, December 17, 2008 4:39 PM by Ryan


Although I can see and understand your content - I disagree. To have a team, you need team players. But blowing off a candidate for saying their a team player is a mistake - especially thinking of them as losers for saying so. I, myself, believe myself as team oriented and very much a strong part of the teams to which I belong -- would I say I'm a team player in a resume? I'm not sure. I suppose the reason I wouldn't though, would be from reading blog posts like this. Too bad... 
 
I just don't really see your point on this one. 
 
:)

posted @ Thursday, December 18, 2008 2:26 PM by MikeB


Having built and managed many development teams, someone who states they are a team player is admitting low confidence in their core abilities. They are making the statement that if they cannot do the tasks required, they will do whatever else the team needs. Can you afford this? 
 
I think what we are looking for is "can play/work with others". There are some of those who are "Dennis Rodman's" in our profession. They are talented but can disrupt the progress of your project and even cause it to fail. The moment I detect one, they are immediately off the project. 
 
The key to building a team is to organize those with like minds. In other words, we have the same core beliefs in software development. This is basic psychology of human organization. Now too much like mindedness is not good either, so you need to add some diversity through experience, disciplines, and strengths.  
 
One more important element to building a team. You must consider the core traits of the team member. Core traits are things that you cannot train, intelligence, passion, capacity to learn quickly, problem solving, and etc. Someone either has it or they don't. These are the first things I consider when bringing someone on my team. This is important because if the team needs them to do something outside their strength, the team will be confident they can get it done. 
 
Leadership style of your team will also factor in your member selection. Is your team lead through self organization, team leads, shared leads, project managers, etc. 
 
Cheers, 
John

posted @ Sunday, January 18, 2009 1:07 PM by John Fuqua


this makes me laugh. i played semi pro soccer in the uk, at university and so on. i also played rugby. i am by definition "a team player". ive done it three times a week since i was 10. 
 
i've often been made skipper of teams because im a decent, hard player, vocal organiser, and good at predicting threats and devising strategies - in short i am a natural leader. sort of "team player plus". 
 
i have had success at amateur sport. this is because in sports there is no politics. once you cross the white line its you and your mates and you either win or not. there are no hiding places and if someone is shit or has a bad attitude they end up looking like idiots or taking an early shower. 
 
this isnt the case in business. in business people can hide, suck up to the boss, nitpick, bully, lie, connive and so on. now if im on a "team" thats failing to deliver because of this i have done what i have always done. identify and organize. you would think a company would value this but no. people like comfort, status quo. the company and team can come last in every race but woe betide you if you say anything. ive actually had managers slowing me down in case it "made them look bad". 
 
so all this "team player" business is a crock. if youve got someone good, get out of their way and reward them for their contribution. 
 
these days i make my mediocre salary achieving mediocre things. my manager thinks im great. thinks im a team player. meanwhile all our jobs are going abroad because the job we do as a team, company or industry doesnt cut it any more.  
 
that what being a "team player" is all about in modern business. fiddling while Rome burns. 

posted @ Monday, February 23, 2009 9:56 AM by zeppeline


Comments have been closed for this article.

Follow Assembla

twitter facebook youtube linkedin googleplus

Subscribe by Email

Your email: