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.
http://nymag.com/news/features/27341/
Excellent article on generational attitudes to social networking and the concept that once information is in the wild on the internet it will always be findable through Google.
Published in NY Mag. Author is Emily Nussbaum.
