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 is precisely why email remains the primary communication vehicle for collaboration.
I believe there is an opportunity to completely revamp all enterprise applications. SaaS was a good first step making enterprise applications far easier to implement, manage and use. The next step is to modify all enterprise applications such that collaboration is built into the fabric of their architecture. All enterprise applications – that are focused on solving a business process – should have 5 primary elements:
- Content – the ability to create/capture, review, approve and share relevant content
- Tools/Workspace – enable the user to perform relevant work on the content
- Workflow — technology that enables everyone to see the status of work that has been assigned and being performed
- Scheduling – assign tasks, owners, deliverables, due dates to content/work being performed
- Collaboration- the ability for teams – both internal and external – to review, discuss, approve and share content
There are other elements but these, I believe, are 5 that are common to every enterprise process and therefore every enterprise process application should support at least these 5 elements.
The missing element from nearly all legacy enterprise applications is Collaboration. As a result, there is an opportunity for new enterprise applications to emerge that fuse collaboration into their architecture.
A really good example of what I am referring to is what Opal Labs has done. They have built an enterprise application targeting B2C marketers that enables them to create new ad content, work with agencies, get legal sign-off, etc. all from within the application. They have thought about the entire end-end process that a B2C marketer needs to go through to create an ad campaign and their application handles the entire process — including collaboration internally and externally.
There is no need to resort to email or other external applications to get the job done. Take a look at the construction of Opal’s UI. This, I believe, is the framework for enterprise applications of the future and Collaboration 2.0.
Collaboration isn’t a separate product, it should be embedded into the fabric of everything we do. This is the real future of “the social enterprise”. If I were SAP, Jive, Salesforce, etc. I would stop trying to sell their collaboration solutions separately and start trying to OEM them to the creators of enterprise application software with flexible APIs and pricing models that support an OEM distribution strategy.