Thanks for visiting the Digital Workplace Group (DWG) website. You'll see this post may refer to the "Intranet Benchmarking Forum (IBF)," the "Digital Workplace Forum (DWF)" or "IBF Live." But that doesn't match our website name!
In a nutshell, we merged IBF and DWF into one service and changed our name to "Digital Workplace Group." The new name represents the broader set of services we've grown to offer, beyond an original focus on just intranets. We also changed the name of our monthly webinar from "IBF Live" to "Digital Workplace Live."
Although we've relabelled things, we're proud of our decade+ history and have left this page intact. Enjoy your time on our site and please contact us with any questions or comments.
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 DWG 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
- 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
- Use RSS output if available to provide feeds of
Wiki content into Portal implementation (or elsewhere, as desired, on the
- 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.