The Business-Technology Weave


November 30, 2012  3:15 PM

Content: The Life of a Managed Document

David Scott David Scott Profile: David Scott

Essentially, the life of a document and its associated control would go something like this:

Creation:  Staff creates new content, perhaps a new word-processing document.  This new content may be generated as entirely new material, or it could be content that is being repurposed and built upon (edited and added to) from existing content.

Filing (Storing):  The new content is filed, as a file’s creator would normally generate and store documents (File, Save, or Save As…, etc.).  The Repository will take action based on the file’s destination folder; based on the creator’s choice of  folder  according to subject matter, and the content’s relation to other like-content. 

Categorizing (Taxonomy):  Storage is also the means by which content is categorized; by virtue of the folder in which content is stored by the creator.  Folders within the Repository will be dedicated to specific categories of content.  Depending on your desire, the content management system can also suggest storage and categorization based on its inspection of the document’s contents at the time of its creation, and subsequent comparison of key content to an organizational taxonomy table. 

Metadata (Tagging):  The content’s location and categorization also lead to the assignment of key metadata.  The document’s metadata is assigned by virtue of a metadata template that is associated to each content area (folder).  This way, each template’s information is leveraged for the tagging of all like-content in a specific folder.  The system can also extract keywords from documents for inclusion to the metadata, and can generate an abstract or summary.

Delivering/Sharing:  Content is now delivered when users query for various categories of content, on keywords, and concepts.  Collection and reference of data is now as comprehensive as possible.  You can even have your content/records manager query on content that has specific areas of metadata that are unpopulated (unfilled) – for purpose of generating a report concerning these documents.  The report(s) can then be delivered to various content authorities for completing the assignment of metadata to this content.

Re-using and Repurposing:  Now that content is locatable, identifiable, accessible and readily understood, it is easily employed for reuse.  With proper authority and access, departments can glean knowledge, formatting, and process from other department’s content.  Further, content can be repurposed:  it can be modified and incorporated to new content.  

Review and Reporting:  Content now is available for review by any appropriate authority.  Reports can be run to review all documentation generated in a given day for a specific client, for example.  You can view who produced the most effort – who is doing the bulk of the real work? 

This is also where you take action on content in accordance with a retention plan.  Disposition dates of documents provide the yield for a monthly report.  The report can indicate all documents subject to archive, and subject to destruction (pending review by the appropriate authority, of course).  This report can also expose those documents that must have their disposition date adjusted – this can be due to reasons of regenerated business, inquiry, subpoena, discovery, etc. 

Action:  Once content ages to the point where it is no longer being accessed (easily determined by reports), and is unlikely to provide further, or timely, business value, it can be archived or destroyed.

     – Archiving:  Archiving the information means that you remove it from your active business environment, and store it somewhere else – perhaps with a vendor who maintains your offsite backups, or in an offsite warehouse where your organization makes other storage of items.  Archived material can be compressed and stored on high-density (high capacity) storage media, such as DVDs and CD-ROMs. 

This material is cataloged, and can always be referenced if the organization needs to go back to it.  It can even be reintroduced to your active business environment if the need arises – nothing is “lost.”  The purpose in archiving is to prevent the active business environment from becoming overrun with useless data.  Taken to its logical extreme, if you don’t manage the removal of relatively useless data, it will eventually outweigh your useful data. 

     – Destruction:  Business material that becomes completely obsolete, as determined by Business, and technical documentation as determined by IT, should be destroyed.  Anything that serves no further purpose to the organization should be destroyed.

A Practical Example:  Let’s provide a quick practical example in the life of a document: let’s say that the organization has a current project; Project LMN, and associated content.  The project’s scope or domain could be anything: a marketing initiative, it could be legal representation of a client, it could be a new software solution and its implementation. 

Project LMN documents reside in a specific Project LMN Folder – that folder would have an associated metadata-template for the management of this project’s content.  Also, the main folder would have attendant subfolders, such as an LMN Budget folder for specific budget info and docs regarding the project.  Of course, specific subfolders to the main project folder would have their own metadata templates too.  Subfolder-templates can inherit the main folders metadata if you like.  However, many subfolders will require at least some unique metadata information.  For example, it’s likely that budget material associated with the project has a specific authority for access and edit; so, a budget subfolder within the main project folder would have a metadata template that differs, and it will tag budget information with different metadata.  Of course, authorized content creators and users within any folder can edit and tweak metadata to reflect the desire for control and disposition of that particular content.

Creation of new LMN content, such as a document, would bring up a dialog box requiring a destination folder – once identified, that folder’s default metadata would fill this new document’s specific metadata template.  This would tag the document based on its content, and its match to taxonomies used in the organization.  Thus, when we create and file content in a specific folder, it gets tagged with appropriate metadata based on the folder’s template.  In this manner, controlling elements that are common to all Project LMN material are applied to content: Such things as the document’s title, its category (Project LMN), its life, its disposition instructions at the end of that life, its securities and permissions, among other things. 

