This is a nice overview piece on using distributed communities of practice to boost your design/production teams, although there are a few oddities. It doesn’t seem written quite right to perfectly target either corporate or higher ed applications (though it could be very easily modified for either). On the corporate side, it’s a bit too…federated. I don’t know of many companies (even really big ones) that have a loose enough and geographically distributed enough command-and-control to allow for this. And in the cases where they do, there are often major cultural barriers due to organizational siloes (although, of course, that’s not a good reason not to try this strategy). Most corporations interested in trying this would benefit from a section on overcoming those barriers (which is typical in a KMish piece on CoP’s for corporations). On the whole, the strategy as written seems better suited to large universities, or maybe federated non-profits with lots of local chapters. The reference to SCORM makes me doubt that it was originally written with universities in mind, though.
Anyway, it’s a good place to start thinking about this stuff.
