1 person found this helpful
Wikis can become a huge ball of useless data very fast. You need to impose some organization and standardization to help people. You need to look at how all of those pages get searched and if that search integrates with the other communications and publishing platforms, such as an intranet. Typically, I have seen engineering groups grab wikis and run with them, but very few other organizations end up using them.
If this is really a community and not a wiki, then you need to rebrand it quickly to avoid people automatically thinking, I know what a wiki is and I do not want one".
Mike, UBM calls their Jive SBS instance "the Wiki"... I know. It's confusing.
Rebranding is really outside my scope of work. And the boat for that decision has long since sailed. Besides, I don't think most of our users do in fact know what a wiki is. Some do, but those aren't having an issue with the fact that this instance is different. But thanks for those comments.
And we have done quite a bit to help people get their content organized. We'll be concentrating on that even more this year. I think that the Categories will help some in that respect.
Is part of your role as administrator to evangelize the use of the system throughout UBM?
How many users do you have?
What was the state of the deployment when you inherited it?
Some folks seem to take to social systems like ducks to water while others have trouble using email and telephones. For those who will enjoy using your SBS deployment you'll probably just need to provide tips and tricks to get the most out of it but for those others you'll likely need a "carrot" of some sort to lure them (unsuspectingly) into the brave new world that the rest of us inhabit.