The future of Content Management is the continued extension and reach of ECM systems. Much of the success of these systems to date has been the integration of document repositories with role based permissions, audit tracking for compliance, enterprise workflow, and web publishing. However, the emerging needs of team collaboration will continue to drive new functionality including:
Leveraging Social Networks
Rather than providing pieces of social networking, there must be direct integration with Twitter, Facebook, IM, and other relevant Web 2.0 technologies. Unlike blog and wiki support which many vendors have partially replicated, these social networks are all about reach and extending information beyond the corporation. Harness the fact that many users enjoy these systems outside the workplace and put the tools to use in-house. Of course there need to be safeguards and monitoring for data-loss prevention, but the benefits of user productivity and adoption are worth the effort.
Support inside and outside the firewall
Most ECM systems were designed when corporations maintained all functional teams within the organization. With today's dynamic and economic constraints, it is most likely several key rolls are outsourced whether for marketing collateral, analyst relations, development, or customer support. Rather than having to extract content from the content management system and exchange it with these outside contractors using email, FTP, or some other file exchange, ECM systems should have options for replication or exposing limited content outside the corporate firewall. Enabling this work process while maintaining the auditability and management of the content is key.
In many cases, a cloud or SaaS based offering will best address this need. The lower startup cost and reduced IT overhead offered by solutions like SpringCM, Google Wave, and Content Circles can complement investments made in the corporate ECM by providing the tools needed for distributed teams without significant cost and delay.
Desktop and Mobile integration
The biggest challenge for ECM within an organization is getting users to use it. Most users will review a new system when it comes online or is mandated by IT, but most will abandon the system when it becomes to cumbersome to use or out of their day-to-day work process. Most content is created and maintained on the desktop so ECM systems must include desktop integration to eliminate the rigorous upload/download cycle that web based content management assumes. Desktop integration should also offer local access to content so even when their laptop is offline they have their most important content with them at all times and can sync updates back when they get online.
Mobile integration would take this a step further to enable email or app delivered notification of content updates as well as potentially remote access to content for review or sharing even if the user is away from their desktop. It will be several years before mobile devices can legitimately provide anything more than a read-only experience, but remote access to notifications and content would address the majority of the need.
User-centric auditability and tracking
Gaining insight to the usage of an ECM system is key for an organization to improve adoption across the corporation. The advanced analytics most Web 2.0 web sites have today must be offered within the ECM system so active users, popular content, frequent searches, trending topics, and new uses of the system can be identified and exploited. For ECM to be a vital part of every employee's workday, careful attention should be paid to how those users are using the system and look for ways to further enrich their experience.
Uniform repository access with CMIS
The OASIS CMIS standard promises to achieve what Shamrock, WebDav, and JSR-170 have failed to do -- broad industry support for a common repository API that customers and 3rd parties can leverage to avoid vendor lock-in and enable innovative new extensions. ECM vendors should focus on providing the best tools and capabilities rather than holding corporate content hostage. With strong support from market leaders including IBM, Microsoft, Oracle, Alfresco, and Day demonstrating reference implementations of the standard, hopefully we will finally have the right interface for repository integration.
We are very excited about the future of content management and hope to see more and more innovation to help bring ECM capabilities to the masses. Our thanks to Julian Wraith for inviting comments on the "Future of Content Management". You can follow this topic with hashtag #CMSFuture or the MD5 tag 6f82f1d2683dc522545efe863e5d2b73.
