Developing the global community I talked about in my previous entry, turns out to be a little more challenge than originally expected. This has nothing to do with the community itself, but with how the developers are working together. Indeed, we are developing this with people from different companies, sitting on both sides of the ocean. So, you would think we just need a little collaboration space and everything would be resolved, isn’t it. Well wrong, first the traditional file sharing tools do not allow to share some types of files (eg. java scripts generated by our PowerPoint to Flash conversion tool), do not allow us to make documents publically available (e.g. Google Docs and PDF documents), and I could go on like this.
As the world becomes global, increasingly companies and people need to collaborate virtually. Unfortunately the tool providers (Google, Microsoft, Yahoo) are looking myopically in silos, addressing collaboration aspects in isolation. What we really need is for a company to take the problem from a different angle, starting by asking itself what is required to collaborate and then develop the integrated environment to just do that. So, let’s think a minute, what do we need to collaborate?
- Well, first we need to share documents either with a know community, with a larger group who’s names and e-mails we do not all have, or be made publically available. These documents may just be looked at, may be downloaded, may be commented upon (with notes or voice) or may be edited by particular members of the community. Obviously we would want to keep track of any activity around the documents.
- Second, we may have to interact, either asynchronously or synchronously, using text, sound or video, or any combination of those. Interactions may be private (between two people) or with a group. During those interactions, documents may have to be referred to and shared. Data may be made available also.
- Third, we may have to work together at a common task, in that process we may share real-time information, documents, and we may use a common application that can be on one of our systems or in the cloud. Here again this can happen between two people or with a larger group.
A number of supporting functions should be available. These include a group calendar (that links with the calendars of the members to identify availability etc.), action item lists, a parking lot, participant information, version control, etc.
Most of what I describe here is available in one form or another on the internet, but there is no consistency, no easy way to cobble it all together, and even if we managed, we would spend our life login on to different systems. Why is nobody looking at the collaboration needs of globally dispersed people and addressing their needs, rather than continuously coming up with incompatible tools.
No comments:
Post a Comment