I had the good fortune to get to meet Tom Malone way back when he was working on what makes computer games fun (cited in my book). I stopped by PARC (then the geek’s Mecca), and got to bask in the environment that produced the GUI on top of Doug Engelbart’s mouse.
I knew Tom then went on to be a thought leader out of the Sloan School of Management, studying office work and then higher levels of activity, leading to a recent book “The Future of Work”. I happened to meet him again at an event at IBM’s Almaden Research Center, and he was gracious enough to remember me and discuss his work (I challenged him about his ‘guilds’, since they still can’t get reasonable healthcare that businesses can get, don’t get me started).
I mention this backstory to show the trajectory of thought leadership he’s had (and yet still remain a really nice guy). He just spoke at the celebration of Doug Engelbart’s work, and while I couldn’t attend, I was looking for blog postings and found his slide deck.
You (should) know I like models, and he’s gone beyond talking about how web 2.0 social networking can facilitate work, to actually analyze and distill some underlying principles. In his presentation on The Landscape of Collective Intelligence, he comes up with four characteristics of design patterns (or genes, as he calls them): What (strategy), Who (staffing), How (structure & process), & Why (incentives/alignment). This is a really nice systematic breakdown into patterns tied to real examples.
For Who, he distinguishes between a hierarchical arrangement and a crowd, the latter being a more random structure. He focuses on the latter. For Why he breaks it out into Money, Love, & Glory. For What, it’s Create a solution or Decide on an issue. How is whether you’re having it independent or dependent. The latter two work out to a nice little matrix with collection, collaboration, many-to-many, and group decision.
I really liked his statement that “failure to get motivational factors right is probably the single greatest cause of failure in collective intelligence experiments”. That’s insightful, and useful.
The implications for informal learning are obvious, I’ll have to think more about formal learning. Still, a great foundation for thinking about using networks in productive ways. Definitely worth a look.