Matthew Clapp schrijft There are two major goals of any collaboration initiative: 1. Enable your employees around the world to easily collaborate; and 2. Be able to share that output with the rest of the organization. In my opinion, this order is significant. The goals of collaboration should first be to allow knowledge workers to labor together to complete projects and only then to collect that knowledge to be leveraged for the rest of the enterprise. Too many collaboration technology implementations are led by a knowledge management team that may have reversed the order of those two priorities. This can contribute to an over-engineered, failed project because the process for contributing and classifying content is so cumbersome that workers bypass the million dollar solution for another, simpler one that works.Pilot First
The market is full of vendors eager to peddle their latest quick-fix collaboration solution (more about some of the larger ones below). Alhough some IT organizations are more than eager to throw a few hundred thousand dollars at the problem and hope that it goes away, I wouldn’t recommend this approach.
Before you go and blow your entire budget on a solution that has the same likelihood of success as a manned mission to Mars in the same timeframe, consider piloting an open source solution with a small group that is in dire need and eager to get started. This will allow you time to build your business case, learn some hard lessons about usability, and also make essential improvements to business processes in anticipation of other groups. You will also quickly discover the sources of any network connectivity problems and have an opportunity to solve other persnickety (but potentially prohibitive) technical problems before rolling out a full-blown solution globally.
» lees verder [Bron: CMS Watch]N.B. Getipt door Column Two