This link has been bookmarked by 7 people . It was first bookmarked on 01 Nov 2009, by someone privately.
-
12 Oct 11
-
11 May 11
-
02 Sep 10
-
05 Nov 09
-
While retaining secondary support for documents, 80 per cent 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.
-
“There are fundamental differences between working styles that are file-oriented and document-based and those that are Web 2.0 and browser-based,” said Jeff Mann, research vice president at Gartner. “Understanding and accommodating these differences will be important factors in determining the success of collaboration platform introductions.”
-
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.
-
“Users who have spent years primarily working with PC-based office automation suites such as Microsoft Office, tend to favour the file orientation and can find it unnerving to work in a Web 2.0 environment where people can be editing the same page at the same time,” Mr Mann said. “Similarly, users accustomed to free-flowing wikis and blogs can stumble over the process and the more-structured requirements when using document repositories. It is this mismatch between expectations and working styles that lies at the heart of many projects facing issues with user adoption.”
-
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.
-
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.
-
- 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.
- Recognise 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.
Gartner has the following best practice recommendations for managing the transition between the two working styles:
-
-
27 Oct 09
Nick GallWOA Baby! RT @ianrbruce: @Gartner_inc:80% of Ent Collab Platforms Will Primarily Be Based on Web 2.0 Techniques by 2013
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.