Throwing Technology At Information Governance Efforts
Information Governance stands atop many other disciplines as a "super-discipline" or an "umbrella concept" depending upon who you ask. As such, it fulfills, primarily, a strategic role within organizations. That strategic role is often one that didn't exist previously or existed in "pockets" in an organization (think legal departments and Records Management departments).
Since Information Governance stands atop many other disciplines, it stands to reason that a large part of what comprises "Information Governance" is, in fact, strategic. Coordination, policy development, process creation or improvement, etc. are all typical leading activities in Information Governance. Note that none of those activities are technology implementation.
No, technology is simply an enabler in Information Governance, not a leader. Whereas previous Information related efforts, Document Management, Enterprise Content Management, and Information Management often led with technology (despite warnings from leaders like Sanooj Kutty, Laurence Hart, Steve Weissman, and others), Information Governance leads with thinking and discussion; strategy.
This is why some of the old leaders of past information initiatives sometimes struggle with Information Governance, strategy leads. You simply can't utilize the same techniques of throwing technology at the problem that many information leaders have relied on in the past.
While technology doesn't lead in Information Governance, it does hold a significant supporting role. Technology must enable Information Governance.
Enabling Information Governance means bolstering the business requirements that lead to Information Governance, which means that no technology will be successful unless there is already an understanding of:
- The Business Problems
- The Business Requirements
- The Strategy
Far too often, one or more of these pieces is missing or incomplete, the technology is implemented, and it is only then that there is a realization that something won't work as desired.
Rather than work around system limitations, work around the business problems, the business requirements, and the strategy up front and save many headaches later.