Comments on: Jive SBS Rollout: Worst Practices http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/ Connected Tue, 11 Oct 2011 14:24:22 +0000 hourly 1 http://wordpress.org/?v=3.2 By: Mark P http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-3483 Mark P Tue, 05 Jan 2010 16:54:12 +0000 http://giatalks.com/?p=234#comment-3483 Never under-estimate the ability of sarcasim and irony to attract attention. Well done to Gia for making these points interesting - a skill most IT departments could do with learning! Never under-estimate the ability of sarcasim and irony to attract attention. Well done to Gia for making these points interesting – a skill most IT departments could do with learning!

]]> By: Kukulkan http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-3462 Kukulkan Fri, 04 Dec 2009 18:19:26 +0000 http://giatalks.com/?p=234#comment-3462 Hrm, your article is kind of amusing and brings up some good points - but it's not very useful. Wouldn't it have been more productive to make a list of potential pitfalls in rolling out SBS, with suggestions as to how they can be avoided/worked around? Just saying, it's a lot easier to snipe on the sidelines than it is to help improve a process. I can't help but wonder if any of your concerns and observations were expressed to your IT department or if you're just venting. :) Hrm, your article is kind of amusing and brings up some good points – but it’s not very useful. Wouldn’t it have been more productive to make a list of potential pitfalls in rolling out SBS, with suggestions as to how they can be avoided/worked around?

Just saying, it’s a lot easier to snipe on the sidelines than it is to help improve a process. I can’t help but wonder if any of your concerns and observations were expressed to your IT department or if you’re just venting. :)

]]> By: Gia Lyons http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-1363 Gia Lyons Wed, 01 Jul 2009 18:40:27 +0000 http://giatalks.com/?p=234#comment-1363 "Discuss your results in email... a lot." ROFL! Love it! And Laurie, totally get that all the time. Deploying to a group of people who already know each other and collaborate with one another isn't going to garner the best success stories. ;) And Mark, the "let's pretend to share but really let's don't" nature of private communities can be stepping stone to working in the clear, but yes, a very public statement about transparency should constantly be reinforced. “Discuss your results in email… a lot.” ROFL! Love it! And Laurie, totally get that all the time. Deploying to a group of people who already know each other and collaborate with one another isn’t going to garner the best success stories. ;) And Mark, the “let’s pretend to share but really let’s don’t” nature of private communities can be stepping stone to working in the clear, but yes, a very public statement about transparency should constantly be reinforced.

]]> By: Karyn German http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-1362 Karyn German Wed, 01 Jul 2009 17:54:54 +0000 http://giatalks.com/?p=234#comment-1362 This is a great post. Here are a few more - they are related to some of the ones you already posted, but with a slightly different spin: - Focus a lot of your feedback on people who do "stupid" stuff to make an example of them, because you certainly can't trust the community to do it for you. - Spend a lot of time working on large taxonomies of content, communities and people that require tedious maintenance by a team of KM professionals. - Don't bother with publishing guidelines - everyone will know the perfect use case for when to blog, use wikis or discussion forums. - Discuss your results in email…a lot. This is a great post. Here are a few more – they are related to some of the ones you already posted, but with a slightly different spin:
- Focus a lot of your feedback on people who do “stupid” stuff to make an example of them, because you certainly can’t trust the community to do it for you.
- Spend a lot of time working on large taxonomies of content, communities and people that require tedious maintenance by a team of KM professionals.
- Don’t bother with publishing guidelines – everyone will know the perfect use case for when to blog, use wikis or discussion forums.
- Discuss your results in email…a lot.

]]> By: Laurie Buczek http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-1353 Laurie Buczek Tue, 23 Jun 2009 17:36:19 +0000 http://giatalks.com/?p=234#comment-1353 Deploy social tools over an established silo. Deploy social tools over an established silo.

]]> By: Mark D http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-1352 Mark D Mon, 22 Jun 2009 20:16:42 +0000 http://giatalks.com/?p=234#comment-1352 - Allow everyone to setup private communities with little or no resistance (or even asking them why. - Allow everyone to setup private communities with little or no resistance (or even asking them why.

]]> By: Gia Lyons http://www.giatalks.com/2009/06/jive-sbs-rollout-worst-practices/comment-page-1/#comment-1351 Gia Lyons Fri, 19 Jun 2009 19:41:34 +0000 http://giatalks.com/?p=234#comment-1351 More from my colleague, Greg: - Only grant login access to one department at a time - Have 27 required profile registration fields - Turn off reply by email - Misconfigure your email server so all invitations end up in Spam folders More from my colleague, Greg:

- Only grant login access to one department at a time
- Have 27 required profile registration fields
- Turn off reply by email
- Misconfigure your email server so all invitations end up in Spam folders

]]>