Book Image

Data Governance Handbook

By : Wendy S. Batchelder
Book Image

Data Governance Handbook

By: Wendy S. Batchelder

Overview of this book

2.5 quintillion bytes! This is the amount of data being generated every single day across the globe. As this number continues to grow, understanding and managing data becomes more complex. Data professionals know that it’s their responsibility to navigate this complexity and ensure effective governance, empowering businesses with the right data, at the right time, and with the right controls. If you are a data professional, this book will equip you with valuable guidance to conquer data governance complexities with ease. Written by a three-time chief data officer in global Fortune 500 companies, the Data Governance Handbook is an exhaustive guide to understanding data governance, its key components, and how to successfully position solutions in a way that translates into tangible business outcomes. By the end, you’ll be able to successfully pitch and gain support for your data governance program, demonstrating tangible outcomes that resonate with key stakeholders.
Table of Contents (24 chapters)
1
Part 1:Designing the Path to Trusted Data
7
Part 2:Data Governance Capabilities Deep Dive
14
Part 3:Building Trust through Value-Based Delivery
20
Part 4:Case Study

Simple and strong core messaging

As you embark on a formal data governance transformation, it is of utmost importance that you make your messaging simple and understandable to the masses. One great way to do this is to think about what life will be like once you’ve delivered. A great way to do this is to start by outlining your as is versus your to be state. I’ve seen this work well in a number of companies and as a clear way to depict the variance between before and after. This should be done in several ways, but first and foremost, it should be done from a business perspective.

For example, if it takes 18 days to complete a quote for a customer in the current state but, in the future state, we expect it to only take 8 hours, you should define this for the user. Show them and tell them how you’re going to get there:

  • Are you going to implement a new system?
  • Are you going to automate processes?
  • Are you going to remove redundant processes?
  • ...