this may be why some organisations find wikis a bit of a risky proposition

This is a genuine piece of guidance from an intranet in a company with which I've been doing some work. It is entitled - what to do if you want a site on the Intranet - read it and work out why this same company finds the concepts of wikis a bit of a mental leap too far...

• Agree with the Communications Department Ext.xxxx that there is a business requirement for having an intranet site
• Nominate a Web Author who will need to attend the Intranet training course 'Developing Your Intranet Site'. Contact Mrs xxxxx to arrange this course.
• The Webmaster will then create a template site ready for your new site to be designed.
• If a Web Author is already trained in your area then they can begin to create the site.
• Submit a form with your requirements to Communications Department. Who will review your requirements, complete the resource constraints part of the form and pass it to the Head of Communications who will approve the site.
• On completion the sites nominated Data Content Manager will need to check the site editorially and approve the data contained within the site.
• Decide which business process the site will be placed under by contacting Mrs xxxx
  
• On approval the Webmaster will technically check the site. If all is well the new site will then be published

Imagine how this company could flourish with thos contraints removed!!!

Comments

[Euan Semple]

And people wonder why wikis are attractive!!

[Lars Plougmann]

A company I worked with had a process of 50 days duration for getting a new microsite on their intranet. A CMS is their first step in reducing the wait. But access to a wiki could soon mean zero wait.