Page 172 -
P. 172

Overview    151




               Tips for Success

               As we said earlier, data governance generates a lot of resistance, and you cannot afford to ignore it.
               Resistance usually occurs across a continuum, from visible support and advocacy to overt hostility.
               Either end of the spectrum is easy to spot, but it is the passive resisters to worry about because they do
               not speak up and are very hard to spot. Make sure your plan contains the tasks and the time to
               understand and address all the types of resistance you will encounter. Your DG program will definitely
               benefit from the time spent.
                  Also, make sure your CM plan gets integrated into the overall DG roadmap effort. These tasks do
               not stand alone, and it is essential that they be coordinated with the overall effort.

               Activity: Define DG Organization Rollout


               It is obvious that you should not announce to everyone, “DG is here!” and then wait for DG to happen.
               Very often, it is too easy to develop a rollout strategy that does just that. No matter what good
               intentions are held, the rollout process for DG can very easily be perceived as force-feeding the
               organization. Remember, you need to govern something and it is perfectly fine to implement in small
               pieces, by project, or by program. This does not mean you have separate DG efforts for every program.
               You will need to coordinate among the projects to ensure the enterprise aspect of DG. The rollout of
               the DG framework entails a little bit of planning.
                  One key aspect of a rollout strategy is to get the governance structure busy doing some kind of DG
               activity. Too often, the stakeholders are sent to training and then told to wait for the first opportunity to
               govern. This activity, therefore, not only defines the incremental events that deploy DG, but also
               specifies what is happening in these events, as well as fine-tuning the structure to match the rollout
               approach.
               Activity Summary Table




                               Objective    Define an incremental process to deploy DG.
                               Purpose      Ensure DG is absorbed into the organization in digestible
                                            portions.
                               Inputs       DG operating framework
                               Tasks        1. Develop DG management requirements.
                                            2. Revise DG charter/mission, if necessary.
                                            3. Develop/refine DG organization positions.
                                            4. Identify immediate governing tasks.
                                            5. Define DG rollout schedule road map.
                               Techniques   Project planning and coordination
                               Tools        Excel, project management
                               Outputs      1. Day-to-day DG management
                                            2. Revised DG charters
                                            3. Revised DG organization
                                            4. DG rollout plan
                                            5. Road map
               FIGURE 12-8
               Activity Summary Table.
   167   168   169   170   171   172   173   174   175   176   177