The Sametime Blog
Marlon Machado 100000PEST email@example.com Tags:  collaboration-agenda industries solutions lotusphere sametime 1,903 Visits
It's 12:26 AM EST in Orlando. Lotusphere is in full swing and I just came back to my room at the Dolphin hotel after attending the Australian Party--allegedly the hottest ticket in town during Lotusphere. I just said good night to my lovely wife and, instead of brushing my teeth and getting ready to go to bed, I'm here writing this post.
The reason I'm doing this is to clarify what Collaboration Agenda means for Sametime. I've been manning the Collaboration Agenda pedestal at the IBM booth and I'm getting lots of questions about what this actually means; questions from business partners, customers and even from IBM colleagues. So, here it goes.
Collaboration Agenda is a philosophy, a way of doing things, a metamethodology that brings together well-known best practices to help customers address pain points with solutions that will save them money and help them make money.
It all starts with industry priorities defined by industry leaders and visionaries. Each industry priority encompasses a series of well-defined pain points that are measurable and quantifiable. Then, based on that knowledge, we apply known best practices to address those pain points with solutions designed to minimize the impact inflicted by those pain points on the customer's business processes and to maximize efficiency and agility. In the case of business processes that benefit from reducing and/or eliminating human latency, such solutions will be based on unified communications and collaboration software.
Devising solutions using the Collaboration Agenda philosophy produces things such as RadioConnect for Sametime, a solution based on Sametime Standard and a soft radio plug-in developed by UnifiedEdge, an IBM Business Partner based out of Round Rock, Texas. RadioConnect was designed with a manic focus on solving a single problem: lack of interoperability among disparate radio infrastructures in emergency response and public safety scenarios and nothing else.
This is what Collaboration Agenda can help us achieve. RadioConnect may not be very sexy--it won't update your Tweeter status or your Facebook wall--but it will help first responders communicate with each other in an emergency situation, which can contribute to minimizing the loss of life and property.
If you happen to be at Lotusphere and would like to have a deeper discussion about this feel free to drop by the IBM booth. I'm going to be back at the Collaboration Agenda pedestal between 11:45 AM EST and 2:00 PM EST today.
I've been reading lots of literature about Communication-Enabled Business Processes, or CEBPs over the last few weeks. Most of it seems to revolve around the notion that CEBPs are nothing but voice-enabled business processes; that all you need to do to enable a business process with communications services is add voice to it. Other ideas around CEBPs call for taking the basic premise of eliminating human latency to the extreme and to actually measure how much a business process can be accelerated through communications enablement in actual minutes. I think both notions fail to present the full dimension of what CEBPs are and why we need them.
I agree that the main purpose of turning a regular business process into a CEBP is to deal with human latency. However, there are business processes in which human intervention is an intrinsic feature and, as a result, expected to be part of the process. I'm talking about processes where human decision-making must be rooted on reflection and careful evaluation of pros and cons, reflection that will invariable manifest itself as latency in the overall business process. I wouldn't mind, for instance, having my doctor taking enough time to evaluate the best treatment options for me or a fund manager taking time to go over a company's books and strategy before investing my money in it. What I would like is for both, my doctor and my broker, to be able to access all the contextual information they need to support the thought process and to have the tools to eliminate latency from their own decision-making process.
I think in these cases the goal behind communication-enabling business processes should be to prevent the process from slowing down as opposed to accelerating it just because faster is better. Doing this requires more than voice, chat and video. It requires a healthy combination of real-time and asynchronous communications and collaboration services to reduce not only human latency where needed but to enhance the context to support decision-making.
I think work styles have a lot to do with the perception that CEBPs are all about voice and reducing human latency. Traditional work styles tend to hover towards extremes: you're either sending email (the most asynchronous way of communication aside from snail mail and fax) or you get on the phone with that person if you can't walk into his or her office. And so, if these are your parameters, that's what you're going to try to optimize. When, on the other hand, you're used to live in a multimodal environment in which chat, voice, a blog post, an entry on a Wiki or a tweet can get you the information you need and when knowing the person who gave you the answer is just there without you having to talk directly to him or her, that's when you realize email and voice alone are way too extreme. Then you learn that just having access to the context in which that person operates can be enough.
Why am I talking about this? Well, this is how we define CEBPs in the Sametime world. We view Sametime as more than just real-time communications--hence the "UC²" thing. We do have the real-time communication capabilities that our competitors have and we also provide the asynchronous and context-based means to provide a better way to do CEBPs through Sametime Advanced and with the help of our sister products and I think we need to talk more about this. I know I should probably write this in a white paper at some point (and I will) but I thought it necessary to rant about it a bit here just to get it off my chest..
See you all in Orlando.