Written by Jamie Tuesday, 24 January 2012 10:21
In 1980, Geert Hofstede published a book called Culture’s Consequences. He had been lucky enough to gain access to a huge survey that IBM had carried out against its employees. Hofstede was able to draw some conclusions about different countries, including the distance between ‘the man on the street’ and a member of the ruling class. He called this the Power Distance and compared countries to each other in what he called the Power Distance Index. This is what he had to say about leaders from different countries:
In low PDI countries, power is something of which power holders are almost ashamed and which they will try to underplay. I heard a Swedish university official state that in order to exercise power, he tries not to look powerful. This theory definitely does not hold in Belgium or France. I once met the Dutch prime minister with his caravan on a camping site in Portugal; I could not very well see his French or Italian colleague in that situation. (Culture's Consquences, 2nd Edition, p. 97.)
Another dimension that Hofstede studied was uncertainty. He compiled The Uncertainty Avoidance Index. This index is of course interesting, with Germany and Greece, conservative countries, scoring high, and the United Kingdom and Holland, scoring relatively low. However, what is more interesting to the modern manager or leader are the questions that were used in the IBM survey. Understanding the questions is key, for example, to a successful agile transformation. The three questions were:
1) How often do you feel nervous at work?
2) How strongly do you agree with this statement ‘Company rules should not be broken - even when the employee thinks it is in the company’s best interest’?
3) How long do you intend to stay at the company? (Hofstede et al. p. 190)
A person who is nervous at work is not likely to introduce unnecessary ambiguity. Therefore, even though it could be good for the company, this person would never break the rules. A person who doesn’t change employers regularly is also afraid of ambiguity. Any team, then, whose mean score to these questions is high, is likely to be conservative. (Hofstede et al. p. 191) If it’s a conservative team, it is likely to resist change.
What Can One Do With This Information?
A good strategy for a company that is transforming to a more agile way of working is to get one team fully functional. A team that lives by its principles leads to what Jim Collins calls ‘inspired motivation’. This one team goes onto inspire the other teams. The answers to the three questions can be used when thinking about the composition of this team. It is better to staff the team with the opposite of conservatives, i.e. to staff it with radicals, because radicals always reject what is in favour for what can be. They are, therefore, powerful, and often fearless, agents and leaders of change.
Another strategy for a company that is transforming to a more agile way of working is to fire all the conservatives. This is an option most people ignore. Many people are caught up in a collective denial of human nature; they assume that people are flexible. This is obvious from the proliferation of two-day training courses, which are superficial by design, and by the enormous amount of literature that speaks of transformation but never speaks of firing people. In his book, From Good to Great, Collins says a cornerstone of success is to ‘get the right people on the bus’. There is a logical corollary to this: get the wrong people off the bus.
Conclusion
Humans hate uncertainty. We’ve invented technology to try and remove the uncertainty associated with the weather. We’ve invented the law to try and remove the uncertainty associated with other people. This is a fact that we have to look in the face. To help us with that, we can let people like Hofstede guide us. His work is uniquely powerful. It inspires us, as engineers and managers, not to deny human nature but to accept and work with it. It affords us the courage to reject the out-dated and, frankly, wrong modes of transformation that have become the tools of choice for so many consultants, the cornerstones of so many failures. And finally, Hofstede re-reminds us of what Collins, in Great by Choice, says: ‘[the best performers] don’t favor analysis over action; they favor empiricism as the foundation for decisive action’.
Further Reading
I adapted the Hofstede’s questions from the third edition of Cultures and Organisations: Software of the Mind. Great By Choice is written by Collins and Hansen and it’s a half decent meditation on the choices we can make as managers, engineers and leaders.
For those without the books, I would encourage you to follow these links to ‘Uncertainty Avoidance’ and ‘Power Distance Indexes’.
Last year I used Handy’s Understanding Organizations and I am still happy with the chapter on power and influence.
| < Prev | Next > |
|---|
Comments
The idea of starting with one successful team is also interesting, I know some companies have gone that way for their transitions. I think it's important to have diversity on the team, so maybe a 'conservative' or two wouldn't be bad. But IME you have to let go the people who simply don't want to change and aren't passionate about doing good work.
Human nature is so complex, it's smart to try to work with it!
Having too many similar personalities on one team can be a recipe for disaster. I ran a simulation at a local XP meetup based on culture models and MBTI and it was interesting to note that 'NT' temperaments didn't finish the exercise which is a trait of the NT temperament. They tend to spin and avoid making a decision. Too many NT's on a team can result in the same problem. Full details here if you're interested:
http://www.agilecoach.ca/2011/11/28/people-create-your-culture/
Thanks for the comment.
Jason,
Of course I am interested, thanks for the link.
As for diversity, and having diverse teams, etc. I couldn’t agree more. That’s important. Here is the big hairy but, engineering is about change. A conservative, therefore, has no place on any team just like a cricket player has no place on a rugby team. A radical is not someone who is a ‘bit mad’ or ‘super cool’. A radical rejects what is in favour of what can be. This is essence of engineering. A conservative accepts what is and, worse, hinders those who don’t agree with him.
There is no place for a conservative on team that builds software.
There is a much more rigorous treatment of this here: www.financialagile.com/articles/3-software/10-in-defence-of-moving-forward
Also, this blog was a spin-off from a larger essay which includes proper definitions. Please look out for that, a draft is coming in the next week and I’d love any feedback.
I agree with your point that a conservative hinders those who don't agree with him/her. Especially when that conservative is in a position of power, it creates a control culture and worse, a mediocre product.
Just to play Devil's advocate for a moment. Should we have murderers on the street because they balance our societies out? Or, as I said earlier, a cricketer in a rugby team, for the sake of balance?
What is this balance we all seek? When I play rugby I don't want balance at all. I want 14 of the best man I can find on the field with me because I want to win. When I play business, or software development, I want the best people around me because I want to win.
What do you think?
What I meant was, given my experience and observations with NT temperament and function pair, not having a person who counter-balances the group can lead to slow or no progress.
Even on a Rugby team you have people with different skills, some are offensive minded, some are defensive minded (maybe, I dunno, in hockey it's that way...I'm Canadian eh?)
Personally I don't want to work on a team of conservatives so I get where you're coming from, unfortunately I think the IT and software world are dominated by controlling personality types who think the way software was built 10 years ago (or even 5) is still the best way today when I know it's not.
OK, I think we agree. To be continued.
Thanks for feedback. Will post essay shortly.
J
Collins' work has been widely discredited, and he is to a large extent a modern day snake-oil salesman (check "The Hallo Effect" for a critical review of Collins work).
On the other hand some of the things he says and you quote actually make sense. I especially like your title for this post! We should do that more! (with the appropriate data and science, of course :)
I had no idea about Collins. Do you any links to papers that discredit his work?
This piece was not meant to be about Collins, but I did use some of his stuff to make my own points. This was maybe lazy of me.
RSS feed for comments to this post