For your consideration thoughts I have captured from different Jivers in the Community:


If the sender pauses to think about the nature of the communication and its intended audience, they should be able to easily determine the appropriate tool:


  • Team communication - use JIVE to send shared content, updates or start conversations within the team.  Avoid using email, or leverage the Incoming email service to forward an email thread into JIVE content to continue the conversation in the appropriate forum. In this manner, JIVE use displaces what many of us have used email for in the last 10 years or so...
  • Private message / small audience - still consider using JIVE if the content is appropriate for sharing, otherwise send a Real Time Chat ("message") using JIVE to the recipient, or default to standard email.
    • Email remains the default tool used with external audiences, especially if the organization hasn't adopted an external facing collaboration platform (such as JIVEx, etc.)
  • Organically linked content (knowledge) - use a Wiki, which allows the community to contribute and add dynamically linked content (not like you'd see in a Discussion thread, or a standard page / document format).  I've read other posts about how JIVE and other social platforms allow organic growth and addition of content, but from my experience I don't believe JIVE offers a true Wiki experience.  I could be wrong here, but that use case would require a distinct tool in my mind.

So, JIVE isn't just another tool added to the pile, but displaces a large portion of communication sent within an organization. There are exceptions to this, but as a general rule I believe a lot of communication sent internally is meant to be shared.


Another point of view:


  1. Email
    1. Works when you want to make sure someone gets your message. Like it or not, most people still "live" in email, and using email to deliver a message allows you to ensure that it reaches the audience.
    2. Works if you need to deliver a message using a distribution list and feel the need to ensure delivery (not necessarily that it was read).
  2. Blog - Personal opinion based on my own interactions with blogs are that they are best for a technical audience. If you have an IT team that like using them, let them continue using it for their existing workflow.
  3. Jive


  1. Delivery of messages to a large audience that doesn't share a single email platform or where a distribution list doesn't exist and can't easily be created.
  2. Any time you want to solicit or encourage feedback, whether that be to a "memo", announcement or otherwise. For example, if the CEO sends out an email announcement about something, people are reluctant to respond. It feels like one-way communication. If the CEO instead creates a blog post as an announcement, people feel empowered to response, ask questions, etc.
  3. Conversations. People will often use email in place of a phone conversation or meeting. Jive works much better because you don't have the experience of accidentally dropping part of the audience, having the thread get fragmented, having the email get "lost" because it was moved to a folder. And if the conversation is "open" in Jive, other people can find and comment, and important perspectives can get added that would never have surfaced in email due to the closed nature of it.
  4. Collaboration on content by non-technical employees. Examples are for product management, RFPs and other content that required input from a number of sources. Using Jive for Office, people can simultaneously edit documents and thus move toward the final version with more speed and ease than using email (where often you end up needing to manually merge multiple versions of a file). Technical folks often prefer wiki format.
  5. Reference material. Examples here are benefits information, product documents, help information, etc.
  6. Facilitating a help desk - JiveX has functionality to accommodate this for external communities. Even as an internal community, the functionality works well and only improves with newer versions of the platform. We use it this way for support questions raised about the Jive platform itself. One of the benefits is that for employees who are willing to search, it can create a great self-help database.