In addition, other specific tags relevant to the document itself are made.  The contents can be surveyed by the system in order to automatically generate very specific metadata that is relevant only to that individual document – extracting keywords such as author, names, places, dates and other key information.  The system extracts these things based on built-in pattern recognition.  These keywords can be gleaned based on a predetermined list provided by the vendor’s application, and by your own internal table of keywords – you can build your own custom pattern recognitions. 

This document could also inhabit multiple categories:  for example, its metadata could indicate that it is a general budget document, and contains specific Project LMN budget components.  The document would have a disposition date for archive or destruction, in accordance with the project’s standing in your retention plan, and as necessary, within compliance for any of the other categories. 

The creating user would either accept the metadata, or edit it – as authorized.  All new content that is generated and saved within the Project LMN area of the Repository will automatically assume the appropriate metadata for the management of that content.  Now the document is enriched according to attributes and keywords associated with that document – things your users can identify and use when searching for LMN content.  This way, authorized users can search, browse, and aggregate critical content regardless where the content is stored. 

Let’s say a creator generates a document regarding the project, but chooses to store that document in their User folder.  This is ok, since the document’s overall subject matter (Project LMN) will still allow appropriate categorization, and subsequent associated default metadata.  The system will still review the document’s content in order to generate the other specific metadata.  In fact, a likely scenario would be one whereby an authority would arrange for a Project LMN subfolder within all User folders for those staff associated with the project – using the same default metadata template for the main Project LMN Folder. Therefore as you go along, all Project LMN documents will be traceable, retrievable, and actionable no matter where they reside – in user folders, central project folders, or even e-mail, if desired, and no matter what the form of the document: wordprocessing, spreadsheet, presentation, or e-mail.   

We’ve now enabled a powerful way to identify the Project LMN files, and anyone associated with the project can search for them, and if authorized, access and use them.  When we capture content, we can: develop; manage; review; approve; archive; check-in/check-out; maintain version control; perform full-text and metadata search; optimize team communication; automate routing requirements; and deliver notification of status changes and new documents.  We can provide specific information and the surrounding context needed to optimize work within the project team.  We add value by exposing such related material as additional documents, tasks, calendar items, and team e-mail.  Our intellectual capital is in a secure, centralized repository.  All project matter is centralized and accessible.

This material can also be copied and repurposed within other projects and initiatives when it has relevant content.  Too, when Project LMN is long completed and done, and its material no longer of any practical use in the active environment, this content can be fully identified and acted upon for ultimate disposition.

November 29, 2012  6:14 PM

CMS: Getting to the “System” of Content Management

David Scott David Scott Profile: David Scott

[Note:  You may wish to visit the beginning of this series by scrolling down several articles.  If landing here brought you to a solo-article, Google “The Business-Technology Weave” and scroll]

The Content Manager

We’ve established background regarding content management.  Let’s introduce one more important thing:  a content manager in the form of a qualified person.  Increasingly, Content Managers (or if you prefer, Records Managers) are operating within a certified discipline.  Most if not all of the standards regarding the general duties of a content/records manager are detailed on the web.  Organizations that are about to embark on a full-scale content management solution and system should hire or delegate a content/records manager at the outset of the project.  This person also is a logical choice for this project’s selection as project manager.  As with all projects, make this selection carefully: It is this person who will drive the organization’s qualification for selection, implementation, and use of a system.

 The “System” of Content Management

Instituting management of content where there has been no real management is a daunting challenge to most.  There are so many forms of content, in so many differing structures, in so many different places, within the authority of so many different individuals and departments: Yet, if we can understand one area, we can understand them all.  The principles are the same. 

Let’s gain an understanding for the management of unstructured electronic document content first (your word-processing documents, spreadsheets, presentations, and any other unmanaged electronic, unstructured, data).  This is an area that most organizations tackle first – and, an area that is frequently most in need of control.  We can say that unstructured electronic documents take this priority because, conversely, structured (database related) content is at least managed to the degree of their native applications. 

We can also afford to prioritize electronic documents over hardcopy assets in most cases.  This is because there is a comparative advantage regarding hardcopy content:  ordinarily, it at least exists where you can see it.  Because hardcopy content is physical, you have a better chance of at least sensing where common subject matter exists.  We can point to a file cabinet and declare:  “Those are accounting records.”  And, “There are more accounting records over there in those cabinets.”  It is more difficult to do the equivalent with electronic data. 

Our understanding of the methods employed for unstructured electronic documents – and lessons learned – then position the organization to effectively take on other areas of content, in-turn.

