Features of awkward colleagues


goo Ranking took a look at a subject close to my heart, what are the characteristics of coworkers who are difficult to work with.


Between the 17th and 18th of January 2012 1,048 members of the goo Research online monitor group completed a private internet-based questionnaire. 61.6% of the sample were female, 12.3% in their teens, 15.6% in their twenties, 27.9% in their thirties, 25.8% in their forties, 9.5% in their fifties, and 8.9% in their sixties. Note that the score in the results refers to the relative number of votes for each option, not a percentage of the total sample.

I’d say the main problem I see with my colleagues is an unwillingness to challenge the status quo, or even to just suggest different ways of doing things. One recent case that comes to mind was that I was moving on to a new project, and I asked what other people in similar environments were using for source code control, and the answer I got back was “nothing”. After banging my head on the desk for a few minutes, I decided to go with git, which I taught myself in two minutes.

Naturally, I have none of the characteristics from the list below.

Ranking result

Q: What are the characteristics of colleagues who are difficult to work with? (Sample size=1,048)

Rank   Score
1 Violent mood swings 100
2 Doen’t admit their own mistakes 99.4
3 Always criticising 98.9
4 Always changing their viewpoint 89.5
5 Doesn’t inform me when things are not right 82.7
6 Poor time management 75.8
7 Often late for work 70.6
8 Doesn’t do things by deadlines 65.9
9 Pessimistic 57.5
10 Always talks idealistically 50.9
11 Procrastinates 44.7
12 Drones on and on 42.1
13 Has no opinions of their own 38.5
14= Indecisive 35.5
14= Poor at schedule management 35.5
16 Poor at explaining things 35.0
17 Rude to those below them 28.4
18 No conculsions in their email 21.2
19 Not proficient with computers 20.1
20 No self-confidence 16.3
Read more on: ,

Custom Search

1 Comment »

  1. Janne said,
    February 21, 2012 @ 21:43

    Late comment but: are you freaking kidding me? An (assumedly) professional software development department that does not use a VCS? That does not, in fact, _mandate_ the use of one, no matter what individual devels may be thinking about it?

Leave a Comment