Tuesday, February 26, 2008

projectDiversity.equals(productivity)

I have started reading the book described in this article

In Professor's Model, Diversity = Productivity

After reading some of his book, it seems that cognitive diversity (defined as group differences in perspective, heuristics, interpretation, and prediction) generally lead to improvement in overall productivity. There are other kinds of group differences, of course...e.g. what Page calls identity differences (e.g. racial, gender, and social group), and other sorts of differences, but Page identifies cognitive differences as key.

Increased productivity is dependent upon the problem/task at hand, of course. Group tasks/problems that hinge on questions of representation and interpretation get greater value from diverse perspectives, since such diversity allows more alternatives to be generated and considered.

My thought on reading this was that many sw design tasks are like this (i.e. hinge upon how the problem is represented) and so should be particularly good candidates to benefit from teams with high cognitive diversity...and the many perspectives that come with such groups.

Interestingly, Page also identifies a type of diversity that seems to result in lower group productivity...I'll talk about that after I've read a little more.

2 comments:

Ed Merks said...

Scott, I'm very curious to find out about "bad diversity."

Scott Lewis said...

Hi Ed.

>Scott, I'm very curious to find out >about "bad diversity."

Me too :)...just need some more reading time. As a teaser for both of us, he seems to find that if teams differ in what he calls their 'fundamental preferences' (e.g. 'what are the goals of this project?', 'what are we trying to accomplish?', 'should we be open? ;-), etc) then this sort of diversity is very detrimental for productivity...as you would expect.

This is intriguing to me as it relates to open source sw projects...particularly for Eclipse Foundation projects as (I think) there is sometimes goal-level differences among project teams...e.g. I don't suspect IBM's goal for Equinox is exactly the same as mine.

But I do need to read more to find out what he's saying/has found. So take with chuck of salt.