Electronic Document Management – A System of Control:  Think of content management as an establishment of control over data by enriching it.  We enrich data by assigning information “tags” to individual electronic content – to individual files.  These tags mark the file according to what it contains – that is, according to its content.  Once tagged and so marked, an associated application system can grab and assemble that data with other data.  This enables and simplifies our research of data; and enables our ability to report on data for administrative purposes.  This tagging (enriching) of data is effected through the assignment of metadata to the individual document files.

Metadata has been described simply as data about data.  This is a great definition for our purposes.  Metadata tags are based on the subject matter and other general attributes of the specific document’s content, and can include such information as:

      – Document Title

      – Category (or Categories; based on Taxonomy)

      – Author

      – Abstract or summary info

      – Access (permissions)

      – Usage history

      – Keywords (dates, places, individuals, etc.)

      – High-value concepts

      – Disposition date (archive and/or destruct triggers)

The real power comes when metadata is automatically applied to documents, records, web content, and other digital assets according to a schema, or template.  Various templates contain prepared metadata for each condition of content in your organization, according to policy.  These prepared templates are then assigned to electronic workspace folders – much like those already in your network environment. 

When you create content, and file it in a relevant folder based on content’s subject matter, the metadata is automatically applied to that document.  A dialog box with default descriptive (enriching) information tags pops up.  The document’s creator accepts the metadata as is, or can manually edit specific fields of metadata.  Once accepted, the metadata is tagged to that document, and it becomes managed content.  When we query data based on content-criteria that is available through this metadata, we receive all relevant documents which satisfy our query – in a fast and comprehensive way.  The structure that supports the linkage of metadata templates to folders, and which supports all other action and reporting utilities within the managing of content, is a data Repository

The Repository:  The Repository is a component part of the vendor-delivered, overall content management solution.  User action is taken on data through their normal native applications – a word-processing application in the case of a word-processing document, for example – but with the added benefit of the Repository’s control and enhancements to data (such as the metadata tagging).  Further, an allied Content Management software application accesses the Repository to perform content management and administrative functions – such as finding, reporting on, and taking disposition on content.   

Various vendors may have differing names for it, but essentially a Repository is a vessel for data.  As desired, it can mimic your current network structure of folders and permissions.  This way, it will present a familiarity to users as they negotiate for files, and save new files.  In this regard, the Repository is relatively transparent – but it brings with it several very important utilities.  The Repository represents the achievement of a specialized, central, storehouse of data.  It not only will have a similar structure of filing as a network hierarchy, the Repository will facilitate proper filing and control of new content as it gets created, according to subject matter.  It manages data’s security.  It maintains and facilitates reportage and action on data so as to enable oversight.  It does this in a very efficient way, removing this burden from the content’s creator and the organization at large.  The Repository is the key by which content can be found, accessed, used, repurposed, reported on, and actioned for administrative oversight.


November 28, 2012  2:13 PM

Content: Getting to CMS – Qualifying to identify a solutions partner

David Scott David Scott Profile: David Scott

Delivering content management to the organization requires an outside ‘solutions partner’ – a vendor.  The vendor will supply and help to fit their content management product – a system – to the organization’s needs.  It is important, therefore, that your organization understands the nature of your content, the business processes that rely on this content, and the products, services, and positions that your content supports.  Come to agreements regarding content in your BIT (Business Implementation Team) meetings, select a content/project manager, and project management team.

Have the project manager research content management in order to qualify their understanding of it.  The PM should task other project members for the gain of necessary knowledge too.  Here, Business leaders should avail themselves of all material at their disposal – content management is detailed very nicely on the web.  Outside training classes are available too.  Thus qualify the organization to solicit vendor presentations as potential fits to your content management needs. 

Just as there is no “magic ignorance,” there are no “magic vendors.”  Don’t expect to have vendors come in to educate you from a cold-start regarding content management.  Do some research, understand your needs thoroughly, review this chapter as necessary, and be an informed player.  It is ok and necessary to query vendors and to learn from them – but you must be able to judge any vendor’s veracity, capacity, and true value.  To do that, you need some solid base knowledge – and you need to fully understand what you expect from the vendor in vetting them against, and in fulfilling, your needs.


November 28, 2012  2:09 PM

Content: Absent CMS, structured data is “Unstructured” relative to the enterprise

David Scott David Scott Profile: David Scott

Within the emerging necessities for leverage of content, and management of liability, we have to recognize something else.  Absent a comprehensive Content Management System (CMS), not only is unstructured data outside of a central control; even structured data, such as records in databases, and e-mail within systems, is not within a central control.  The records are not leveraged across and with the full enterprise of information.  This is because structured data is only actionable within its own native application; database records within the database application, and e-mail records within the e-mail system, as but two examples. 

