Comments on: Enterprise2.0 – InformationWeek survey http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/ Nic Brisbourne's view from London on venture capital and exploiting change in technology and media Sat, 11 Feb 2012 20:08:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Euan http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-765 Euan Tue, 06 Mar 2007 18:22:07 +0000 http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-765 And of course there is no connection between the widespread use of Sharepoint and the lack of takeup! To be honest the biggest thing lacking at the moment is patience. And of course there is no connection between the widespread use of Sharepoint and the lack of takeup!

To be honest the biggest thing lacking at the moment is patience.

]]> By: Euan http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-10667 Euan Tue, 06 Mar 2007 18:22:00 +0000 http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-10667 And of course there is no connection between the widespread use of Sharepoint and the lack of takeup! To be honest the biggest thing lacking at the moment is patience. And of course there is no connection between the widespread use of Sharepoint and the lack of takeup!

To be honest the biggest thing lacking at the moment is patience.

]]> By: Simon http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-764 Simon Tue, 06 Mar 2007 17:57:26 +0000 http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-764 For Wiki's I see the power for a lot of corporates is in technical guides, training guides etc. where it is useful to be able to access anywhere, anytime without needing to open Word. Most of these manuals don't need to have hundreds of authors but do need constant updating, improvement and release. This is where I definitely see Wiki's having strength. A core nucleus of authors is responsible for maintain the documents with others able to comment on the documents (errors, questions for clarity better examples). Similar in many ways to the MySQL Technical Guides. For Wiki’s I see the power for a lot of corporates is in technical guides, training guides etc. where it is useful to be able to access anywhere, anytime without needing to open Word.

Most of these manuals don’t need to have hundreds of authors but do need constant updating, improvement and release. This is where I definitely see Wiki’s having strength. A core nucleus of authors is responsible for maintain the documents with others able to comment on the documents (errors, questions for clarity better examples). Similar in many ways to the MySQL Technical Guides.

]]> By: Simon Cast http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-10666 Simon Cast Tue, 06 Mar 2007 17:57:00 +0000 http://www.theequitykicker.com/2007/03/06/enterprise20-informationweek-survey/#comment-10666 For Wiki's I see the power for a lot of corporates is in technical guides, training guides etc. where it is useful to be able to access anywhere, anytime without needing to open Word. Most of these manuals don't need to have hundreds of authors but do need constant updating, improvement and release. This is where I definitely see Wiki's having strength. A core nucleus of authors is responsible for maintain the documents with others able to comment on the documents (errors, questions for clarity better examples). Similar in many ways to the MySQL Technical Guides. For Wiki’s I see the power for a lot of corporates is in technical guides, training guides etc. where it is useful to be able to access anywhere, anytime without needing to open Word.

Most of these manuals don’t need to have hundreds of authors but do need constant updating, improvement and release. This is where I definitely see Wiki’s having strength. A core nucleus of authors is responsible for maintain the documents with others able to comment on the documents (errors, questions for clarity better examples). Similar in many ways to the MySQL Technical Guides.

]]>