Cultivating Communities of Practice Hardcover – March 15, 2002

i'm building Gaudeamus - the academic network for publishing in journals (gaudeamusacademia.com), an online community of scholars (professor, researchers and journals’ editors). It was founded to provide a tool for academics to help them to get their research published in journals, enabling them to network with editors and to share what they have learned and discovered about publishing.So this book has provided us with an useful guide to manage knowledge and with the theoretical bases to keep building and developing our globally distributed community.

Excellent book that mergers practical advise with theory. If you're only getting one book on CoPs, I would suggest this!

Great book! There are CoP's everywhere, but this book helps to outline HOW to get the CoP you want, with the results you need.

Cultivating Communities of Practice is the second book from Wenger which is only about Communities of Practice (COP). The first book was a little dry and academic (and intended to be), but this book is your typical business book, which makes it easy to read. Wenger is teaming up with Richard McDermontt and Willian Snyder, which probably helped a lot in the amount of real-life stories in the book.The books can be separated in two major parts. The first five chapters are about just about COP and the last five chapters are about COP related to other topics.The first two chapter are introduction chapters which talk about what COP is and what their value is to the organization. It also does a good job in separating COP from other communities. The three main elements of a COP is domain, community and practice. A COP related to a domain, creates or has a community and owns a set of practices within that domain. They are self-managing and emergent, which means that in organizations its hard to create them -- you need to cultivate them.The third chapter talks about the cultivation and the principles of doing so. I probably liked this chapter most, it's concrete and clear. It can be used directly in organizations who would like to promote communities.The next two chapters describe a typical life of a COP and the different stages they go through. Knowing the typical stages helps in deciding your actions to cultivate them.Interestingly, I wish I would have stopped reading after chapter 5. (which the exception of chapter 7). At this point I thought the book was one of the most interesting books I've read in a while, but then the second part was disappointing to me. Chapter six talks about distributes COP. It is still important, but somehow the tone of the chapter changes (or did my mood reading it?). Chapter seven was good again, about the downside or dysfunctions of COPs and what to do about it.Chapter eight, about measuring the value of COP, completely lost my interest. The writing style seemed to change (different author?) and the emergent, self-managed tone of the first couple chapters changes to a more controlling tone. The examples also changed and most related to McKinskey.Chapter nine is the typical "change" chapter of business books and describes the stages for implementing COP in organizations. Chapter ten tries to predict the future of COP. Though I felt chapter ten just miserably failed and it even seemed the authors moved away from their previous definition of COP and talked about communities in general.After the first five chapters, I would have rated this book five stars and would have recommended it to everyone. Though, the last five chapters would just be a three star rating, so I'll go for the average here.I'd strongly recommend to buy this book and read chapter 1-5 and 7.

I ordered this book on a co-workers "you need to drop everything you are doing and read this book" recommendation, and I must confess, it was immediately useful the day after I read it (and still two weeks later, after I've had a chance to share its insights with hundreds of people). And indeed I have found myself recommending it, despite numerous limitations.The strongest and most important contribution this book makes is to first define a robust definition of community and community practice within the command-and-control corporate hierarchy. I especially appreciated that the authors did not go overboard (as so many business authors do) and try to redefine absolutely everything in terms of their particular insight. Their restraint makes the first two chapters a very safe "if you care the least bit about this subject, you need to get grounded in these two chapters *now*".The most glaring omission of this book is that there is no discussion whatsoever about free/open source software. Granted the book was published in 2002, but by that time:* Netscape started the open source Mozilla project (1998)* Red Hat went public on NASDAQ, using a community-based R&D model (1999)* IBM committed to invest $1B into Linux (2000)* Amazon.com reported its first-ever profit, attributed in part to its use of Linux (2001)One possible explanation for this omission is that the authors wanted to leave technology (and thus technology-mediated practices) entirely out of their discussions. But the fact remains that the free software community, which was started explicitly as a community first (Free Software, Free Society: Selected Essays of Richard M. Stallman), and the open source movement (which was a combined commercial/community symbiosis, see Open Sources: Voices from the Open Source Revolution (O'Reilly Open Source)) are defining examples of the cultivation of communities of practice at the billion dollar level in 2002 (and now well past $10B today). Such an omission makes me very ambivalent about recommending this book to the communities I work within.Hopefully the authors will see fit to release a revised and updated version, one which maintains its neutral and yet insightful perspective, while also giving some much-deserved attention to both the free and open source software communities as well as the ways in which those communities have enabled other communities to operate (using the World Wide Web, Wikis, and other open source technologies).

This is one of the classics in the field of communities of practice, and deservedly so. I would consider it a "must-read" for anyone who wants to know more about how communities work. However, it's not a novice's book; it won't provide the nuts-and-bolts, step-by-step directions you may want if you are just getting started with communities of practice.

Very good practical model for building a community of practice.

Putting a group together now to focus on Poverty