Jannsen Cilag Wiki-intranet case study

By Alex Manchester, Editor, The Internal Comms Hub (Australia), Melcrum

The Janssen Cilag case study was one of the standout presentations at last week's Enterprise 2.0 event (written about here, here and here), and chief architect Nathan Wallace has posted links to a full, written version:

• Case Study of a Wiki changing an Enterprise.
• Building Enterprise 2.0 on Culture 1.0.
• Clarify. Simplify. Implement.

The presentation slides are also available here

This is an excellent story with a focus on simplicity, user needs and "latent demand", which is a phrase I think we're going to hear more and more of in the future.

Another interesting point: few people refer to the new Intranet ("JCIntra") as a wiki, and even fewer care that that's what it is. It was written in our research and is something I've said many times in presentations and workshops in the past year: it doesn't matter if it's a blog, a wiki or whatever a tool is called. It's what it can do that's important.

My only question lies around JCIntra's scaleability. Jannsen Cilag is a subsidiary of Johnson & Johnson, with around 340 people. With the new intranet there's been practically no training and take up and use has been very high. The size of the project does not take anything away from it, and various elements - simplicity, ease of use, roll out, structure, zero training etc. - could well provide a blueprint for bigger projects. But, if you were looking at a bigger intranet project, say for 10,000+ employees, would any aspects of this approach need to be changed?

Comments

[Stuart Peacock]

Hi Alex,
I would be interested to know about how the Confluence model integrates with (or not) the customer facing JC internet site?
Cheers, Stuart