Document Management vs. Content Management vs. Knowledge Management Part 2 – Understanding Content Management

31st May, 2009 - Posted by Sean R. Nicholson - 1 Comment

Sean R. Nicholson

In the second article in this series, we’ll focus on understanding Content Management and how it differs from Document Management and Knowledge Management. If you recall from the first article in the series, Document Management is all about how we create, manage, route, retain, and destroy the container that we refer to as a document. Content Management, on the other hand, focuses primarily on the information stored inside that container and how you can effectively add/edit/delete the information in the document.

Keep in mind that while some folks use the term “document” generically to refer to Microsoft Word documents (primarily because they use the .doc extension), a document can also be an PDF file, an HTML file, a Microsoft Excel spreadsheet…really any kind of container that holds content.

Distinguishing Between Pure Content Management And Enterprise Content Management (ECM)

Note: Before we dig into the details of Content Management, we need to establish that the focus of this article is to define and discuss pure Content Management separately from Enterprise Content Management. ECM blurs the lines between Document Management, Content Management, and Knowledge Management which, when brought into the conversation,  makes it difficult to discuss each of the separate components on their own merits. So, for the duration of this article, take a step back and let’s just focus on the Content Management component, apart from ECM. In the final article in the series, I’ll bring it all back together to discuss ECM.

So What Is Content Management?

In it’s simplest term, content management is simply editing a document to add, replace, remove, or modify the content. When you open a new Microsoft Word document on your desktop and type a few lines of text, you are engaging in content management using MS Word as the content management tool. You then save the document and store it on your computer, network location, or document management system. Through this process, you have engaged in both document management (the creation and saving of the document) and content management (the adding of information inside the container). Simple, right?

Content Management becomes much more challenging for organizations when you ask many people to collaborate at the same time on the same document. Issues arise such as the following:

• How do you keep one person from overwriting the content that another has added?
• How do you keep people from corrupting documents by editing them at the same time?
• How can you control the quality of the content to ensure proper spelling and grammar?
• How do you audit when someone last edited the content?

The existence of these, and many other issues has driven the creation of tools that allow organizations to collaborate around content, aka Content Management Systems. By introducing functionality such as user accounts, authentication, check in/check out, change tracking, and rich text editors (aka “WYSIWYG”), Content Management systems have addressed many of the concerns created by mass collaboration by limiting what individual contributors are allowed to do with the content and tracking when content is being edited. By leveraging this added functionality, organizations can minimize some of the risks of mass-collaboration and can maximize of the benefits that content management tools offer.

Different Kinds Of Content Require Different Editing Tools

In their early days of distributed content management, CMS tools focused primarily on editing Web pages. These Web Content Management systems allowed non-technical users to create, edit, and publish content to corporate Web sites and Intranet portals without having to know HTML, JavaScript or any other coding languages. As a result, organizations were able to empower their business users to take ownership of the content in their Web site and Intranet portals without having to engage IT for each and every change. In addition, the use of user accounts allowed organizations to control which roles were allowed to create content, edit it, and approve for publication.

Because of the proliferation of these tools and the rapid organizational adoption of them, the term Content Management System became synonymous with Web Content Management System. But as organizations saw the value of these systems and a variety of different types of content were introduced into the enterprise, new content management tools were needed.

For instance, digital assets such as images, videos, Flash movies, and audio files presented new challenges. To maintain the quality and appropriate use of these corporate assets, Digital Asset Management Systems were created to all organizations to manage the assets in a similar fashion to managing documents, while allowing some content management functionality through plugins with popular editing software like PhotoShop and Flash.

Document Management and Content Management Come Together Through Business Process Management

As the ability to edit different types of content has grown, organizations have recognized that the content management and document management can be intertwined to improve on business processes. Business Process Management tools provide organizations with graphical workflow solutions that allow for the creation and routing of documents from one user to another. upon arrival in their workflow queue, users can edit or review the content using a content management tool and then finalize the document or route the document to another user or queue for further processing.

Business units like Accounts Payable, Human Resources, Contract Management, and Decision Support have optimized document and content management by applying automated business rules that allow the document to be management in a specific manner based on the content.For instance, in situations where an invoice has a low total amount (say under $500), an organization can auto-approve the payment of the invoice without a high level of risk. In situations where total invoice amount exceeds a threshold, the workflow can route the document appropriately for a content review to ensure proper auditing.

Bringing Content And Documents To The Users Through Knowledge Management

The process of creating documents and managing their content continues to become more difficult as the volume of information in the organization grows. Effective organizational content and document management strategies are going to have to find ways to get the right information to the right user. To do this, business process tools and content management systems are going to need to leverage knowledge management principles to evaluate content and route content appropriately.

In the next article in the series, we’ll take a look at how Knowledge Management principles can be used to ensure that content is being effectively reviewed and used in the organization.