by Angela Guess
Dylan Jones recently clarified the difference between a data governance framework and a data governance strategy. He defines a framework as “(1) A skeletal structure designed to support or enclose something. (2) A frame or structure composed of parts fitted and joined together.” He defines a strategy as “(1) A method or plan chosen to bring about a desired future, such as achievement of a goal or solution to a problem. (2) The art and science of planning and marshaling resources for their most efficient and effective use. The term is derived from the Greek word for generalship or leading an army.” Dylan Jones recently clarified the difference between a data governance framework and a data governance strategy.
Jones continues, “I’ve recently read a lot of local government reports on data quality frameworks and policies which are a cause for concern because they focus far too much on the ‘skeleton’ at the expense of the ‘desired future.’ There seems to be a tendency for frameworks to be circulated, adapted slightly and then passed off as the corporate strategy for data quality. Another area this is commonplace is in data migration. I often get asked for template project plans and data migration frameworks. I supply what I have but with the caveat that the best framework in the world won’t tell you what your strategy is, only you can figure that out.”
He adds, “Take a look at your own data quality or data migration strategy – was it based on an existing framework? Does it have clear goals and a vision of a ‘desired future’? Or is it made up various components that are all best-practice and well presented but ultimately irrelevant unless they are pointing in a specific direction that is meaningful to your situation? What do you think, have you seen this issue out in the field recently?”