Any of your other disparate systems of “managed” data, such as the accounting system, core-business management systems, claims systems, HR systems, and so on, suffer the segregation from other systems’ data and content.  This segregation of data is normally an asset: it is necessary for data and system integrity.  But from the content management perspective, it’s a liability.  Therefore, absent a true CMS, structured data has no “central” control when viewed in the totality of the organization’s enterprise-wide content – much of which is ancillary and extremely important in the context of certain necessary views.  This ancillary content can be other structured content, silo’d in its own application’s control, or it can be relevant unstructured data.

For example, records within core business applications, such as customer or member records, are only searchable, retrievable and reportable through those native applications.  That is, each customer record exists within the control of an application system, and can contribute to report information when combined with data from other customer records, from within that same application. 

Suppose you wanted all the information, as of a certain date, that your organization harbors for a client – EFG Corporation.  Perhaps upcoming litigation is driving your concern.  You want all statuses regarding EFG from your main client business application; all relevant e-mails from respective employees and client contacts; all policies referencing EFG; all letters and correspondence; and location of all hardcopy reports and products regarding EFG.   Without an independent system that manages your content – all content – you cannot automate a comprehensive, enterprise-wide search of electronic content by criteria.  Too, without the electronic cataloging of hardcopy, you cannot query content’s physical location in support of the current need.

Assembling a comprehensive report in this regard would involve searching for data within many controlling systems, manual assembly of some data, and some kind of tedious collation from the many disassociated parts.  Here, your best option is to produce reports from the disparate systems, and then tediously assemble and format information.

And – you’d have no real way of knowing if you had captured all relevant content.  So, in the context of “full asset leverage and liability management”, even structured data is “unstructured”.  If you are interested in, and need, true content management, then you must structure all of your data for dictate by an overarching system in order to achieve ready action and oversight. 

Business users today need a means by which they can approve and review content during its creation and use, regardless of format, regardless of its location.  They must be able to search for and quickly find content.  They must access the most current versions of various content.  They need to be able to repurpose and share content (as opposed to “reinventing the wheel”).  They must have confidence that when seeking content, they are finding all relevant, authorized content.  And, they must identify and dispose of content at the end of its useful life.


November 28, 2012  1:59 PM

Content: The proliferation of unstructured data

David Scott David Scott Profile: David Scott

We know that business success will increasingly depend on the most efficient use of its information assets.  These assets must be centrally managed for security purposes, and for quick dissemination to where they’re needed.  To do this, we need a special structure around data – all data – to manage it.  But in the vast majority of organizations, information is scattered throughout a variety of resources and vessels.  There is no cohesive, managed plan of access according to actual work, leverage, or liability to be had by the content of the individual information asset.  The data is “unstructured” – that is, there is no ready “handle” by which to identify data according to its relevancy, its level of importance, or its possible liability.

We have things locked up on servers, workstations, filed in various cabinets, and piled on desks.  Content is parsed, fragmented, dispersed, etc., between electronic documents, e-mail, images, and hardcopy – all being managed, if at all, within discreet “silos” of various “systems.”  Under these circumstances, the content is not only difficult to leverage – it is difficult to ensure that the most current version of information is shared across the organization.  It is even difficult to guarantee that the organization’s various disciplines are presenting compatible information to the outside.  Yet, The Gartner Group reports that 80% of all information generated by business today consists of unstructured data.  Compounding this situation is the estimate that the average employee spends 50% of his or her time looking for things. 

What exactly is unstructured data?  Unstructured data is anything that lies outside of a centrally managed, and accessible, “repository.”  (A repository can have special meaning, and we’ll revisit it shortly).  Unstructured data is generally in the form of documents, spreadsheets, presentations, e-mails, and any other electronic form for which no automated central control can be exercised. 

A piece of unstructured electronic content (such as a document) does not represent a “record.”  It does not belong to a community of other records, sharing similar structure and collective maintenance, through a common base of data:  a database.  Therefore, it’s not that we’re refusing to leverage these unstructured items (through the lever of common, related, or timely content) it’s that we’ve never had that lever with this unstructured material. 

Unstructured data also exists in the form of hardcopy data.  When hardcopy has no centrally managed measures for leveraging content, we know that reinforcing subject matter can be scattered throughout all manner of departments and disciplines; residing in filing cabinets, on shelves, on desktops and in desk drawers.  Frequently it’s stacked on the floor, or hidden away in boxes.  Industry analysts estimate that Fortune 500 companies lose $12 billion each year because they cannot manage and take full advantage of unstructured content. 

Regardless of your size – if you don’t know something exists, you can’t use it; if you can’t find it, you can’t use it; if you’ve lost it, you must recreate it; and if it takes time to find it, you’ve lessened your efficiency in using it.  This kind of inefficiency and duplicated effort is plain unaffordable. 

