Contextual Collaboration is More Than Integrated Presence & IM
I'm disappointed with the implementation of "contextual collaboration" by some vendors. That term should represent the pinnacle of integration of collaborative capabilities into business applications of all sorts, not merely the existence of a presence-enabled buddy list and a set of right-click contact options. At an IBM Lotus briefing yesterday, a slide showing a transition from "Collaboration" to "Advanced Collaboration" and finally "Contextual Collaboration" was displayed ... although the only detail provided for contextual collaboration was "the integration of Sametime into a portal interface". When I questioned the presenter (who did a great job of presenting given that me-the-skeptical-analyst was in the room), he agreed that there was more to contextual collaboration that what he discussed ... I stressed that he/they/IBM need to push the boundaries on what that could mean.
From my perspective, one of the sterling examples of contextual collaboration is the work done by DETERMINE Software with Kubi Software to integrate a standard business application (for contract negotiation) with the Kubi client for Outlook (yes, no Notes compatibility ... which is bad for the overall Kubi value proposition, but it was DETERMINE who decided to implement as such). In essence, as a user is working through the contract process using DETERMINE, there comes a point when a greater set of collaborative capabilities are required ... and so DETERMINE creates a Kubi space for the individual participants, and invites them to it. The (hard) work around coming to points of agreement with other members of the contract negotiation are undertaken within the Kubi client, and on completion of that stage, the resulting discussion threads, contact records, and documents are embedded back into the DETERMINE process. Users have been able to collaborate in the context of the business process.
Another example for further investigation and elaboration is the points at which collaborative capabilities -- presence, discussion lists, real-time application sharing, etc -- can/should be integrated into enterprise resource planning systems. This means that all negotiations and discussions about an element of the overall plan are available to all future users of the system, not locked away in some 'out-of-band' (eg, email) system.
The team at Groove have done some good thinking about this, too, although I'm a bit out-of-touch with where and how they are doing such integration going forward. One of the Groove VP's presented at a conference I moderated, and shared some initial ideas.
Yes, integrating buddy lists into other applications is an initial step of contextual collaboration, but please don't make it the be-all-and-end-all.
Request: Does your organization have a coherent ... or even emergent ... strategy/vision for "contextual collaboration"? If yes, I'd love to hear from you, either via the Comments system below, or privately to contextual.collaboration@shared-spaces.com.