You are currently browsing the tag archive for the 'collaboration' tag.
What is co-browsing?
Co-browsing lets multiple users work together in their respective browsers through what look like shared screens and communicate via telepresence including video and audio. The impact of this technology is enormous as companies become more virtual and the need for serious collaboration increases to be competitive in tough times. To be able to share, interact and see the body language of your collaborator in real-time without extraordinary downloads to your PC or expensive third party solutions could simply change the way we work. This innovation comes from not Google, or Yahoo but from IBM in a proof of concept project called Blue Spruce, a Web browser application platform that IBM is working on to allow simultaneous multiuser interactions enabled by AJAX and other standard technologies through the Web browser.

The Blue Spruce project is IBM’s solution to the classic one-window, one-user limitation of current Web browsers. The application is a mash-up that combines Web conferencing with voice and video and other data forms to let people share content including existing Web widgets – at the same time. Two different users, possibly anywhere, are able to move their respective mouse pointers around the screen in the browser to click and make changes on the shared application, with the platform enabling concurrent interactions through the browser without disruptions. Despite the appearance, the co-browsers aren’t actually sharing content. Both collaborators obtained a Web page through the Blue Spruce client, but the “events” enabled by the mouse are what is being sent to the Blue Spruce Co-Web Server. The idea is that no matter where the two users are in the Internet world, they pick up the general data caches on both personal computers and react to the events.
The applications for co-browsing collaboration are numerous, especially for knowledge workers. In healthcare, IBM has used Blue Spruce to create an online “radiology theatre” product, currently at the prototype stage, which allows teams of medical experts to “simultaneously discuss and review patients’ medical test data using a Web browser.” The project is being run in collaboration with the Brigham and Women’s Hospital of Boston. According to IBM, it has created a secure Web site that allows select medical experts at Brigham and Women’s Hospital to access and collaborate on data such as CT scans, MRIs, EKGs and other medical tests. Each medical expert can “talk and be seen through live streaming audio/video through their standard web connection, and have the ability to whiteboard over the Web page as well as input information to the patient’s record.” Basically it is a secure multimedia experience running inside a single browser window, using Blue Spruce as the platform.
It is important to note that Blue Spruce is not your typical “fat client” or downloaded application, but it is a fully browser-based application development platform, currently in development, which is being built on open Web standards. The main feature of Blue Spruce is that it allows for a combination of different Web components – data mashups, high-definition video, audio and graphics – to run simultaneously on the same browser page. It’s important to note that the Radiology Theatre app only requires a standard Web browser – so there’s nothing to download for the end user, in this case, doctors.
This is how IBM described how the new online radiology theatre will work:
”A group of doctors can log into a secure Web site at the same time to review and analyze a patient’s recent battery of tests. For instance, a radiologist could use her mouse to circle an area on the CT scan of a lung that needs a closer look. Then using the mouse she could zoom into that scan to enlarge the view for all to see. An expert on lung cancer could use his mouse to show how the spot had changed from the last scan. And then, a pathologist could talk about patient treatments based on spots of that size depending on age and prior health history, paging through clinical data accessible on the site.”
“The theatre allows all these experts to discuss, tag and share information simultaneously, rather than paging through stacks of papers, calling physicians to discuss scan results and then charting the results. This collaborative consultation brings together the personal data, the experts and the clinical data in one physical, visual theatre.”
The impact on rural medicine and the need for telemedicine for key healthcare experts is significantly advanced with this technology.
Perhaps the biggest potential benefit of the online radiology theatre is that it will enable experts from all over the world to consult on cases. The ability for multiple users to “co-browse” means they can interact in the browser in real-time and see each other’s changes. Of course, since this is medical data, there are significant privacy implications involved in using the Internet to collaborate. The time and cost savings from collaboration is important, but better and faster decision making is the key.
The need for inexpensive and minimally invasive techniques for real collaboration over the Internet is real and the backlog of potential applications is fun to consider. Imagine reviewing your health care or insurance claims with a live person (and their reactions) at the insurance company to reduce cycle time, or collaborating on new product engineering drawings from the U.S. with your Chinese manufacturer. Imagine the potential for teaching or training with key experts and a worldwide audience using a live whiteboard. Finally, imagine not paying big monthly fees for basic meeting collaboration needs on a daily basis. Blue Spruce is really a technology to keep an eye on.
One of the strongest and most misguided arguments expressed online and in many companies we speak with about Enterprise 2.0 is that it is not strategic.
That this collection of tools, technologies and ideas is not yet mature enough, lacks proven ROI, introduces a myriad of security and governance issues and even if successful is not a priority in today’s soft economy. It is too often delegated to IT managers to experiment with and report back in a few years.
Here’s where the difference is: Enterprise 2.0 is not a technology. It represents first and foremost a new way of thinking, interacting and communicating that includes attitude and cultural changes, empowered by IT. Is there anything more strategic than that and more important to a business future success?
It is arguably the biggest opportunity for IT driven cultural change facing organizations since the introduction of PC networks more than 2 decades ago.
One of the C suite most important tasks is to shape an organizational culture that will make their company innovative, competitive, efficient and successful not just now but in the future. Embracing Enterprise 2.0 now and guiding their employees through this transitional period should be one of their top priorities.
While in a few cases adoption started from the bottom up, a change of this magnitude usually needs to come from the top accompanied by the matching set of values and actions that prove the seriousness and commitment to change.
It requires leadership that is able to see that transparency and increased visibility into activities throughout the company will finally enable them to know what is really happening and will create a culture of trust. That openness and exchange of ideas will lead to innovation and efficiency. That collaboration will enable a diverse workforce to work together in emergent ways while being physically and geographically dispersed.
In short, it requires vision that will set a future path and will ask managers to overcome the obstacles in the way. The type of vision CEO’s need to provide and not delegate to IT managers.
The challenge and opportunity is that not many chief executives have realized yet that embracing Enterprise 2.0 is a strategic imperative and are focusing the discussion around short term ROI.
Dion Hinchcliffe at ZDNET provides a comprehensive review of the evidence and opinions regarding ROI and adoption challenges, and adds his own interesting model of collaboration cause and effect chains that while clearly provide benefits, make them harder to pinpoint and measure.

