I regularly get feedback from users that they want to use a "web site" to store and organize documents so that it is "easier" for their users to find stuff (the content owners want to choose the layout, order, etc. of the content). But then they want a sense of community and when they hear of the various social interactions that come from Jive, they want those as well. But they feel that they can only get a good "user experience" via the web site.
How do you address the document repository question? Posting to a non-social intranet may allow for you to layout your attachments in a nice way, but the ability to share, mention, follow, comment, re-post, etc. is lost. Is there a Jive feature that would help resolve this or some best practices or tips that would help a team make this paradigm shift? I think that the users also have to make this shift. Some people don't like to have to look for content. They want to be told what to review and where to find it.
I know that they can customize their group overview page and can feature content. But is it a best practice for them to add links to a large volume of content on the overview page? That appears to be a way for the content to still be layed out as they want, but to also be social, so that is a good thing. Is it worth the set-up work involved (1st upload attachment, then update overview page with the reference links, and then to regularly maintain that list of attachments)? I'm curious what others have done to balance the document repository question when they don't just want a folder view, they want it all organized for their users.
Several teams are open to this new paradigm, but I need a compelling message to share with a specific team on 7/30/13 (yes, tomorrow). My existing messages have not made a sufficient impact with this particular team, so I'm trying to improve my message. Any help is appreciated.
I saw Gia Lyons' social intranets post and agree with what she shared, but I need a little more. I know that some companies have Jive set up as their main employee portal/intranet. So I maybe just need to know what technology was needed to accomplish that.
Alos, maybe it would help if I defined this particular scenario:
- This will be used for executive leader orientation
- A lot of resources will be posted by those responsible for the program
- This is replacing an event that has previously been delivered live; to cut costs, they are taking this virtual
- Although we have the SharePoint connector, the content is not stored on a traditional SharePoint site/library, but rather the Moss version that allows it to look and feel like a web site rather than a SharePoint site. From what I understand, this level of integration is not available.