Tag Archive for 'jive software'

Don't Miss Innotech This Week in Portland!

I wanted to just remind everyone about InnoTech here in Portland this week. I will be there on Wednesday and Thursday, April 16th and 17th.

A few things that I am involved in or excited about:

  • Jive Software CEO, Dave Hersh, is presenting on “Ready or Not? Assessing Your Collaboration 2.0 Preparedness” at 9:30am on April 17th. Dave is a great speaker, so you won’t want to miss it!
  • The eMarketing Summit has some great content, and it will be kicked off on the 16th with a panel including Dawn Foster (me), Jeff Hardison, Kerry McClenahan, and Barry Tallis to talk about Strategies for Planning & Building an Online Community
  • I will also be moderating a panel about Open Source Communities on April 17th with some amazing panelists and open source rock stars: whurley, Stormy Peters, Danese Cooper, and John Mark Walker. The session is part of an all day open source tracking being organized by Raven Zachary.
  • There are many other great sessions at InnoTech including: Don Tapscott (author of Wikinomics), Ward Cunninham (inventor of the wiki), Brian Jamison, Andrew Aitken, Jason Mauer, Steve Morris, and many more.

Cost-wise, this event is really reasonable, and it is a great opportunity to learn and meet interesting people.

Clearspace 2.0, Acquisition of Jotlet, Openfire Enterprise Goes Open Source and more

This weekend, we announced a bunch of changes at Jive.

We released Clearspace 2.0, including a renaming of Clearspace X to Clearspace Community. We also upgraded Jivespace to Clearspace Community 2.0 with an update to the look and feel, so I’ve spent a fair amount of time yesterday and today doing lots of testing and some tweaking.

Jive announced our acquisition of Jotlet. While I love to see Jive acquiring cool technology, I am even more excited that Adam Wulf relocated from Texas to Portland as part of the acquisition. Make sure you give @adamwulf a big Portland tech community welcome.

While Openfire has been open source for a long time, Openfire Enterprise had been a proprietary add-on to the open source version … until now. Openfire Enterprise is also being released under an opn source license.

The press has also been writing about the changes (search Google News if you don’t believe me). I won’t go into too much detail here, since the blog posts linked above have a bunch of details, but I am excited about the changes!

Jive Software Moving to Club Fed

Jive finally signed the lease to take over several floors in the Federal Reserve building on 9th and Stark with a move in date happening sometime this summer. The new building has already been nicknamed Club Fed by my fellow Jivers. Right now, we are sitting on top of each other in the current space. We have people at tables pushed up against walls and windows wherever we can find enough space for a computer & chair, so we are really looking forward to having some more room.

The article in the Daily Journal of Commerce had a pretty interesting description of what Jive Software is all about:

The Portland-based company specializes in flexible-source and web-forum software – programs that users can tweak and manipulate to suit their needs, and which are easy to configure with existing operating systems like Firefox. The company’s Clearspace software, for example, helps companies manage the flow of information between members of a team, in much the same way as a wiki.

Despite the minor faux pas of calling Firefox an operating system, the details of the move look good. And you can even see the top of my head in the second cubicle in the tiny picture at the top of the article :-)

Clearspace: Best Community Software Award from InfoWorld!

w00t! Jive Software’s Clearspace X just won the Best Community Platform award from InfoWorld! You can read their full review on the InfoWorld site. This is no surprise to me. We power the 2 communities that I manage, Jivespace and Ignite Realtime, on Clearspace X.

Did you know that you can get a free license for Clearspace X if you are a non-commercial open source project or developer group? This is one of the cool parts of my of my job … I get to give people free software :-)

How to Structure a Community

Last week, I posted a piece on the Jive Talks blog with ideas for how to structure a community:

If you want a community (internal or external) where social productivity can be optimized, you need to put quite a bit of thought into how the community will be structured. In addition to productivity concerns, this initial structure can also impact the adoption of your new community. The challenges include how much or how little structure should be provided and then what kind of promotion/coaching/training should follow the initial implementation. The amount of structure falls into three main categories: emergent, highly structured, and adaptive.

In the post, I go into more detail about the pros and cons of each of the three types of structures (emergent, highly structured, and adaptive). I thought some of the Fast Wonder readers might also be interested in reading it. The full content of the post is on the Jive Talks blog.

I also have a Fast Wonder podcast on the topic of community structure that should go out sometime this weekend.

Related Fast Wonder blog posts:

Community Roles: Manager, Moderator, and Administrator

I was asked an interesting question last week about the best ways to divide the community manager role into separate manager, moderator, and administrator roles. In my role as community manager at Jive, I act in all three roles under the broader title of community manager with plenty of help from the web development team on the administrative side and participation from development and product management with answers to questions.

In small to medium sized communities, I suspect that a single person typically performs all three roles. In most cases, and in my case, the community manager also performs the moderation functions. If the community gets enough traffic, it would probably make sense to have a separate moderator role to handle the load. This question got me thinking about how the roles might be divided for very large communities.

If you were going to break them out into separate positions, I have two scenarios (although there are probably many more):

Scenario 1: The Enormous Community

In reality, I suspect that these would only be full time jobs for 3+ people in a large community.

  • Community Moderator: The moderator or moderators would focus on day to day responsibilities for the community. Reading the threads, making sure that the right people are answering questions, moving threads when posted in the wrong place, dealing with spammers, and other day to day maintenance in the community.
  • Community Manager: This person would be responsible for the overall direction of the community. They would be responsible for content plans, content creation, determining new functionality, and evolving the community.
  • Community Administrator: This person (or team) would be responsible for the software and other technical aspects on the community (maintenance, upgrades, implementing new features, etc.)

Scenario 2: The Medium to Large Community

For most medium sized communities and for new communities, I would start with this approach and then further separate the roles as community growth required more focused time commitments.

  • Community Moderators: Subject matter experts responsible for a specific area within the community as part of their regular job. For example, the product manager might be responsible for the feature requests area within the community. Moderation would be a small part of several people’s jobs. In this role of community moderator as expert, they would stimulate discussion by responding thoughtfully to posts and starting new discussions to get feedback on ideas or get the community thinking about a specific topic. It would also be good to have them blogging in the community within their areas of expertise.
  • Community Manager: This person would be responsible for the overall direction of the community – probably a full-time job. They would be responsible for content plans, content creation, determining new functionality, and evolving the community, but would also be focused on day to day responsibilities for the community. Reading the threads, making sure that the right people are answering questions, moving threads when posted in the wrong place, dealing with spammers, and other day to day maintenance in the community. The community manager would make sure that the community moderators are keeping up with their assigned areas.
  • Web developer / administrator: Unless your software is an extremely complex or custom solution, it probably makes sense to have one of your web developers or admins also administer the community software.

I think that what I have said above is probably more applicable to corporate communities; however, I think that these roles are similar in other types of communities. For example, in open source communities, community members typically pick up most of the moderation role in an informal capacity. This is certainly the case with the Ignite Realtime community – most of the moderation is really done by the community, and I usually only step in for any larger issues. I suspect that this is also true for social communities as well.

In general, there is probably quite a bit of overlap between community administrator, manager, and moderator. I would be curious to hear about how other people have successfully (or not so successfully) broken out the role of community manager.

Related Fast Wonder Blog Posts: