Alfresco's Social Computing Slant Shows ECM's Evolution

I had an interesting discussion with John Newton, the co-founder of Alfresco, recently. I'm a little star-struck by this guy. It's hard to get much higher on the food chain when you look at Newton's credentials. Not only did he co-found Documentum, he's also less than five years into the launch of Alfresco, arguably one of the biggest disrupters to appear on the enterprise software radar in years.

We've covered Alfresco before, and each time I come away thinking I'd like to classify them as something other than an open source ECM company. It's hard to explain. Maybe it's because Newton makes everything sound so damn easy when he talks about enterprise content management. And when's the last time you heard the words "easy" and "ECM" in the same sentence? But, back to their classification for a moment.

Newton and company have the usual check-boxes for ECM, but have managed to separate themselves from ECM's shadowed legacy of big, unwieldy repositories and tough implementations. Perhaps it's because of its mashup-centric approach to looking at content or how it describes knowledge worker applications of the future. Whatever the case, I want to put them somewhere in the middle of Web platform providers and collaboration vendors. The point is, you need to have both those qualities if you intend to peg yourself as a player in the enterprise content space.

"ECM has a penetration of less than 10% and the demand for content is very high. The old model that ECM has to be a suite is obsolete, " said Newton.

If you take into account the way information increasingly lives inside and outside the firewall, ECM becomes even more complex. Companies now have to figure out how to consume and create content in both environments, something Newton says Alfresco accomplishes by adopting a "content-as-service" approach. He argues that most enterprises lay out their palette of required services based on the need to create content. The focal point shouldn't be centered so much on the ECM suite, he argues. It has more to do with looking at "how the Web browser can help knowledge workers do their jobs."

And that's where the mashup mentality comes into play. Alfresco is smart enough to realize that the needs of tomorrow's enterprise will be heavily tied to its ability to create and consume content in real-time, regardless of platform, place, or device. Browser-based mashups will ultimately be one of the ways to empower that type of manageability and manipulation of content. John described it as simply asking, "what are the Web applications people want to use"?

But don't forget about the collaborative life of that content. It needs to live on your intranet, your corporate Facebook group, or perhaps within your partner's forum or Wiki. Mashups play perfectly in those scenarios. While Facebook-ing the enterprise is out of most vendors' comfort zones, Newton thinks the key is giving that capability to users and letting them create the next-generation of social software applications.

While that may be too progressive for some enterprises to stomach, it does highlight the trend of diminishing "command and control" mentalities. If you deter newer ways of collaborating, you're digging your own grave with "here lies a content dinosaur" as the epitaph.

"Content services should just be accessible wherever knowledge workers are. We shouldn't be forcing workers to go into these ECM suites. In our view, collaboration spans far more than ECM."

I'm betting Alfresco's legacy won't have anything to do with being an ECM suite.