He also concludes that
“… an accumulating body of knowledge is pointing to potentially dramatic business returns with Enterprise 2.0. If these continue to be borne out, it will affect the competitive and financial positions of the companies that are proactive and therefore their long-term marketplace success“
And wonders what it will take to break the current status quo?
His colleague Dennis Howlett on the other end thinks the ROI is still years off and concludes
“As always, the secret to long term success depends on management’s ability to maintain a sustained commitment and all that goes with it. The difficulty today is that same management is wondering where the next sale comes from or how cash will be generated.”
The good news is that Enterprise 2.0 does not require large capital expenditures but mostly thorough organizational commitment. There has rarely been an opportunity for businesses to gain so much competitive edge by investing so little.
As in many cultural revolutions, by the time Enterprise 2.0 related changes start translating into business differentiators, organizations that have not made the transition will look as outdated as an organization resisting getting these useless PC boxes or adopting email.
When looking at the results of our last poll on collaboration styles, several things jumped out at us.
1. Nearly a third of the respondents are either still relying on email collaboration or under-utilizing basic portal functionality (document checkout/checkin for version control).
2. Among users of collaboration portals, there was an even split between Sharepoint and other tools.
This led us to wonder how broad corporate adoption of collaboration tools might be. And it leads us, of course, to another poll.
Comments always welcome, and in case you missed the first post in this series, it’s still open and you can vote here.
Clearly, many companies have collaboration tools such as portals on their to-do list as one of the top technology trends of 2009. Even this early in the year, we’re already hearing some frustration with the earlier adopters, in terms of the difficulties in getting their organizations to actually embrace the powerful functionality of collaboration portals.
Here are four key elements to fostering user adoption of collaboration tools. They need to be baked into your portal implementation plan, because you need to sell this change aggressively into your organization to realize the full ROI of the technology investment. Sometimes, this can be the part of the implementation that requires the most finesse.
1. Strong executive sponsorship. Portals can fail when they are perceived as an IT initiative. Someone at the top has to get the early message out about how the portal can make the whole business more efficient. Executives can then lead the way by making the portal the preferred place to interact with the executive team.
2. Data Migration plan. If your business has traditionally used shared drives for file-level collaboration, make sure your portal migration plan includes moving the latest versions of files over to the portal site and decommissioning the old shared drive.
3. Refine your collaboration processes to fully exploit the new technology. Workflows that have burdensome review/approval cycles can bog down any attempt at collaboration. While such rigor is useful in highly regulated businesses, it’s overkill in many others. If you make the portal a place where people can quickly share lessons learned and the new tools they develop for doing their jobs more efficiently, they will rush to embrace the portal. Limit approval requirements to the bare minimum and don’t let their contributions languish an an approval queue.
4. Change management. More than just training in portal functionality is needed. Key elements of your portal change management plan include organization design (assigning clear responsibility administration and creation/maintenance of portal sites), getting the message out early and often about the benefits of portal functionality, training in key user procedures (checkin/checkout, alerts, discussion boards, etc), and handholding as the business units create their own working sites.
If you’ve implemented a collaboration portal and are finding that your enterprise is ignoring it or under-utilizing its capabilities, please leave a comment–we’d love to hear about the challenges and how you’ve overcome them.
Fast away the old year passes. It’s time for New Year’s Resolutions. Even if you’re not a resolution-making sort of person, the additional challenges the economy imposes on the coming year make it absolutely essential to think through some changes in approach.
Budgets will be tighter, and in the grand tradition of good things that roll downhill, the people who will most feel the squeeze are the people in charge where the rubber meets the road, the project managers. You will be challenged to do more with less, to face multiple changes in strategy and scope, and to achieve success on tighter timelines.
Here are some suggestions for thinking outside the box in 2009:
Manage your team, not your project plan. Your project plan file is merely a tool for planning and tracking. The key to success is your daily leadership of your team. Meet frequently with each contributor to your plan to understand where their difficulties are and to suggest tactics for moving past bottlenecks. This is much more valuable to the project than reporting that task 345 is only 45% complete as of the end of the week. This leads to the next resolution, which is:
Embrace collaboration tools aggressively.New times and new challenges call for new tools. Use project portals to the fullest. Get beyond Level 1 portal usage (shared documents) and fully exploit the discussion and alerts features. Build status dashboards for your executive sponsors, so that status communication becomes more than a once a week meeting or conference call. With widely dispersed teams becoming more the norm than the exception, twitter-like tools can help project managers to keep tabs on the current activities of all team members, and foster real-time assistance when team members tweet about a newly encountered difficulty.
Slim down that project plan! You just knew there had to be a diet resolution in here somewhere… Your plan needs only enough detail to quantify effort, predict duration, and define a critical path. More detail beyond that means more overhead in terms of status tracking and replanning, and if this is not in the project budget, it’s only going to come out of your personal time.
Build contingency plans into your approach from Day 1. All that stuff about completing projects on time and within budget as the measures of project success is very pie-in-the-sky. There will be changes in scope. There may be changes in budget before you get to the build phase. The key milestone date may well be pushed up while you are still in the analysis phase. Have a clear idea of what’s essential for launch and what can be deferred from Day 1 and you will be in better shape to roll with the changes.
Align effort with risk. Don’t spend 80% of the analysis effort on 20% of the business functional domain, unless that 20% is the most mission critical, the most regulated, or the most central to driving revenue. As the project manager, you must rein in project team members who are focusing on areas that are not really central to the success of the effort. In this new tighter budget, compressed timeline world, there are going to be some bumps in the road. You need to make sure that mission critical requirements are safeguarded at the expense of those business requirements that are less crucial from a bottom line perspective.
…Is that it arrives before we are ready for it.” A bit of plainspoken wisdom from American humorist Arnold H. Glasow. Thanks to the miracle of google, it becomes our intro quote for today’s topic of acquisition integration readiness.
In an earlier post, we talked about data integration readiness, but that’s only one task on a list of things you should be doing now if you plan to acquire a company in 09. Readiness is the word of the day, and the best way to sum it up is you have to have a documented platform to integrate with across the board, or you will lose time during your integration period. Lost time means revenue drag–you won’t hit your projections.
So, let’s make a list.
1. Data integration readiness, already covered in detail here.
2. Process readiness – are your procedures for key business areas up to date? You will need to walk through them with business team leads on the acquisition side to rapidly understand the gaps between the way they do business and the way you do business. Can you rapidly train the influx of people you will be onboarding with the acquisition? An effective training plan is a solid way to minimize post-close chaos.
3. Collaboration readiness – don’t underestimate the amount of time those new employees will take up with endless “How do I?” questions. Hopefully, you have a corporate knowledge portal in place already and you can give them access and a navigation walkthrough on Day 1. Make sure it includes discussion groups, so that the answers to their common questions can be searchable and institutionalized. There was a great post on this recently describing how IBM is using collaboration tools to help with acquisitions, and Edgewater’s Ori Fishler and Peter Mularien have posted extensively on Web 2.0 tools for corporate collaboration.
While we are on the subject of collaboration tools, let me tip you off to an important secondary benefit. The people that use them and participate actively in discussions are your change agents, the people that can help lead the rest of the acquired workforce through the integration. The people that don’t participate, well, they are your change resistors. They need to be watched, because they may have emotionally detached from this whole acquisition thing. If they are key employees, you want to make sure they don’t have one foot out the door.
4. System integration readiness – It’s oh-so-much-more-challenging (meaning time consuming and costly) to integrate into an undocumented or underdocumented architecture. Get your data flow diagrams and infrastructure diagrams, as well as your hardware and software inventories up to date before you close.
That first quarter after you close will still be a wild ride, but you can be sure you’ve cut the stress level down significantly if you make these readiness tasks a priority before closing day.
I wanted to follow-up the IsoTech08 conference and the talk I delivered there on Web 2.0 and Insurance with answers to a few questions that came from the audience.
The full presentation slides are posted on slideshare:
Questions and Answers:
Q: the new trends in the innovative use of the web seem to give direct insurers an advantage over indirect ones, as they focus a much larger portion of their resources in direct to consumer services and marketing. How can traditional agent centric companies compete?
A: Do you remember the end of real estate agents? When Your Home Direct launched with a website and a 2% commission structure everyone mourned agent based companies. It appeared that agents do provide value and the 2% became 3%, then 4% and now chapter 11. Remax is still going strong…
Agents provide a personal relationship and value that is appreciated by many customers. Companies can empower these agents with the latest tools and technologies that will allow them to provide their customers with the best user experience and convenience that will provide the best of both worlds.
The direct providers like Geico, provide tools but no context or tailoring to the client specific needs. Agents should be provided with a white label set of tools (tools that the Insurer provides but can be customized with the branding, contacts and products that a specific agent provides). When providing a quote, it is not a printed document but a link to a personalized client site with all the details of the quote listed and the ability for the client to make changes and see options. Agents can communicate through messages or live chat and provide all the options and discounts.
The Customer gets a completely customized experience guided by a trusted agent.
Insurers that will empower their agents with tools like these will not have a problem to compete successfully.
Q: It was mentioned that one of the largest hurdles in the successful implementation of social and collaboration tools inside the enterprise is lack of critical mass of users. How can we ensure that we reach the critical mass and what will drive adoption?
A: It is true that for any community to be lively and for any communication tool to be effective it needs to reach a sufficient number of people. There are few ways to help that happen:
- Cultivate the core user group. The ratio is usually 1:9. For every one contributor you have 10 readers and commenters. The contributors form the heart of the community and need to be encouraged and rewarded
- Put collaboration tasks within the line of business. Collaboration and social tools are often considered “above the line” or things you do above and beyond your regular work. If an organization can find ways to put the use of these tools in the regular course of doing business, their usage will become just part of doing your job. Examples can include posting files and not emailing them, soliciting feedback through a forum, not in an email etc.
- Make it the social norm. if key activities happen there, and key executive post and conduct business in the internal social network, it will become the place to be. People will start asking each other if they saw a specific thread or comments and will drive up adoption.
Q: Can you provide an example where Mashups provide a solution that can not be addressed using other existing Portal, BI ,EAI and Dashboard tools?
A: As with any new technology, people are justifiably concerned that the hype is exaggerated and that it is just a fancy term for well implemented dashboards. The new class of tools called Mashup engines try to solve some of the fundamental problems of integrating data from multiple sources and providing it in a visual interface without the need to go though the extensive and expensive effort of actually integrating the applications and their data. By leveraging web services standards, each source of data or data driven service can be assembled quickly and provide unique insights and different way to look at data that was very difficult until now. Here are a few scenarios:
-
Dynamic view of the customer. We often talk about a 360 view of the customer with all their claims, policies, history, and in multiple lines of business. A customer mashup can take a customer record as a baseline and pull together a combination of structured and unstructured data with visual rendering. For example, if the client is company X, the company view can include:
- Company information and price stock
- Map of company locations
- List of latest news from news services about the company
- List of SEC filings
- Existing policies with their value and renewal dates
- List of open and recent claims
- List of recent service calls
The data comes from multiple sources and can quickly change but the dynamic nature of the mashup, allows sources to be added or removed quickly and for different data to load based on retrieved parameters
Image taken from: http://www.andybudd.com/presentations/dcontruct05/images/zen2.jpg on April 21, 2008.




