I wanted to kick off a new round of blog posts that focus in on the design process that the team here at Jive took to design and build Clearstep.
The main driver for Clearstep was to help our customers answer the question, "What do I do next?" As part of our professional services organization at the time, I helped a number of our customers out with this question. It was just natural for Jive to create a community to focus on the non-technical aspects of using our software for Online Communities as well as Internal Collaboration.
The concept for the project started about a year ago, initially as a subspace on the developer community, then was transfered ownership an external consulting firm, before I took the project over. That's lesson #1: Have a dedicated project stakeholder associated with the community that has access to the resources necessary to complete the project. I took the project over in early 2008 and started the design process, using the same methodology I've been coaching our clients through. It is this process (reflected in the tag group organization in the Build community) that I will be blogging on over the next couple of weeks.
Our rollout plan was fairly aggressive once we nailed the purpose, design, and structure. I'll go into more details in a subsequent approach around our rollout strategy and plan, but one of the big decisions we made was to go live early on our latest Clearspace Community 2.5 platform (BTW - we just announced availability of it today!)
One of the reasons we decided to run Clearstep on beta code of Clearspace Community was because of the Groups and Friending functionality. We knew that one of the big goals of Clearstep was to connect people who are in the process of implementing social technologies to people who have already done it. You will be noticing some changes over the next couple of weeks to make this more apparent on Clearstep. We will also be featuring some community managers and others who have "been there, done that" and have them post about their experiences.
Also, I knew that no matter what, the community will evolve and shift based on topic interest. Despite all our best research on what the right taxonomy should be, we know that community members would want to talk about certain things that don't necessarily fit into the overall community structure. Thus, we have started implementing the Groups functionality. Again, over the next couple of weeks you will see specific groups form that are more focused around a specific topic, or group of people. For example, there is a OMS Group (Online Marketing Summit) that is available for anyone to join. This group is targeted around those who attended the Online Marketing Summit that I spoke at over the past couple of weeks. If you have suggestions of what groups you would like to see created, let me know.
So, over the next couple of weeks you will see a series of posts talking about what it took to design and build this community. I will be posting about our goals & objects, member personas, community characteristics, content management plans, and go-live checklists. Stay tuned!


