program during this phase is to raise awareness of the policy change and offer guidance on how to successfully implement the policy in a manner that will meet compliance evaluation standards.


Define the scope of data and/or IT systems that will be subject to


compliance The compliance program should also clearly articulate the scope of what it will evaluate. Put simply, it should define what is in scope versus what is out of scope. Defining the scope will depend on the specific aspect of data management being evaluated, but defining the scope


www.tomorrowsfm.com


based on data or IT systems is often a good place to start. Many data governance programs early in their maturity want to govern all data, but that is generally impossible and impractical. Data can include a spreadsheet on someone’s local hard drive, and typically it is not valuable or cost-effective to manage that level of data in an enterprise program. Data that is critical to the business is a good starting place for scope.


For instance, customer data such as grant recipients or account holders is always a critical asset to running a program, and managing that data to improve quality, availability, and other aspects of data is valuable. In the first year, a compliance program could focus on customer


TOMORROW’S FM | 35


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60