http://www.cio.com/article/389613/Three_Things_the_CIA_Learned_About_Implementing_an_Enterprise_Wiki?page=1
I’d imagine the CIA is extremely sensitive about information published to a Wiki so its good to see what they see as important.
The 3 items:
- Appropriate access policies. some people can only view, some can edit, wiki divided into public, secret and top secret areas.
- Start small. Basically people need to get comfortable with the technology and the change in process.
- Move process out of channels and into platforms. Eg, instead of the email to 50 staff just put it on the Wiki.
Its a good read.
Issues like leaking of corporate secrets, confidentiality, liable, etc with the Enterprise Wiki.
“Companies need to be alert to the dangers that free comment made in wikis and blogs may be libellous or infringe employee rights laws.” - Crispin O’Brien, KPMG’s head of technology
The KPMG press release: http://www.kpmg.co.uk/news/detail.cfm?pr=2898
Article is http://www.socialmediatoday.com/SMC/13450
http://www.e2oh.com/2008/03/02/a-banana/ is an interesting article on the pitfalls and best practice from implementation of an enterprise wiki.
Items like “painting lines on the road” are important but equally not styming uptake with overly agressive security models, excessive taxonomy, and extreme management styles.
http://distributedresearch.net/wiki/index.php/Wiki_facilitation is practical on the process of facilitating wiki contribution. Simple concepts like not creating a full skeleton of blank pages for the wiki but rather concentrate effort on small content centres.
Starting to think about what the new Intranet is going to be. Initially the concept of a Wiki seems appropriate with broadly the following areas:
1. Corporate. The “official version” type information, ie published policies, procedures, news etc which is published from “the company”
2. myTeam. While you may be a member of many teams this sort of content is ment to be user generated/updateable.
3. myStuff. Information published for you by you.
The one problem with Wiki is it isn’t really how lots of people use the web, for that you need more of the social networking stuff and here is a list of open source social networking platforms that could play into the intranet space. Key strength is that its the information you / your collegues believe is important and may include information from outside the corporation.
Have a look at this article from 2007. http://mashable.com/2007/07/25/open-source-social-platforms/
and this comparison on wikipedia. http://en.wikipedia.org/wiki/Comparison_of_social_networking_software
Socialtext Enterprise Wiki
OK, this is another enterprise wiki that has some good positive info like reducing email overload etc. Well worth exploring
What makes an enterprise wiki? — CMS Watch
This is an excellent article explaining enterprise wiki’s. Well worth a read.
Found some interesting direction for collaboration through wikis. A website wikipatterns http://www.wikipatterns.com lists positive people patterns, negative people patterns, positive wiki adoption patterns and negative wiki adoption patterns.
Extremely well written, and it reminded me not to do all the work myself. I am going to create a real collaboration page about the golf game but Im not going to fill everything in, if I did thats an anti-pattern (do-it-all) and I need to avoid that. I still think a project needs a project lead but that may just be IT experience talking and I need to give this alternate approach a chance.
simonsays: 4 Weeks Of Introducing A Wiki Into An Organisation
OK, I’m very interested in how to bring a wiki into a largish organisation and this is a definite good start.
There is another site mentioned in there http://www.wikipatterns.com that I’ll need to check out.
I’ve got to say I’ve become a fan of Atlassian an Australian company that develops and distributes the Confluence enterprise wiki and Jira, the bug and issue tracker.
Atlassian’s products are distributed applications targetted at the enterprise. One of the issues with open source is that large organisations do require support from a vendor and that just isn’t achievable with most open source products. Atlassian has a real advantage here in that while its products are definitely proprietary it makes use of open source components.
The concept of distributed applications built on open source components also aids in the flexibility and ability to reuse Atlassian’s products in other areas.
Atlassian are a company that is doing ebusiness right.
Refs:
Atlassian website.; http://www.atlassian.com
A good article from KMWorld Magazine concerning Wiki’s. Cindy Gordon discusses implementation of Wiki’s at several larger organisations.
http://www.kmworld.com/Articles/ReadArticle.aspx?ArticleID=15802