Unstructured Data’s Other Liability:  Consider too that it is impossible for a central authority to state with ringing certainty that your organization is not harboring inappropriate content.  Are you certain that employees aren’t downloading obscene or illegal material?  Can you certify that people aren’t passing around defamatory information through e-mail?  Can you be certain that employees are not using company e-mail accounts to post to Internet sites and blogs (web logs, message boards) that support positions or advocacy that is contrary to your organization’s positions?  Can you be certain that employees aren’t using these same company accounts as reference when ordering products and services of questionable repute?  All of these things leave an audit trail, outside the scope of your control in the absence of content management.  These things can impact your organization’s good name and can bring harm to your business. 

What about hardcopy?  How can you know that laxity and carelessness aren’t contributing to loss of this material?  Anyone can print out sensitive information, take it to an offsite meeting, and leave it behind.  How do you know whether staff is complying with your Acceptable Use Policy for this content and associated resources?  Without some kind of structure for review and report on data, you can be certain of nothing.  This is the gross inefficiency and liability that springs from unstructured data, the associated lack of control, and the uncertainties it brings.  Uncertainties will be increasingly unaffordable to business, as we shall see…


November 28, 2012  1:51 PM

Content: Business enlightenment, and knowing where we are

David Scott David Scott Profile: David Scott

We must realize that managing your organization’s content requires a strong, steady commitment on Business’ part, and it must in fact be Businesslead in getting this off the ground.  There must be understanding and sanction from the top.  There must be enterprise-wide sponsorship.  There must be a strong business presence in the BIT meetings.  In specific project management meetings, there must be a solid, knowledgeable business representative for each phase of the project’s implementation.  In this regard, and most others, IT will help design and will deliver the crank that turns and satisfies the process – but Business must define the business requirements and expectations of the crank.  The business process that the crank will turn must first be identified. 

These needs of the business are based on its size, nature, number of locations, volume of content, regulatory requirements, risk management, protection against liabilities, employee oversight, and anything else the business requires of content management.  Don’t make the mistake that so many other organizations make, on so many other initiatives: do not try to make this an IT-driven initiative: Business cannot drop content management on IT and say “take care of us.”  This must be Business-driven.  It is, after all, business-content that will be managed according to internal and external requirements and standards best known by Business. 

Remember that IT can, and should, do research and make suggestions.  But remember too that IT’s primary purpose is to align a right-sized solution to the policy and process defined by, and required by, Business.  When we make projects such as Content Management, and the creation of associated policies, Business-driven, we guarantee Business sanction, Business sponsorship, and full Business participation and commitment.  IT’s participation in these regards is already guaranteed by its report to, and subordinate status to, Business.  For Business and IT:  Make sure that these understandings are “Where You Are.”


November 28, 2012  1:47 PM

Content: The retention schedule

David Scott David Scott Profile: David Scott

Once an organization’s documents are categorized, their content’s retention is then managed on a schedule.  The schedule simply lists various categories of content based on taxonomy, each category’s retention period, and action taken on that content after the retention period expires.  Only your organization can capture the comprehensive categories of documents relevant to your business.  We cannot craft “generic” retention, and content management, policies here.  Therefore, purely as an aid to understanding, let’s show some broad examples.

An organization should have a schedule for its “defining” documents; things such as records of incorporation, charters, business agreements, etc.  These things are permanent.  Other permanent items may include meeting minutes of board committees, minutes of evidentiary actions and consents, and records of settlements and releases, for example.   

Beyond foundational documents, there will usually be a general schedule for organization-wide content types – things that any department grapples with (such as working papers, minutes to meetings, confidentiality agreements, personnel records, etc.).   

In addition to this, each department will have it’s own schedule for content that is specific to that department (a Marketing department, for example, would produce a retention schedule for things such as marketing plans, sales reports, forecasts, etc.). 

Taking Action on Content:  Each department’s schedule rolls up to the organization’s main retention policy.  As time goes by, reports are run on a routine basis – usually monthly, and usually by a person in the form of a content/records manager.  The reports identify that month’s actionable content, in various categories.  Action is driven according to content’s age from date of creation, and its having reached the end of the retention period.  After review by appropriate authorities, the content is either archived or destroyed according to instruction in the Schedule. 

Many templates for schedules of content management are available on the web.  Organizations with their own legal resources will generate a good part of their retention schedules and content management policies there.  Here it is important to understand the concepts so that you can begin to plan your system, and deliver proper expectations when evaluating vendors and implementing a solution.

A Retention Review:  Retention drives a large part of your Content Management policy.  All content should have a retention period based on categories of subject material (taxonomy); it is the categories that yield the length of the retention period based on business value of that particular category of content.  A retention period can be extremely short, extremely long, and anything in between, from months to years.  For example, meeting notes’ retention period can be extremely short: the schedule can dictate that once formal meeting minutes are produced, the notes are to be immediately destroyed.  At the other end of the scale are things such as records of incorporation or organization, partnership and membership agreements, etc.  These would be permanent.  Other content can have a conditional retention period: you may choose to retain employee attendance records for a period of four years after the end of employment, for example.

Retention must comply with any laws governing content, and any other regulations.  Also, your organization will be legally obligated to retain all content relevant to pending or reasonably anticipated litigation, investigations and administrative proceedings.  Here, we cannot and do not want to be seen as advocating a system for obfuscating truth or sheltering an organization from consequence to actions of bad faith or bad business.  However, in an age of many frivolous lawsuits, we can see value in reviewing content for potential liability on a proactive basis.  We must recognize the importance in moving and removing “dead-value” content from our active environment. 

We must maintain an efficient, relevant, useful, bank of content, and that is a laudable goal and achievement.  In fact, archiving and destructing content on a disciplined retention schedule has become a duty within the true Business-Technology Weave, and is a crucial process in our overall management of content.


November 28, 2012  1:01 PM

Content: Getting it; using it; etc… Continued

David Scott David Scott Profile: David Scott

We mentioned policy last time:  Without a policy, your means of reporting on content will be less than comprehensive.  Therefore, we must develop a specific Content Management Policy that concentrates on three basic things:

     – Category of content (identifying it according to taxonomy [subject matter]).  This categorization leads to our leverage of content;

     – Retention of content:  Retaining content for a period of time as defined by its category, against a prepared schedule for the retention/disposition of the various categories of content within compliance of laws and any other regulations.  This allows us to ensure that content remains reportable, known, and available during its useful life; and

     – Disposing of it in an efficient manner (removing it from the active business environment at the end of its life, either through deletion or archiving).  This allows us to remove content from the active environment, and helps to prevent the “glut” and liability of unmanaged information.

In this manner we help to secure content through its lifecycle.  In defining the terms of content management, we’ll see that retention drives the policy.

Retention:  Retention is the expected length of time that a piece of content will be in your active business environment.  Retention helps to drive the efficiency that content management delivers.  It sets the periods and dates whereby you can remove data from the active business environment, generally through deletion.  A retention policy is part of your overall content management policy, and ensures that all business records are retained for a period of time that will reasonably assure the availability of those records when needed.  Certain fundamental, vital, records are identified and appropriately safeguarded – their retention period is “permanent.” 

Due to growth in business content and increasingly stringent compliance requirements, Business must recognize that we can’t keep everything forever – much content steadily loses value, ultimately having little or no value.  Here we must recognize that over the course of time, any record that is not required to be maintained for legal or business reasons should be destroyed (or at the very least, removed from the active business environment, by virtue of some kind of archiving).  This removal is necessary to reduce the high cost of storing, indexing, and handling the vast amount of documents and paper that otherwise accumulate.  The retention part of content management ensures the minimization of storage and maintenance costs.  It also helps to increase the efficiency in finding documents, and is an overall lever in building a tight, solid, fit of content to your business-intelligence needs.  It becomes much easier to repurpose and combine data that is  reinforcing to the projects and initiatives that business pursues.  

So, how long do we retain specific information against the measure of time?  For that, we refer to a retention schedule.  Retention schedules indicate every major category of information the organization has, and the schedule for a disposition – such as destruction, or archiving.  For our early understanding now, appreciate that once the schedule exists, we remove specific content according to that defined schedule of retention.  

For example, you may have royalty records, within a comprehensive category.  Your portion of the retention policy, and your chosen, defined, retention period for such records, may look something like this:

VII.  Copyrights, Patents, Royalties, Licensees, Trademarks, Intellectual Property Rights, General Business Relation Agreements:

  • Royalty records:  Life of the patent or trademark, plus 5 years.

There are categories of documents that you would never archive or destroy.  The retention policy accommodates these too – in fact, it protects them.  For example, general corporate records specific to the creation of an organization, and detailing its constitution, partnerships, and qualifications to do business, etc. would be indicated as being ‘Permanent.’

Another example common to all organizations would be your handling of various personnel records.  Your organization may choose to destroy performance appraisals five years after an individual’s departure, for example.  Regardless of commonalities, a retention schedule acts on categories of content that the organization defines – the organization is serving itself.  It sets retention according to its need, and in compliance with all Federal and State laws, and any other applicable regulations. 

Further, our retention schedule can help clean up hardcopy content.  We can help to eliminate the divide of electronic content from its hardcopy counterparts through an understanding of taxonomy (subject matter) – for purpose of categorization.  We can then set an associated schedule for the management of retention according to the content of documents and records – regardless of physical form or media type.  (This also leverages content’s use, removing liabilities of its form and even physical location). 

A table of taxonomies will help your organization and its members to define types of content for categorization.  Your retention schedule then defines the term for which you keep various kinds of content (according to category)  –  starting from an individual piece of content’s original creation date.


November 28, 2012  12:56 PM

Content: Getting it; using it; re-using it; and getting rid of it

David Scott David Scott Profile: David Scott

Beyond mere accountability, the modern and evolving discipline of managed content is more sophisticated and powerful than anything previously established.  We make content searchable and relevant to people in powerful new ways, in support of projects and disciplines within the organization.  We find supporting and illuminating relationships between existing content that were previously hidden because there was no way to find or readily expose these relationships.  We see new clues regarding markets, customers, products, services, trends, activities, and risks.  As importantly, when new content is developed, we automate the assignment of key information fields to it so as to make this new content a part of our leveraged information assets.  Instead of being buried under an explosion of content, we explode content to splay its purpose, relevancy and value.  We then snap content together with other content to form a completed picture.

Imagine this: a scrambled jigsaw puzzle where the pieces reside in various departments, in various physical locations – perhaps all around the world – with individuals and groups working the various pieces in some measure of ignorance for the efforts and work of others.  We now connect all the pieces with an interwoven thread.  The thread guards against loss, and identifies puzzle pieces as relating to each other, among other things.  On demand, an authority pulls a master thread, and all the pieces come together to form as complete a picture as the moment allows: not part of a picture, not a picture with missing pieces, not a picture that requires recreation of missing parts that had already been created – but a 100% collection of parts with corresponding context and fit to the other parts. 

That is a large part of what content management delivers to business.  It can be the assembly of information regarding something in process, such as status that reflects the true moment of progress.  Or, it could be the review of completed project materials and all related effort.  It can be a search for relevant supporting content when mounting a new initiative.  Or, it can just be general research within your assets. 

What’s important to recognize is that you get the complete, best, picture of the situation according to all assets, according to the moment.  When we achieve this system of confidence and control, we gain enormous efficiency and leverage by reusing, re-purposing, and assembling content by optimizing its formerly hidden business value.

Reducing Exposure – Minimizing Liability:  We’re also talking about a comprehensive process that can give a central authority a ready report, at any time, on all content in your organization, according to any criteria by which they query:  What is its subject matter?  Who created it; who has it; who’s been using it?  What is its useful life?  How does it relate to and support other content?  Which members, customers, staff, projects, products, services, regulations, agencies, etc. does this content pertains to?  Where are versions of similar content residing?  Which version is current? 

Accumulation of content contributes to inefficiency.  Multiple versions and drafts of documents can exist in all sorts of locations.  As things get passed around within the organization, and saved in various user and departmental folders, you build all sorts of redundant, near-redundant, and ultimately erroneous data.  There may be content that was created by persons who have left the organization – there may be no one who can readily answer whether the content is correct.  Outdated content, or content whose value is murky, should be weighed against some standard in order to determine its disposability. 

Content management goes beyond eliminating “glut,” and yields the possible exposures (liabilities) that certain content may represent.  For example, your organization may have all manner of outdated business policies, stored in various departments, which may be based on expired outside law and regulation.  You wouldn’t want anyone taking action within such policy that no longer applies.  How can you be sure that everyone is operating on the most recent issue of organizational policies?  Another example may be emerging client relationships:  relationships to you, and their relationships to other agencies.  How do you best disseminate breaking information throughout the organization?  How do you ensure it’s received?  How do you ensure it supplants the old?  How do you remove the old?

Policy:  Content Management vs. Acceptable Use:  Sooner or later, every organization is going to have some measure of policy for content’s  management, and that measure will likely increase as time goes by.  It is important to note here what a Content Management policy is, and what it is not. 

It is for leveraging content, exposing and reducing specific liabilities, and for taking action on content in an administrative sense – reporting on, archiving, and destroying.  It is not the central policy regarding expectations of appropriate use, and regarding actions taken in circumstances of willful abuse of content.  Content management measures certainly do help to identify and expose abuse; however, the definitions of abuse, and measures regarding them, will be contained in the organization’s Acceptable Use Policy. 

Jumping ahead slightly, this Acceptable Use Policy details appropriate use of all business resources, tools, and assets – including information.  Your content management policy can point to the Acceptable Use Policy (or contain extracts from it) regarding things such as the improper access, accumulation, dissemination, removal, and destruction of information.  But again, content management helps us to identify and leverage content toward a positive purpose; helps to limit liability and exposure; and to take administrative action on content.  [We will discuss the Acceptable Use Policy later on this blog – if your organization is lacking such a policy, or needs a better one, stay tuned…]. 

Pairing Process and Policy:  Any policy simply formalizes and documents the understanding of needs, shows the value to be had, and details the mandatory course and standards of actions – the process – in satisfying those needs and requirements.  However, many processes find their way into practice without a formal policy.  Either they don’t require much formal documentation and standards, or they stagger along without them.  But, that cannot be the case with content management.  There really is no middle ground with content:  you either know what you have, or you don’t.  You’re either actively managing your data environment – culling bad and leveraging good – or you’re not. 

More to come…


November 26, 2012  11:03 AM

Content Management, Part II – A growing divide

David Scott David Scott Profile: David Scott

Please see Part I below, or here

Management of content is already well underway in some organizations – with varying degrees of success.  But for most others it is a looming imperative.  If you do not have a method for determining and using your information effectively throughout the organization, you will grow an ever-widening divide between your needs and your reality.  That is, between the sheer necessity for effective use/leverage of business information – and the conditions of inefficiency and diminished returns that accrue with the accumulated glut of unmanaged information.  You must avoid or close that divide now.  Here’s why:

Business is faced with an explosion: it is the exponential growth of content.  What exactly is “content”?  It is any information that your business holds, whether known or unknown, and whether asset or liability.  Whatever electronic information resides in your business systems, on your network, on workstations, in your e-mail system, on backup tapes, on all those scattered discs – is content.  It also includes whatever information exists in the form of hardcopy – printed reports output, written notes, mail you’ve accumulated, etc. – things existing in filing cabinets, bookshelves, and piled on desks.  Whether electronic or hardcopy, content can exist as text, artwork, photos, presentations, etc.  Really anything in your enterprise containing information of any sort, business and non-business related – is content.  That menu from the corner deli is content, and if it’s in someone’s desk drawer, it is part of your organization’s content:  your organization contains it.  The importance of that realization will be made evident, but for now it is imperative that we understand that the organization is liable for all content it harbors.  This is whether it’s harbored by design, or by accident.  This understanding will be necessary as we talk about specific liabilities imposed by certain content.

Content:  A Basic Understanding of Need

Content management can be illuminated further in very practical terms.  Remember the old WYSIWYG (Wiz-ee-wig) acronym?  What You See Is What You Get.  WYSIWYG came about around the time of Windows-based applications, as they replaced DOS-based applications.  At that time, a graphical user interface replaced a text interface.  Software applications delivered to the screen the exact font, formatting, colors, and images that would be produced when you printed your work.  Before WYSIWYG, what you saw on the screen was an approximation of your output – the screen showed, primarily, same-sized text.  Fonts, sizes, graphics, and colors were represented by codes and symbols – you couldn’t confirm what you were getting until you printed, and often what you got was wrong. 

Obviously ‘getting what is wrong’ is inefficient, counterproductive, and frustrating.  This is no less true in the realm of content.  Today’s challenge isn’t aesthetic correctness; it’s content correctness.  Getting what you need.  Content management can be thought of as WYNIWYG (Win-ee-wig): What You Need Is What You Get.  And just as importantly, what you don’t need is what you get rid of

The growth in content is paired with an increasingly important requirement.  Whereas data management, or information management, was once viewed primarily as a concern regarding simple access, delivery, storage, and space – this data is now understood to have value beyond its face and local residency.  It often has continued value beyond any immediate need, and becomes a leveraged asset across the organization as we develop, share, combine and repurpose content.  Data’s content can also pose a potential liability – to the organization and to those with whom we do business.  Content’s liability depends on its nature and, further, its exposure.  

For these reasons there is a whole new realm of standards, within an already established (yet evolving) discipline, in basing the management of information according to content.  This isn’t something that’s never been done before: electronic information on any computer network is managed to some degree according to content.  Things are filed in specific folders, according to subject matter.  Permissions are granted to users based on their need and the data’s nature and sensitivity, and so on.  Hardcopy information too is filed, often locked in filing cabinets; access granted according to the content and who is authorized to access it.  Your HR department’s hardcopy files, for example. 

A Missing Accountability:  But until fairly recently, most organizations had no comprehensive view of their content – those paper and electronic files that comprised the whole of their information.  It’s true that IT had a certain handle on information – regarding disk space utilization, allocation of storage to users, and administering of electronic security.  Too, departments, various bridging teams, and ad hoc groups would have some measure of knowledge regarding their specific content’s information.  But no central authority knew, indeed no one could know, what exactly was on the organization’s computers or in its files in any comprehensive manner. 

There was simply no practice, discipline and allied system for the central control of, knowledge of, and reporting for, content.  An absence of accountability.

Next:  Getting it; Using it; Re-using it; and Getting Rid of It


Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: