A community of practice is more than a website

1 reader likes this.
Core purpose

Opensource.com

A community of practice (CoP) is, according to cognitive anthropologists Jean Lave and Etienne Wenger, a group of people who share an interest, a craft, and/or a profession.

Over the last year or so, the term communities of practice has entered the social media buzzword lexicon along with virtual collaboration, engagement, platforms, and Enterprise 2.0. Senior leaders want to establish them, new employees are being told to join them, and middle managers are being told to support them, but what, exactly are they?

Nowhere in the definition above does it mention the words website, wiki, blog, or social network. Nowhere does it say that it has to be virtual or physical or even either/or. There is no reference to the tools that are used to facilitate the communication and collaboration, nor is there a defined set of characteristics that define how a community of practice works or what topics they discuss.

A group of people who share an interest, a craft and/or a profession. Sounds pretty simple, right? Sounds like we might already be members of dozens of communities of practice – at work, at church, at school, etc. It’s just a group of people communicating and collaborating openly around a topic that they all care about. CoPs have existed for as long as people have had a desire to learn from each other.

Whether your organization knows it or not, your company/government agency is already filled with CoPs. Just because all of their communication and collaboration doesn’t happen to occur on your designated SharePoint site doesn’t mean that people aren’t already communicating and collaborating around a shared topic of interest. Whether it’s the group of new hires who coordinate the monthly happy hours or the new parents who get together over lunch to discuss work/life balance, communities of practice are alive and well within most organizations. They just might not be the ones with a unique URL on the Intranet.

Are you creating a community of practice or are you just creating another website? How does your CoP stack up to some of these statements?

  • People voluntarily spend time helping others in a community of practice. People visit a website to download what they need.
  • CoPs focus on adding value to their members. Websites focus on getting new users.
  • The success of a CoP is measured in anecdotes, efficiencies, and employee satisfaction. The success of a website is measured by hits, visits, and referrals.
  • The members of a CoP volunteer their expertise to create new tech features. A website has paid developers who add new features.
  • A CoP is built around conversation. A website is built around content.

Communities of practice have been around for decades, and for decades, they’ve helped countless organizations navigate major changes, increase productivity, cut duplication, and make work more enjoyable. In many cases, the use of social media has enhanced these CoPs by providing more tools and opportunities for people to connect with other people. Unfortunately, social media has also given rise to zombie communities filled with content on blogs, forums, and wikis, but which lack any actual human interaction. What are you building?

For more about Communities of Practice, check out Cultivating Communities of Practice: A Guide to Managing Knowledge, Harvard Business School Press, 2002 by Etienne Wenger, Richard McDermott, and William M. Snyder.

User profile image.
My name is Steve Radick and I’m a Lead Associate with Booz Allen Hamilton, a global strategy and technology consulting firm that works with clients to deliver results that endure. I’m one of the leads for our social media/Government 2.0 practice, working with clients across the public sector to integrate social media strategies and tactics into their organizational strategies.

1 Comment

This is an excellent article. Thank you Steve. The Wenger, et al book is absolutely worth reading.

I agree that a CoP is more than tech features, however it is important to include the features needed for the community members to support each other. I manage an internal community at Children's Hospital Boston and our community is not made up of expertise to create new tech features.

Members want to voluntarily spend time helping others plan events, work through important issues, etc. The digital community allows us to do that with so many employees with different schedules and working from different parts of the world. If those tech features (message boards, calendars, todo lists) don't exist, it makes it tough for your community to do that.

If you want to enhance your CoP with websites, wikis, blogs, or social networks, you do need to think about the website itself.

Originally posted on steveradick.com.