Nathan @ e-gineer: Our Intranet, the Wiki: Case Study of a Wiki changing an En... - The Diigo Meta page

• 21 Mar 09
  

  Dale Pike

  cms confluence intranet wiki Tags

• 08 Jan 09
  

  cas entreprise entreprise 2.0 enterprise 2.0 intranet

• 10 Dec 08
  

  Workcolab .
• 29 Oct 08
  

  Christophe Deschamps

  cas entreprise entreprise 2.0 enterprise 2.0 intranet

• 07 Jul 08
  

  Richard Fahey

  wiki collaboration web2.0 confluence intranet enterprise2.0 pharma

• 22 Apr 08
  

  Stephen Carr

  LavTalks google-bookmarks

• 09 Oct 07
  

  Steve Mackenzie

  wiki_casestudy wiki_modelsofuse

• 06 Oct 07
  

  Emanuele Quintarelli

  2007 case studies confluence enterprise 2.0 enterprise wikis janssen-cilag pharma

• 02 Oct 07
  

  Mark -

  enterprise productivity training wiki

  • In 2006, Janssen-Cilag completely replaced our simple, static HTML intranet with a Wiki solution. Over the 16 months since launch, it has dramatically transformed our internal communication and continues to increase in both visits and content contributions each month.
  • • We need a trusted source of information
    • Whatever we do has to be simple
    • Just do something!
  • 6 more annotations...
  • • • We need a system where editing is immediate and very simple.
      • Getting people to contribute at all is hard, so we need to concentrate on letting people do things rather than worrying about what they shouldn't do.
      • The risk of letting anyone change anything is low, since we'll keep a complete history of changes so we can quickly undo mistakes and we can hold irresponsible individuals accountable for anything improper. (Reactive moderation rather than Proactive moderation).

    • After evaluating a wide range of alternatives including MediaWiki, Twiki and FlexWiki; we selected Confluence by Atlassian. Our main concerns were support for a hierarchy of pages, strong attachment capabilities, news features, LDAP integration, high quality search and a decent rich text editor.

      

      Our customisation focused almost completely on usability. People shouldn't know or care that they are using a Wiki. All that matters is that they can easily browse, search and contribute content. (In fact, after 16 months, only a small set of Janssen-Cilag staff would think of our Intranet as a Wiki. To them, it just seems natural that Intranet software would have evolved to something this simple to use.)

      Here were our implementation decisions:

      • Integration with LDAP and use of NTLM for automatic single sign on is essential. We even hacked someone's starting point and open sourced our improved version.
      • Rich text editing must be available and as Word-like as possible.
      • Users like hierarchy and structure, the Wiki should not feel disorganised or completely free-form. (Confluence supports this with an exact page hierarchy capability.)
      • Sacrifice power and flexibility for simplicity. For example, our page design is fixed into a title, alphabetical list of subpages, page content, alphabetical list of attachments. While it would be nice to be able to change this at times, or order the attachments, or change the look and feel; it's far more important that everyone can contribute and clearly understands how things work.
      • Remove as many unnecessary features as possible. For example, labels are a great idea, but we already have hierarchy and most users don't really know what labels are.
    • Launch & user training

    • Our launch was timed with an informal head office monthly meeting, where around 100 people stand and listen to an update from senior management. We switched the site to live during the meeting, and had 5 minutes to present:

      1. 1 min: Highlight the desire for a trusted source of information that was simple to use.
      2. 3 mins: Full training that showed how easy it was to view, search, edit & maintain.
      3. 1 min: Point out that responsibility for building that trusted source is now in your hands!
    • The adoption of JCintra has been remarkable. After only 3 months, 111 people had contributed more than 5,000 changes. After 12 months, we had 18,000 contributions from 184 people within the business.

    • Content ownership model

      For many Intranet owners, the model for content ownership is a key point of focus. With JCintra, our philosophy (successfully so far) has been:

      1. If someone isn't willing to maintain a piece of content, it can't be that important to the business.
      2. We happily show people how to do things with the site, but we don't do it for them.
      3. Occasionally we highlight sections of the site on the home page, which is a great way to drive the defacto owners to clean it up a little.
      4. We encourage people to have high expectations for content on the Intranet. If something is missing, please report it to the appropriate area of the business, or better still, add it for them.
      5. The answer to verbal queries for many departments has become, "it's on JCintra". This reminds people to search first and ask later.
      6. In the end, the quality of content in an area is a reflection on the defacto department owner, not the Intranet itself.
• 23 Sep 07
  

  Rotkapchen .

  Enterprise2.0

• 20 Sep 07
  

  Jim Hanna

  confluence wikiusage wiki

• 19 Sep 07
  

  Joserra Mosteiro

  atlassian cms collaboration confluence management for:javali for:pumbinha wiki intranet web2.0 enterprise2.0

• 12 Sep 07
  

  Martin Koser

  The goal of technology is for it to be invisible, just the way that things are done, not some cumbersome monster. In my experience, many nonprofit and government organizations forget about this part

  adoption atlassian enterprise2.0 wiki collaboration intranet casestudy usability design web2.0

• 02 Sep 07
  

  glen gatin

  07:598 collaboration web2.0 wiki

• 27 Aug 07
  

  Nancy White

  wikis intranet knowledge_management business enterprise2.0

• 

  Mike taylor

  wiki tspo

• 23 Aug 07
  

  lauren pressley

  wiki business collaboration

• 

  Will Stewart

  business case collaboration corporate Enterprise enterprise2.0 study transparency web2.0 wiki wikis intranet Confluence

• 21 Aug 07
  

  Frank Hamm

  In 2006, Janssen-Cilag completely replaced our simple, static HTML intranet with a Wiki solution. Over the 16 months since launch, it has dramatically transformed our internal communication and continues to increase in both visits and content ...

  wiki case-study intranet pharma australia

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.