{"id":204,"date":"2015-03-15T18:27:44","date_gmt":"2015-03-15T18:27:44","guid":{"rendered":"http:\/\/kb2.host.dbj.systems\/?page_id=204"},"modified":"2015-03-15T18:27:44","modified_gmt":"2015-03-15T18:27:44","slug":"enterprise-content-management-is-not-information-governance","status":"publish","type":"jetpack-portfolio","link":"https:\/\/dbj.systems\/kb\/portfolio\/enterprise-content-management-is-not-information-governance\/","title":{"rendered":"Enterprise Content Management is not Information Governance"},"content":{"rendered":"
\n

Enterprise Content Management is not Information Governance<\/h1>\n<\/div>\n

Quite a lot is written these days about information management and information governance.\u00a0Analysts are predicting that effective information management and governance can be a game changer for enterprises.<\/p>\n

BUt.\u00a0Doesn\u2019t this sound a lot like Enterprise Content Management, or ECM?\u00a0 Aren\u2019t there already plenty of successful vendors, ECM installations, and ECM strategies at work across companies at all levels, for many years now?<\/p>\n

ECM and IG are not the same<\/strong><\/h2>\n

In the world of enterprise content management, everything hangs on one single\u00a0principle: that each document is unique, serves a defined purpose, and is therefore managed.<\/p>\n

ECM is critical to regulated industries such as pharmaceutical, where even the specific revisions of drug labels must be managed and ECM solutions provide reliable, defensible tools.\u00a0 ECM aids companies who regularly develop collaterals, training materials, as well as mundane activities like tracking contracts, document revisions, and so on.<\/p>\n

This is not information governance, however \u2013 nor is it information management as the world is beginning to understand it.\u00a0\u00a0 The ECM world already assumes a one-to-one relationship, which is why ECM has never proven to be a solution for information governance.<\/p>\n

Information management and governance \u2013 the one-to-many conundrum<\/strong><\/h2>\n
\"One
One to Many<\/figcaption><\/figure>\n

In the information governance world, the rule of thumb is one-to-many. \u00a0And this is driven largely by email!<\/p>\n

Email by its nature is repetitive:\u00a0 even email archiving systems cannot and should not eliminate duplication.<\/p>\n

In cases where an author sends the same document attachment to multiple recipients, logically all copies point back to the same central document. But as that document moves outside the organization, gets multiplied, is commented upon, and becomes the foundation for an email dialogue, the same information will be repeated and multiplied to make the matters worse.<\/p>\n

Information governance has to go beyond the notion of identifying a single document or item and then tracking all revisions.\u00a0 In the case of email, these revisions are derivatives in branches \u2013 in other words, conversations.\u00a0 An\u00a0ECM\u00a0management solution can\u2019t handle this situation, at least not easily.<\/p>\n

Managed per content vs. managed per value<\/strong><\/h3>\n

Another way to look at ECM is to look at how information is managed. ECM manages based on content:\u00a0 what\u2019s in a document determines how it and any documents that relate to it are managed. This is how revisioning for example works: inside each revision only changed content is stored not the whole document.<\/p>\n

In the information governance world, there are simply too many variables.\u00a0 Going beyond mere duplication, there is also the challenge that content simply \u201ccomes into\u201d an organization via email and then forms the basis for other content.\u00a0 The process is random.<\/p>\n

The key to information governance is understanding the value of content and then applying management.<\/p><\/blockquote>\n

This is exactly and also is what Big-Data is all about: value of the whole content. Content (aka Information aka Data) \u00a0Value has been elusive, but think-groups like the Information Governance Initiative have begun to identify how companies are being successful in valuing information, (often by using Big-Data platforms).\u00a0 Often, the mere age of the information is a measure of its value:\u00a0 email is transient by nature, and unless mail refers to a specific subject that is managed differently (example, emails discussing pharma\/client relationships at bio-tech\u00a0institutions), its value decreases as it ages and it ultimately becomes worthless. And toxic as IT Regulators are very keen you don’t store but dump old information. \u00a0Companies have successfully ascribed any pre-determined aging to such documents and, as\u00a0they are covered by legal holds or compliance regulations, delete them after a defined period.<\/p>\n

Modern enterprise needs both ECM and IG<\/strong><\/h2>\n

Is this really true for each and every mid to large Enterprise? The answer is probably yes, but it is easier to answer whether or not they need enterprise content management (ECM) first.<\/p>\n

There are a number of ways to handle content within an organization, and solutions regularly overlap.\u00a0 Multi-disciplinary solutions like SAP and Oracle provide content management as well as enterprise resource management, routing, tracking, programmatic responses, and the like.\u00a0 Rarely do they provide information governance for unstructured information like emails, and in cases where they do, that email is often associated with other content.<\/p>\n

Information governance (IG), on the other hand, first and foremost requires mature organization with mature and repeatable governance in place.<\/p><\/blockquote>\n

On the implementation level, IG can be simply an archiving solution:\u00a0 capture and preserve email to satisfy regulations and later search and discovery.\u00a0 At its most granular (read: complex) level, IG\u00a0implementation can, similar to ECM, play a role in identifying unstructured content, categorizing it, and applying very company and content-specific management rules.<\/p>\n

Companies need both for different reasons.\u00a0 Companies usually need ECM platform, because the particular type of information being managed is critical to their business.<\/p>\n

Companies need information governance, on the other hand, because there is too much unmanaged and unstructured information flowing throughout their organizations.\u00a0 Without management, they are unable to mine any potential insights from that information.\u00a0 Without management, they are also unable to mitigate any risks that information may pose. And this is one very critical driver becoming obvious as from 2015 Q1. \u00a0Information can and will become toxic just as any other waste: if dumped anywhere it will develop its toxicity through time. As any “big bank” knows by now, for example. On the other hand if old and stale information, is classified and incinerated it will be safely disposed of.<\/p>\n

And make no mistake: informations protection regulators are already here.<\/p>\n

[In part inspired by an article published February 2, 2015 By Dave Hunt<\/a> 0\u00a0<\/a>]<\/p>\n","protected":false},"excerpt":{"rendered":"

Enterprise Content Management is not Information Governance Quite a lot is written these days about information management and information governance.\u00a0Analysts are predicting that effective information management and governance can be a game changer for enterprises. BUt.\u00a0Doesn\u2019t this sound a lot like Enterprise Content Management, or ECM?\u00a0 Aren\u2019t there already plenty of successful vendors, ECM installations, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"footnotes":""},"jetpack-portfolio-type":[87],"jetpack-portfolio-tag":[88,96],"class_list":{"0":"post-204","1":"jetpack-portfolio","2":"type-jetpack-portfolio","3":"status-publish","4":"format-standard","6":"jetpack-portfolio-type-compliance","7":"jetpack-portfolio-tag-content","8":"jetpack-portfolio-tag-governance","9":"czr-hentry"},"jetpack-related-posts":[],"jetpack_sharing_enabled":false,"_links":{"self":[{"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/jetpack-portfolio\/204","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/jetpack-portfolio"}],"about":[{"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/types\/jetpack-portfolio"}],"author":[{"embeddable":true,"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/comments?post=204"}],"version-history":[{"count":0,"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/jetpack-portfolio\/204\/revisions"}],"wp:attachment":[{"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/media?parent=204"}],"wp:term":[{"taxonomy":"jetpack-portfolio-type","embeddable":true,"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/jetpack-portfolio-type?post=204"},{"taxonomy":"jetpack-portfolio-tag","embeddable":true,"href":"https:\/\/dbj.systems\/kb\/wp-json\/wp\/v2\/jetpack-portfolio-tag?post=204"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}