Last year I posted an article on how CenterStage was the Latest ex-Collaboration Tool from EMC. Turns out I understated the case. EMC isn’t going to be building a collaboration tool, at least not one purposely built to encourage collaboration.
In many ways the announcements at this year’s EMC World just reaffirmed the direction set last year. Last year I was sad. This year, I’m starting to lose my sense of humor.
CenterStage, The Awkward Middle Child
At this point, I’m thinking that CenterStage should just go kill itself. It should just trigger an endless loop that can only be avoided by not logging into the interface.
Three years ago, CenterStage (then Magellan) was hailed as the next big thing. Then it languished in grade school, falling back a year or two, and now everyone is pointing to the Unified Client coming in D7. CenterStage used to be the basis for the mobile client, 2 years ago, and now it can’t even rustle up a calendar to match eRoom or SharePoint.
Quick sidebar about the calendar, HOW HARD IS IT? I mean, come on people! Clients tell me that they would move to CenterStage, even the not ideal 1.1 version, if they only had a way to have a central calendar. Try this:
- Take the existing data table construct introduced two versions ago
- Define a custom data table type (look at SharePoint or eRoom for field advice)
- Add an abstraction layer (object-oriented languages might have a simple way to do this)
- Steal graphical look from almost any major collaboration system (eRoom, SharePoint, Jive…)
- Test and publish
I’d write the thing myself if there wasn’t all of these plans to move to a new UI and backend with D7. Where does CenterStage fit into all of that? That was a question I never got answered. Why? Everyone gave me a different answer so now I have none. The best answer I got is that EMC is trying to make sure that nobody can customize CenterStage in such a way that it inhibits their move to the common UI which will have a more structured customization structure (think WDK).
By the way, Webtop has a future in D7. Heard that definitively stated multiple times.
This is all a little harsh considering how good a year CenterStage has had. Two point releases. The lastest, CenterStage 1.2, is supposed to be scalable and be able to access the entire repository. As I haven’t talked to anyone that can independently verify, I’ll leave it at that.
Do you know what summed-up CenterStage’s future? I heard Webtop mentioned as part of presentations 3-5 times more often than CenterStage. If that doesn’t mean anything, nothing does.
The Trinity of Collaboration
During Rick Devenuti’s keynote, the future of collaboration was clearly outlined. EMC will offer to solve the problem in one of the following three ways:
- SharePoint: Need to collaborate in the department and beyond? SharePoint is your tool. In fact, you are likely already using it. It is a way of life in the corporate world and EMC is focusing on making SharePoint work better. After all, if SharePoint doesn’t work well, someone may choose a solution for which EMC isn’t needed to provide the backbone.
- Box: In the surprise of the show, EMC announced a strategic alliance with Box. This is aimed at those that need to collaborate beyond the enterprise and do it on the move. Four months ago, this partnership was unfathomable. While independent of Whitney (Tidmarsh) Bouck’s move, that change likely strengthened/accelerated the alliance. While integrating using the previously announce EntropySoft-based ECM Cloud Connect offering, tighter integration is planned. Lee Dallas talks about this as acceptance of Employee Managed Content within the EMC mindset.
- Cisco Quad: The Quad product is a more traditional social, real-time collaboration platform. This addresses the more Virtual War-Room type of collaboration that can be very useful. Jeetu has posted a “conversation” with Cisco talking about how the two offerings strengthen each other.
No matter what you think of the strength of the products, this shows EMC outsourcing collaboration. In fact, the less you think of the offerings above, the stronger the capitulation EMC is making.
Why outsource collaboration? Simple, as Jeetu stated in his keynote, EMC cannot out-innovate silicon valley as a whole. This is an honest, and accurate, understanding of reality.
Of course that is why you buy companies that fill a gap. You take both their existing innovations and the innovators. From there, you try and nurture the products into something bigger.
Not that it always works that way.
Parts of me are sad, upset, angry, and a whole assortment of increasingly bitter emotions. I love eRoom and collaboration. Watching this happen just drives me nuts.
I wish they would just open-source the eRoom code so it could evolve again and not just limp along in a perpetually supported state. It’s like a zombie of your kid or spouse. You just know that given time a cure will be found and you can’t bring yourself to kill them off.
This emotion makes it really hard for me to step back and evaluate these decisions. No matter how you slice it, Documentum isn’t targeting collaboration. They might say they are with CenterStage, but any collaboration achieved is a side-effect of sharing content. It is the same level of collaboration offered in the 90s by most of the document management players.
Oh, the execs still say they do collaboration, until you confront them. You point out that all the new and planned features for CenterStage are Content Management features, not collaboration features. They hang their hat on the data table in v1.1. Eventually, they agree that CenterStage, and other clients, help people collaboration, but that the colaboration is a side-effect of the core purpose of the interfaces which is to allow better management of content.
Now maybe they were just trying to get me to go away, but they had to know I would share. To be honest, it is okay. EMC can’t be all things. They want to focus on what they feel they do best, Content Management, Governance, and Business Process Management.
That is fine. It is probably the right move given the heavy investment needed elsewhere (e.g. xCP 2.0, Next Gen Information Server). That won’t stop me from mourning a little bit.
Or a lot.