The FASTForward blog has an interesting case study of a wiki being used for a corporate Intranet. It describes how Janssen-Cilag, an Australian pharmaceutical subsidiary of Johnson & Johnson, switched from a static HTML site to using a wiki. They chose the Confluence package and provided staff with just 5 minutes of training. Apparently many of the employees do not know it is a wiki and just think of it as an easy to use intranet.
The Trades Union Congress (TUC) has produced two guides on the use of Facebook and social networking at work. The TUC’s advice to employees is at http://www.worksmart.org.uk/rights/socialnetworking and the briefing for employers can be found at http://www.tuc.org.uk/extras/facinguptofacebook.pdf
A question frequently asked on UKeiG Web 2.0 workshops is “are there any guidelines on acceptable use and best practice for using third party services such as Blogger and PBwiki?” In a recent blog posting, Brian Kelly has listed three documents that look at the issues involved in using externally hosted Web 2.0 services:
Guidelines for Using External Services , University of Edinburgh Information Services
Checklist for assessing third-party IT services, Oxford University Computing Services
Risk Assessment For Use Of Third Party Web 2.0 Services, Brian Kelly, UKOLN
The IBM blogging policy and guidelines, dated 2005 but still relevant, are more concerned with behaviour rather than technology. Most of the document should be common sense but it sometimes seems that people leave their brains behind when they land on a blog or Facebook.
Accessibility of blogs for visually impaired people has already been mentioned in this blog. How to Make Your Blog Accessible to Blind Readers – American Foundation for the Blind is a good starting point.
1. Allow enough time for the discussion – a “traditional” meeting may last minutes to a couple of hours but a wiki meeting may take a day or longer.
2. Offer structure – for example populate the wiki page with questions and issues as well as the agenda .
3. Encourage participants to openly sign their contribution.
4. Provide participants with tools to follow the discussion, for example RSS feeds or email alerts.
5. Manage the discussion.
6. Capture actionable items.
7. Declare the meeting closed. “Give participants 3-4 hours’ notice to put in a last word. After, that, formally close the meeting. Post a notice at the beginning of the wiki page. Don’t leave the conversation open-ended. It’s discouraging.”
This has also been picked up and discussed further on the FASTForward blog.