Opinionated comments on mobile phone industry news
|
All entries are written by Anders Borg, CEO and Consultant of Abiro, that has a long experience in strategic planning, developing embedded and Java software, usability aspects, and the mobile phone industry in general. You can also read the latest Mobile News entries on your phone via wap.abiro.com, and we provide many News Feeds from popular news services. For advertising and contribution queries, please use the feedback form. News feed (local) FeedBurner Feed
|
|
Tuesday, August 14, 2007
Web 2.0 in the enterprise
'IT Execs Seek New Ways to Justify Web 2.0' mentions especially wiki as a useful tool for internal information exchange at enterprises, and I'm sure it is.
While I worked for Axis Communications I single-handedly maintained an intranet directory of all technical information we needed for developing our products. Some info was local, but oftentimes all that was needed was a link to the appropriate Web sites. At the time I didn't use any wiki server, all pages were manually edited so I was the only publisher, but the "read only" user experience was pretty much the same.
The key for this to be a success is that there's someone that bothers maintaining the information database. If everyone just posts information, the information and the value thereof deteriorate pretty quickly.
The note mentions costs for setting up a wiki. Of course the cost is not in the wiki server itself, but in the maintenance of the information contained in it.
Also it says it's tricky for IT execs to convince management about setting this up. More often it's the other way around: Management has the vision, while IT execs stalls. Also, setting up a wiki can be done for one specific department for no initial cost, and decided by the department manager.
Just so you all know, wiki is a very old technology, Internet-wise. The first wiki was published already 1994.
I have to admit I don't like the wiki syntax, that makes very little sense and seems to have been defined during a meth binge.
While I worked for Axis Communications I single-handedly maintained an intranet directory of all technical information we needed for developing our products. Some info was local, but oftentimes all that was needed was a link to the appropriate Web sites. At the time I didn't use any wiki server, all pages were manually edited so I was the only publisher, but the "read only" user experience was pretty much the same.
The key for this to be a success is that there's someone that bothers maintaining the information database. If everyone just posts information, the information and the value thereof deteriorate pretty quickly.
The note mentions costs for setting up a wiki. Of course the cost is not in the wiki server itself, but in the maintenance of the information contained in it.
Also it says it's tricky for IT execs to convince management about setting this up. More often it's the other way around: Management has the vision, while IT execs stalls. Also, setting up a wiki can be done for one specific department for no initial cost, and decided by the department manager.
Just so you all know, wiki is a very old technology, Internet-wise. The first wiki was published already 1994.
I have to admit I don't like the wiki syntax, that makes very little sense and seems to have been defined during a meth binge.
