This post is by Bruce Cleveland
from Bruce Cleveland's Rolling Thunder
Click here to view on the original site: Original Post
I, along with many of you, have been watching the evolution of enterprise internal collaboration products/companies such as Yammer, Chatter, Jive, and Cubetree over the years.
I was an early investor in Cubetree which was acquired by SuccessFactors and then became part of SAP when SAP acquired SuccessFactors a short time later. SAP has since renamed Cubetree to SAP Jam and it now serves as the backbone to SAPs collaboration strategy.
These products are supposed to mitigate – eliminate ? – the need for email within the enterprise and dramatically improve internal collaboration offering far easier and superior ways to capture and share information v. email/spreadsheets, etc.
However, if you can get the product managers and/or CEOs of these product/companies to speak candidly off the record, with rare exception, the adoption level of these products has been far less than the creators and the companies that purchased these solutions had hoped for.
Why? I have a simple thesis. Collaboration within the enterprise usually takes place among people who share a common goal/objective. And, more typically, the collaboration revolves around a project or a process that people need to execute. The problem with current collaboration solutions is that they are not tightly integrated into the fabric of the applications that functional teams use to perform the processes they need to execute to get their work done.
If I am part of a marketing team in a B2C company, I want and need to be able to collaborate with my outside ad agencies, legal department, graphic designers, product managers, account teams when I create a new ad for one of my product lines. I want an application that actually “embeds” collaboration into the process with workflow, role-based authentication; not a separate collaboration product that sits outside the application and operates orthogonal to the process.
If I am trying to generate a forecast, I want to be able to collaborate with my team members – my sales engineer, the product team, legal team – regarding product availability, pricing, terms, etc. I don’t want a separate collaboration product that forces me to remember to communicate with my team members outside the forecasting application.
If I am part of an engineering team and I want to discuss whether or not a certain feature should be linked into the next build process, I should be able to collaborate with product management, sales, legal, etc. within the development applications I am using, not be forced to use a separate application outside the application.
The minute I am required to communicate/collaborate outside the process application, email becomes a much easier mechanism and something I am far more comfortable using. It has the added benefit of working both internally and externally to the enterprise. And, that
Continue reading “Fusing Collaboration Into Enterprise Applications – Enabling the “Real” Social Enterprise”