Gartner Says 80% of Enterprise Collaboration Platforms Will Primarily Be Based on Web 2.0 Techniques by 2013

While retaining secondary support for documents, 80% of enterprise collaboration platforms will primarily be based on browser-based Web 2.0 techniques by 2013, according to Gartner, Inc. As wiki-like collaboration techniques mature and gain more acceptance, Web 2.0 approaches will become increasingly influential.

Gartner expects that managing users’ transition from a file-orientation to Web 2.0 approach will be a major challenge for organizations.

Typically users fall into two camps: those who prefer to collaborate around files and documents, and those who prefer to interact with content and other people directly on Web sites. The differences between these two working styles goes much deeper than mere user preference or alternative ways of getting things done as the "mind-set" of working with files affects how people work, attitudes toward security and the impact of governance.

While document-oriented platforms are well established, familiar and more productive for some tasks, the trend is clearly toward more Web 2.0-type tools. However, Gartner maintained that Web 2.0 will not take over completely because there are situations where working with documents is more appropriate than the wiki style. Tasks that require sequential approval workflows or where the final product will be a file are often easier to get done in a document repository with check-in/out facilities than in a free-form wiki.

Furthermore, some collaboration products show a hybrid of Web 2.0 and file orientation, while several browser-based office automation products allow working with files. For example, Google Apps, Adobe buzzword and Zoho are firmly in the Web 2.0 camp, but also work with files, either by downloading versions to work with offline or by organizing content online using file-like user interface metaphors.

Gartner has the following best practice recommendations for managing the transition between the two working styles:

* Don’t force the issue, if users prefer a particular model, tread carefully when introducing a new one.

* Explain the business reasons for the choices made. If necessary, consider offering alternatives for particular situations where the lack of user acceptance will endanger the success of the project.

* Recognize what each model is good for and adopt accordingly.

* Don’t blindly assume that one or the other will fit every situation.

* Examine the hybrid models some products support.

* Most products are not wholly file-oriented or entirely Web 2.0. Make sure that users know about the features they will find attractive or useful.

More information on the service and support industry can be found at www.supportindustry.com