Before I can begin to boot-strap up a Data Governance process (even a low-impact one), I need to help my organization change realize the old pattern of:
- Business wants an Information Processing function
- IT creates/builds/operates the Information Processing System based on that need
- No one addresses the Data Governance/Management/Quality/Security aspects of the solution
- Start the process again, and again, and again...
I'm considering creating a set of template documents that start with a framework of what the long-term responsibilities of the Business, IT Architecture, IT Operations, Info Sec, Data Privacy and Records Retention, Project Management Office and other functional areas of the organization are signing up for starting at the point that a record is captured at the point the Business declares their need.
I am thinking that this/these documents would start with some loose framework of responsibilities - something not too burdensome for a Concept level effort to produce. Signatures of the representatives from each area would be needed to show that the various teams all had some some exposure to these listings.
As the inevitable project proposal/funding approval process grinds it's way along, at various milestones the participants in the process would need to begin to flesh out those documents. Parts of the documentation would include the need to identify critical data elements, and establish business area data stewardship and long term responsibilities.
The idea would be to build awareness of the repercussions of asking for resources from the organization to build systems that eventually have a far greater impact that the person who originally submitted the request.
Any thoughts on this idea? I'd like to know if anyone has implemented something like this, and see if there are any known document templates along these lines.