How to Design a Community to Reflect Your Relationship With Your Community Members?

Earlier, I had shared my thoughts on the Social CRM use cases report from Jeremiah Owyang (@jowyang) and Ray Wang (@rwang0) and shared ten use cases for corporate online communities.

Now, Michael Specht (@mspecht) and my colleague Gautam Ghosh (@gautamghosh) have extended the same thinking to talent and employee communities across the “employee life cycle”.

Gautam’s post also has implications for how we think about designing communities in general. Basically, Gautam says that communities can be designed to enable four types of communication:

1. From few to many: Blogs
2. From many to few: Ideation platforms
3. Between few: Wikis
4. Between many: Forums and social networks

It’s easy to see that the relationship between the host company and the community members is dramatically different in these four contexts and the choice of a platform will define (and limit) the relationship. It is true for employee communities, but it is also true for customer and partner communities. Fascinating.

I build and nurture online communities as CEO of 2020 Social. Read my bio, interview me for a media story, invite me to speak at a conference or ask me how2020 Social can help you build and nurture online communities. E-mail me at [email protected], call me at +91-9999856940, or connect with me on Twitter, Facebook, LinkedIn, YouTube, or Slideshare.

Related posts:

  1. How to Reward Employee Contributions in Enterprise Communities?
  2. When Choosing Your Community Name, Ask: Will Community Members Wear It On Their T-Shirts
  3. What Are the Biggest Use Cases For Corporate Online Communities?

Link to original post



Leave a Reply