Skip navigation
Here's how to resonate with readers when communicating on an internal platform like Jive:

 

 

 

First, tackle the big questions.
What is the article about? Make sure your topic has broad appeal.
Who is involved? Who should know about it?
When did/will it happen?
Where did/will it happen?
Why did/will it happen?
How did/will it happen?

 

Next, consider the purpose.
What’s the one key message? In other words, what do you want readers to remember after they’ve read it?
Why should they know about it and how will it affect them or their work? What do you want them to do after they’ve read it? And most importantly, why should they care?

 

Add a fresh perspective.
When crafting a message, don’t forget to consider your angle. Is there a something special about this message that will hook readers and make it stand out? Consider putting content into context by framing it with anecdotes or personal experiences.

 

Now, add the detail.
If you want them to take action, spell out what you want them to do.
Who (if anyone) should be quoted? What message should he or she convey?
Are there others who should be quoted or acknowledged? If so, either mention them or provide a list at the end.

 

Sum it all up.
Sometimes it’s easier to write the piece first and add the headline afterward. And sometimes, writing the headline first helps you formulate your message and organize your content. No matter the order you write them in, be sure to include:
    • a headline that captures the essence of the message,
    • a subhead that adds more detail, or
    • a synopsis that sums up the content in one to three sentences.

 

 

Do a clean sweep.
Once your draft is done, edit for extraneous words and nonessential information. Your readers are busy, so the simpler—and shorter—the better.

 

Finally, add the visuals.
If you have relevant photos or videos, don't forget to include them.

Hello Jivers

 

For those of you who don't use streams, now is the time to start... and 'ps' this is a BIG SELL for Jive in your organizations because following a place in a stream (and then setting it as Home) can make the difference between a platform that is overwhelming with information, and a place that is a highly customized and relevant, mobile-enabled place to follow your projects.

 

Click 'New Stream'

Screen Shot 2014-10-17 at 9.08.17 AM.png

Name it "Corp. Comms / HR"

Screen Shot 2014-10-17 at 9.09.17 AM.png

Type "HR" into the search on the right and scroll down to find the Project entitled "Jive for HR and Corporate Communications" that Dennis Pearce has set up for us all to follow this use case discussion:

Screen Shot 2014-10-17 at 9.10.38 AM.png

Click "Add", and you will be following this place in your stream. Click Done.

Screen Shot 2014-10-17 at 9.10.53 AM.png

Now you will have a stream customized with all the discussions in that Project so it is easy for you to follow/contribute, from your cell anytime.

Screen Shot 2014-10-17 at 9.11.31 AM.png

Don't forget... you can set this as 'Home' while you are working on it:

Screen Shot 2014-10-17 at 9.11.40 AM.png

 

Tip: I find that following 'places' is very efficient in streams. When you add people you sometimes get 'too much information' because you are getting everything that person is doing (which may be lots of stuff outside of your project/subject). It's good to set up a stream to follow your direct reports/team, and it is awesome for the on-boarding use case where a newcomer will follow a colleague/mentor to learn. And the best thing is that when you are done with that project/subject/team, simply delete the stream and move on. Having just 9 custom streams keeps you focused!

 

And by the way... this type of group or "Project Stream" can be a game-changer for skeptics

In a large corporation, you'll never please everyone. A sure fire way to get on your new adopters' bad side is to cause a lot of noise in their corporate email inboxes.

 

Here are a few suggestions to help users manage the noise from day one.

 

  1. Educate them about email preferences at the stream level and in their Profile Preferences. Be sure you understand the full functionality of the Email Watch stream if you're converting from an earlier version (ie. before v7).
  2. Encourage smart stream management - explain the difference in following places versus following people (hint: Places generate a lot of noise).
  3. If you're using Jive's Auto-Follow plug in, use it selectively and recognize that content is king - don't waste your audience's valuable time and attention on something that would be more effective in another channel.

 

These are just a few ideas to get started - I'd be thrilled to hear more from the community!

First of all, I don't want to put the Jive team on the spot here, I'm just sharing experiences, that might be interesting to other community members.

 

So, the document preview in Jive. I, like most people that use Jive, have a love-hate relationship with it. It's a great feature, to be able to view a document without having to download it first.

However, on many occasions the layout of documents (especially Excel and PPT) is botched up pretty badly, so that I have to download the doc anyway. Also the flash based viewer isn't particularly snappy at times.

All in all, it's a "good enough" solution in most cases.

 

In one of our products we need to show binary content (Word doc, Powerpoints, Visio, etc) in the browser. For many other things we rely on Jive, but the document preview feature is not available to Jive add-ons so we had roll our own for this.

