The Future of Content Management - AIIM Conference 2011
•
6 likes•1,068 views
Content Management, including collaboration, is poised to make an evolutionary step further. Web 2.0, the cloud, and other innovations are changing the way people view, use, and interact with content. Understanding these new technologies how the impact the world of content management is critical to preparing to meet the new expectations, challenges, risks and rewards posed by these new technologies.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Future of Content Management - AIIM Conference 2011
Similar to The Future of Content Management - AIIM Conference 2011 (20)
More from Laurence Hart
More from Laurence Hart (14)
Recently uploaded
Recently uploaded (20)
The Future of Content Management - AIIM Conference 2011
- 1. The Future of Content ManagementCloudy with a Chance of Innovation Laurence Hart Washington Consulting, Inc. March 2011
- 2. Why Listen? Information Management 15+ years Document Management Records Management Web Content Management XML Collaboration (Grandfather of Enterprise 2.0) Digital Asset Management AIIM Interoperable Committee CM Pros, Chair Standards Group Author, Word of Pie http://wordofpie.com http://twitter.com/piewords Director, Technology Solutions, Washington Consulting, Inc.
- 3. Our World My content growing, evolving, and expanding. Cloud brings rain or hope?
- 7. And Everything Else Email Management Web Content Management Digital Asset Management Collaboration Records Management
- 8. Email Management Content Applications Web Content Management Digital Asset Management Collaboration Records Management ECM Project ECM Project ECM Project Process Services External Interfaces (SOAP, WS-*, RSS, REST, RPC…) The Enterprise CMS Platform Content Services Library Services Enterprise Content Management (ECM) is the strategies, methods and tools used to capture, manage, store, preserve, and deliver content and documents related to organizational processes. ECM tools and strategies allow the management of an organization's unstructured information, wherever that information exists. - AIIM Website, November 2010 Grand Unifying Theory Define ECM CCA Analytics Forms Reports
- 9. Web 2.0 Conversational Web 1.5 Transactional Meanwhile Web 1.0 Informational ECM Content Management ECM ECM
- 10. Two Problems
- 11. For Example U.S. Citizenship and Immigration Service Over 1 million new legal immigrants per year Average storage per file, 70 MB Keep for 99 years 75+ TB/year with ZERO back-file conversion Over 16 million benefit claims per year Everything is audited Multiple agency access
- 12. Two Outcomes
- 13. Req/Design Dev/Test Design/Dev Why the Lag? Enterprise CMS Platform Release Cycle Req/Dev/Design/Dev… Internet Generation Year One Year Two Year Three
- 14. The Unanswerable Question If all the obstacles to ECM adoption - e.g., user/culture acceptance, networks bandwidth, cost, security, etc.- were to go away, what would you do with ECM? Andrew Chapman http://nevertalkwhenyoucannod.com Fall 2010
- 16. Plato’s Cave 16
- 18. Focus on the User The Ether Tags: Proposal, Widgets, Draft, XYZ Inc, Work Share: Sarah(Partner)/Edit Tags: Approved Share: XYZ-Purchasing /Read
- 19. Unify the User’s Content The Ether
- 20. Simple Access
- 21. Map of the Future Omnipresent Content Management Old Guard Features Challengers “We Matter” Architecture
- 22. The Change Enterprise Content Management (ECM) is a strategy for the coordinated management of all content throughout an organization, allowing for people and systems to find and use content from within any business context. Omnipresent Content Management (OCM) is the coordinated management of all content throughout the world, allowing for people and systems to find, use, and share content from within any context.
- 23. You Ready? Twitter: @piewords Blog: http://wordofpie.com Email: lhart@washingtonconsulting.com
Editor's Notes
- A #CMSHaiku to set the tone.
- There was paper, and there was a lot of it. (Still is)
- Now we put the paper onto the digital network Itjust saved a few trees, but we still printed, signed, and scanned back into the network.
- We finally took advantage of the electronic and re-vamped our processes. It took the removal of the requirement to move paper for people to see what could be done to make life easier.
- There was more than Transactional Content Management/Document Management. Other systems popped-up, and then they started to be linked together. Eventually everything became a Record and one-way integrations became two-way.
- The idea of ECM was to unify the technology and make life simpler. It works well in theory, but it is complex, growing, and difficult to implement successfully.Formal definitionAdd a platformPlug-in the applicationsAdd interfaces to talk to other applicationsNeed to use best practices as ECM implementations fail regularlyAdd new features as they are identified
- The evolution of the Web, the consumer technology world. Improved interface increases expectations, increases content/data generated/collected, and the sheer number of users has increased as well.Conversations take place across boundariesManaging that interaction, live interactions cannot be “Approved” firstScale is growingThe Management of Enterprise Content has not evolvedFocus in the Internet is on the User, need it at workEnable conversations and collaboration without boundaries
- Meanwhile, content was growing exponentially and users grew on both sides of the firewall. Large “ECM” installations can quickly become mired in solving the technical issues of managing storage, data, and users, while not focusing on the business problem.While all those Content Management features have been added, there have been 2 massive problems building.More Content to ManageLots of users to manageMore unmanaged content than there was when I started in this profession35 Zettabytes by 2020 (2010 IDC Report) http://www.datacenterknowledge.com/archives/2010/05/04/digital-universe-nears-a-zettabyte/3.5 billion Library of CongressesGiga->Tera->Peta->Exa->Zetta->Yotta
- 10TB ~1 Library of CongressThis example can readily push the limits of even the most robust technology solutions out there. Keep in mind, this is just ONE type of content and ONE business problem atU.S. CIS.
- The sheer complexity of implementing these systems, can take their toll on Content Management experts.The “Jack Sanity Scale”.http://wordofpie.com/2010/12/09/the-jack-sanity-scale-of-content-management/
- “Enterprise” software has long development cycles between major releases. This is okay as you don’t want to upgrade some of those systems within your organizations every six months. On the flip side, innovation is increasingly difficult as those systems grow in size and complexity. For example, SharePoint 2010 still looks shiny, but how will it look in 2-3 years when the next version is nearing release?Where is the Agility?Stable platform, SaaS, enables innovation on the application layerConsumers no longer have to worry about migrations, upgrades….
- These items that we do everyday constitute most of the work. Content Management is rarely simple or straightforward. So much time is spent solving these problems that conceiving of the next thing is challenging.
- The first thing that springs to mind with that question…vacation!
- The real problem was that we couldn’t think of anything because we can’t see outside of our cave.
- If you remove those obstacles, there is a whole world out here. Just like the liberation from moving paper, not having to manage networks, storage, security, and other challenges will allow us to innovate.
- Steve finishes a proposal and saves it. During the process, some tags are applied (manually and/or automatically) and he marks it for sharing. He tags it as a “Work” document as well. Sarah is automatically notified and reviews the proposal. Once done, she adds an Approved tag and Shares it with XYZ’s Purchasing department. No email, no sending of links, no concern over what system everyone happens to use by default.Tagging can manual, automatic when analytics are smarterThis all nice, but why does it matter?Not necessarily the “cloud”, blend of Internet, Intranet, and LocalIf we don’t have to worry about the Management of Content (because it just happens), we can solve the user’s problems
- The same content shared everywhere. Even if multiple copies are stored, to the user, only one copy is stored and accessed from anywhere from any application.
- Need to have both Content AND Identities in the Ether. Do not confuse identity with personal information. There won’t be one single source for either. Trust is a factor, and not everyone will trust/like Microsoft, Google, Facebook, or Apple.This isn’t the generic “cloud”. This is Software as a Service. UI and Services.This isn’t centralized, this is coordinated.Standards make this possibleContent Management Interoperability Services (CMIS) is the CMS standard that makes it work.
- For lack of a better term, let’s call it Omnipresent Content Management (OCM). It is ever-present, pervasive, and everywhere. People won’t think about the system, they’ll just do their work.There are two basic types of vendors, established vendors with the needed feature set and young vendors with the necessary “cool” architecture. Not all are heading in towards OCM, but some in each set of vendors are heading there now.They are in a race to get there, whether they realize it or not. Claiming the mindshare by arriving first will be critical to vendors that want to “lead” in the future (3-5 years). I expect only 1 of the “Old Guard” to successfully make the transition. It doesn’t mean that the others will fold, but they will lose their leader status in the industry.
- ECM is still relevant, but it is just a strategy. You still need to manage your content, but it doesn’t need to be centralized. Standards, such as the new Content Management Interoperable Services (CMIS) standard, will allow the separate systems to work together without having to spend all the time writing integrations and policies.OCM is an extension. The lessons learned from ECM will apply. Standards are even more critical, but the same ones can be used. The goal is lofty, but it will let us get back to working and collaborating without thinking about any of the mechanisms.