« Look how far intranets have come..... | Main | Socializing the social in social computing »

January 14, 2008

Self-service publishing: Implement with care

Self-service social computing tools such as Wikis and Blogs offer fast routes to publishing and collaboration on an Intranet. These applications enrich the Intranet “Under Web;” the informal layer that foments beneath formal information channels.  (The “Under Web” concept was listed as one of the Trends for 2008)

The under Web taps into “real” work, using social computing to allow employees to connect, collaborate and innovate in ways previously unimaginable. At a recent IBF members meeting, I heard about remote engineering teams using a Wiki to share information between Russia and China. These teams used this tool to share knowledge about work they did not know had been done elsewhere. It was a good example of how a Wiki can empower a global workforce to connect and collaborate.

For an Intranet to derive the most value from this informal space, tools must be implemented carefully.

First of all, it's important to provide Wikis and Blogs only after processes for publishing “formal” information channels to the Intranet are well established.  If the right people are publishing to the right place on the Intranet, and there is good editorial workflow and governance, then the Intranet is sturdy enough to add an open, less-structured layer of content. If there are no good controls in place, then handing everyone a Wiki to use will blur the lines between informal and formal communication. What’s worse, it may threaten the information structure needed to support robust personalization and effective information discovery.

Some organizations may be able to pull off a totally self-published Intranet, but these organizations tend to be smaller, more focused, and will have a very strong culture of online communication.

Here are some more tips for getting the best out of self-service publishing.

  •  Log in using common authentication to ensure accountability for posts or edits.
  • Establish User Experience guidelines that distinguish
    the Wiki or Blog space from the more formal layers of the Intranet, yet still
    visually connect these spaces to the Intranet as a whole.
  • Publish and, if possible, require acceptance of,
    codes of conduct for self-service publishing. Better yet, make sure online
    communication is included in the overall code of conduct for the corporation.
  • Publish FAQs or Help for getting started, how-to
    and etiquette.
  • Search: Require Wiki and Blog owners to “opt-in”
    to include their content in Intranet-wide search.
  • Require labels or tags before publishing.
  • Automate archiving after a certain amount of
    inactivity.
  • Use RSS output if available to provide feeds of
    Wiki content into Portal implementation (or elsewhere, as desired, on the
    Intranet)
  •  Finally, leverage the power of this technology
    by training content managers and editors to connect their formal content
    (stories, news articles, features, etc.) with these informal channels. CMS
    templates should allow content authors to easily add links to related Wikis
    and/or Blogs in a consistent location. Easiest is to build a template that
    provides a search result window for wiki and blog-generated buzz on the topic
    of the story.

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d8341d635f53ef00e54fddb4668833

Listed below are links to weblogs that reference Self-service publishing: Implement with care:

» Self-service publishing: Implement with care from Column Two
Abigail Lewis-Bowen writes about carefully implementing wikis and other enterprise 2.0 tools. To quote: First of all, it's important to provide Wikis and Blogs only after processes for publishing formal information channels to the Intrane... [Read More]

Comments

I agree with pretty much all you say here, except that I think we have to stop talking about the under Web. This kind of collaboratively produced, less formal content will have an equal part to play in the blended intranets of the near future. See my blog for more thoughts on blending.....

Hi Ross, thanks for your comment. I totally agree that this less formal content plays an equal, if not more than equal part on Intranets of the near future, as you say. But I do like the Under Web notion. For me this term invokes a kind of "bubbling up" of knowledge and connections from the grassroots level of an organization. I don't really hear anything unimportant or irrelevant in this term. But.. if not Under Web, what else? I'd love to hear some ideas. (FreeNet? GrassWeb? SocialNet?.. okay, maybe not!)

Abigail - I hadn't heard of the term "under web" prior to reading your blog post. Ultimately, you are talking about UGC (I know, I hate the acronym, too) on a grassroots level. Bottom-upNet works for me, though, that's a mouthful, too.

Ultimately, you are describing the UGC from individuals without access nor authority with the formal communication channels. Externally, I suppose we call those folks bloggers, internally?

Your blog post certainly has me thinking, and I will noodle on this for a while.

What do you see the role of intermediaries between the raw, and sometimes untagged/uncategorized content and the formal editorial channels? Would intermediaries be automatic via search or would you see people playing this role?

Thanks!

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Working...
Your comment could not be posted. Error type:
Your comment has been posted. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.

Working...

Post a comment