Also, the support for Visio and MS Project files isn't in Jive anyway.

 

We settled on a commercial solution eventually, and I thought it would be interesting to have some comparison between the document rendering in Jive and other solutions.

Word document

OriginalJive previewIn our app using 3rd party library
word1.pngword1.pngdeb70108-b818-4bf8-9db8-53fe6a4e65d5_Installation Guide - Lotus Notes Social Connector for Jive.docx_image1.jpg
word2.pngword2.pngdeb70108-b818-4bf8-9db8-53fe6a4e65d5_Installation Guide - Lotus Notes Social Connector for Jive.docx_image2.jpg
word3.pngword3.pngdeb70108-b818-4bf8-9db8-53fe6a4e65d5_Installation Guide - Lotus Notes Social Connector for Jive.docx_image3.jpg
word4.pngword4.pngdeb70108-b818-4bf8-9db8-53fe6a4e65d5_Installation Guide - Lotus Notes Social Connector for Jive.docx_image5.jpg

 

PowerPoint

OriginalJive previewOur app with 3rd party library
powerpoint1.pngpowerpoint1.pnga0285afd-6030-4c60-a40a-9ceacf4b475f_New Jive Corp Deck-1.pptx_image2.jpg
powerpoint2.pngpowerpoint2.pnga0285afd-6030-4c60-a40a-9ceacf4b475f_New Jive Corp Deck-1.pptx_image8.jpg
powerpoint3.pngpowerpoint3.pnga0285afd-6030-4c60-a40a-9ceacf4b475f_New Jive Corp Deck-1.pptx_image9.jpg
powerpoint4.pngpowerpoint4.pnga0285afd-6030-4c60-a40a-9ceacf4b475f_New Jive Corp Deck-1.pptx_image25.jpg
powerpoint.pngpowerpoint5.pnga0285afd-6030-4c60-a40a-9ceacf4b475f_New Jive Corp Deck-1.pptx_image26.jpg

 

Generally, Jive has gotten a lot better in the quality of conversion, but I think it's fair to say it doesn't compare well to specialized solutions (or Office365 for that matter). Maybe as part of the Box partnership, Jive could leverage Box View as an option for this at some point.

Internal Communities managers, is this topic something that is on your radar also?

During most internal community implementations, whether it is an upgrade or a brand new launch, a common question emerges; should we provide all departments or groups with a presence on our intranet?   The simple answer is no, and based on recent project experience here is a few items to consider.

 

  1. Don’t migrate a bad presence to a new platform.  Often times when we are migrating an intranet to a new platform (Or upgrading it), users want to migrate all content and all containers.  A new platform is rarely a complete fix to a lack luster department presence.  Review the purpose of each department page before migrating it.  If there is NO strong need for the content or the department presence, save yourself the effort and reduce the clutter.
  2. Department pages rarely keep themselves up to date.  One of the best ways to keep a department page up to date is to ensure it has an engaged owner.  If neither the community manger nor a department representative is willing to manage the page- consider holding off on its creation until someone is available to ensure content is kept fresh.
  3. Department pages do not have to be organized according to your org structure.  Often we find that the way users are organized in an org structure is not necessarily the way they work together or collaborate.  Create places based on needs not departments to ensure ease of use and to avoid unnecessary silos.
  4. It’s OK to develop places as needed.  Creating a lot of places for departments who are not ready to collaborate creates the illusion of a stale community.  Create places only for those who need it now, this will allow the activity to show through. A vibrant community becomes its own activation tactic, as new users will check out the community and look for a place to make their own.
  5. Only reference content which is useful.  A description of the department, all of it’s managers, and every document/ phone number or resource the department has ever created is not always needed on the home page of a department place.  Only highlight highly used or very valuable items, and continuously monitor performance and user needs to update appropriately.

 

 

In Summary, to ensure you are creating meaningful places for communication and collaboration follow these 4 steps:

  1. Have a purpose. Ensure the page has a strong use case and is not just a legacy page.
  2. Ensure you have an engaged and trained owner to keep the page fresh
  3. Create places to collaborate and communicate based on user needs
  4. Consider rolling places out in waves according to needs.
  5. When you do create the place make sure to design it according to the specific group’s needs, ensuring unnecessary features or page elements are turned off.

 

 

 

 

Adams, Scott. "Comic Strip." Cartoon. dilbert.com 03 Feb. 1997. 01 Nov. 2014 <http://dilbert.com/strips/comic/1997-02-03/>

Filter Blog

By date: By tag: