Gimmal Blog

Read the latest thought leadership and industry news from the experts at Gimmal!

All Posts

Transparent Content Management in a Multi-Repository World

Content is everywhere, and its volume and variety continue to expand. Most experts agree that the data will double every two years at least, a 50-fold growth from 2010 to 2020.

A single-repository ECM approach is no longer viable for many organizations, and traditional ECMs continue to age. A forward-looking perspective must seek ways to standardize information governance between platforms instead of gather information under one platform.

Where are we now?

Every organization produces information that is critical to the daily operations of its business. The information produced resides in many formats, is stored in many locations, and has many different uses, all with varying levels of value and requirements that dictate its creation, use, and ultimately, destruction.

While most organizations recognize that information plays a critical role in their business such as making strategic decisions, protecting their business in litigation, processing transactions, documenting activities, and simply being necessary for its employees to perform their daily workload, most organizations struggle with how to effectively govern this information.

While some organizations have intricate policies in place surrounding their information, there are still many that may not fully grasp what it means for information to be governed.

A quote from our own Mike Alsup from his recent CMSwire article sums it up:

The tidal wave of information is accelerating. Companies enlist multiple ECM repositories to handle this, creating further problems rather than solutions. Nothing can be found, managed or governed.

Where are we going?

In order to reap the benefits of information governance across an entire organization, a new approach must be taken: a holistic approach. This means that, when it comes to information governance, the business must be viewed as a whole, which is what an organization should be doing in all of its facets.

Records and information not only live in ECM repositories, they live on file shares, in email servers, tucked into file cabinets and file rooms, on cloud‐based systems, social media, communication platforms, and in line-of-business (LOB) systems. Knowing where the information lives is the first step to proficiently governing any organization’s information assets.

With industry experts projecting that content doubles every two years, it is evident that the sooner an organization gets a handle on its information governance practices, the easier it will be to implement an overarching solution which optimizes and protects the organization to the world’s ever-increasing and demanding needs.

Again, a great quote from Mike Alsup helps to tell this story:

The question will become “Why don’t you move everything or leave everything in Office 365 or Google or AWS?”

I predict the concept of organizations taking content out of Office 365, especially email, in order to govern it will cease to be a useful concept in 2017. Leave the repository driving to us.

How do we get there?

After establishing policies, and coming to the realization that the information governance practice cannot be implemented without the proper tools in place to support it, the organization will then need to put a system in place to effectively govern its information.

The system will need to secure the content, restrict its usage to only those who should have access, and automate the retention and disposition of information. However, taking a holistic approach results in a lot of disparate systems that must be managed.

Because of this, the most important piece of the puzzle will be the transparency we discussed last week. Instead of relying on siloed systems that lock data down, there must be a move towards open platforms capable of handling all types of data across the enterprise.

This is admittedly a radical departure of thought for many in the ECM industry. However, given all that we have discussed, it is clear a change is ahead and the entire industry must be prepared.


New Call-to-action


Related Posts

3 Tips to Ensure KORA Compliance

There has been a spotlight on the Kansas Open Records Act (KORA) in the media lately, largely due to recent violations. Under KORA, any individual can request public records from government bodies. If all requested records are not provided within in a specific timeframe, these organizations are subject to significant repercussions. This is merely one example of a ‘sunshine law’. The purpose of sunshine laws is to provide transparency into government agencies by giving the public access to local government proceedings.

Creating a Retention Schedule that Works

Creating a usable, automated, and simple file plan is an important part of ensuring records are managed in a consistent manner and that you are protected from legal risks, such as failure to disclose information during a discovery proceeding or the unauthorized leakage of information. The first step in the process is creating a retention schedule, which outlines how long records are kept in accordance with the organization’s obligations and the law.

How to Manage Your Sprawling Content

Sprawling content, the spread of content across multiple repositories, has been a thorn in the side of records managers since the dawn of document management. Consolidation of repositories, which began in the early 2000s, at first looked to be the solution. However, it ended up highlighting the problems of content sprawl due to the high costs of consolidation as well as need for records managers to manage multiple file plans. Federated records management offers a solution to these problems but doesn’t offer the same locked-down approach with regards to regulation that consolidation can. Consolidation of repositories and federated records management both have pros and cons and, depending on your organization’s content management processes and repositories, one can be more beneficial than the other in the long term.