Data governance isn't about data. It's about relationships. Who needs information and who has information? How does decision making relate to information, the systems that manage that information, and processes that create information? My wife doesn't spend her time thinking about databases, analytics, enterprise KPIs, and business performance, but she schools me whenever we talk about the daily challenges that confront me during data governance initiatives. These are some lessons from my marriage that are critical to effective data governance.
1. Why My Wife Loves
Data Governance
Paul Boal – Practice Lead
February 24, 2016
Copyright 2016 Amitech Solutions
2. What is data governance supposed to be about?
Data governance encompasses the people,
processes, and information technology required to
create a consistent and proper handling of an
organization's data across the business enterprise.
https://en.wikipedia.org/wiki/Data_governance
2
3. What is data governance supposed to be about?
The execution and enforcement of authority over
the management of data assets and the
performance of data functions.
http://www.tdan.com/view-articles/5037
3
4. What is data governance supposed to be about?
The decision-making process that prioritizes
investments, allocates resources, and measures
results to ensure that data is managed and
deployed to support business needs.
http://www.b-eye-network.com/view/8393
4
5. What is data governance supposed to be about?
…proper handling of data...
...authority over the management of data...
...decision making process...
5
6. What is data governance
6
supposed to be about?
The work of removing those information barriers
and risks that inhibit an organization’s ability to
effectively achieve its purpose.
Paul Boal, 2016
7. What is data governance
7
supposed to be about?
The work of removing those information barriers
and risks that inhibit an organization’s ability to
effectively achieve its purpose.
Paul Boal, 2016
8. Data Governance
1. Better Decision Making
2. Reduce Friction
3. Protect Stakeholder Needs
4. Adopt Common Approaches
5. Build Repeatable Processes
6. Improve Coordination
7. Ensure Transparency
Marriage
1. Be Clear and Assertive
2. No Relationship is Perfect
3. Respect Both of Your Goals
4. When You Are Married, Act Married
5. Spend Time Together
6. Don’t Leave Things Unsaid
7. Speak Plainly
www.datagovernance.com/goals-and-principles-for-data-governance/
zenhabits.net/eight-keys-to-a-happier-marriage/
www.pastoralcareinc.com/counseling/suggested-goals-for-a-successful-marriage/
9. Data Governance
1. Better Decision Making
2. Reduce Friction
3. Protect Stakeholder Needs
4. Adopt Common Approaches
5. Build Repeatable Processes
6. Improve Coordination
7. Ensure Transparency
Marriage
1. Be Clear and Assertive
2. No Relationship is Perfect
3. Respect Both of Your Goals
4. When You Are Married, Act Married
5. Spend Time Together
6. Don’t Leave Things Unsaid
7. Speak Plainly
www.datagovernance.com/goals-and-principles-for-data-governance/
zenhabits.net/eight-keys-to-a-happier-marriage/
www.pastoralcareinc.com/counseling/suggested-goals-for-a-successful-marriage/
10. Reduce Operational Friction
• Make sure finance, supply chain,
and clinical operations agree on
similar terms and conceptual
models.
• Data quality procedures formally
validate that the data looks the
way it’s supposed to look.
• Master Data Management
streamlines the administration of
core business data.
10
11. No Relationship Is Perfect
• We managed our schedules
differently, with different
expectations – and that lead to
arguments and disappointment.
• We started comparing our
schedules regularly to avoid
miscommunication.
• Now, we use shared calendars to
keep each other informed.
11
12. Adopt Common Approaches to Issues
• Set the expectation that it is
important to clearly define how
information is being used and
how it aligns with business
operations and decision making.
• Invest in processes, tools, and
resources to demonstrate the
importance of data governance.
12
• Lead by example, applying the
principles of data governance to
the implementation of data
governance as well.
• Hold yourself and others
accountable to the principles of
data governance.
13. When You’re Married, Act Married
• What are goals in life?
• What is are our love languages?
• How will we manage our money?
• How do we respond to stress?
• Punctual or consistently late?
• Do we want to have children?
• Is faith important?
• Alone time and togetherness?
13
• How important is education?
• Who do we go to for advice?
• Save or spend?
• Buy things or experiences?
• Do we both work or does one of
us stay home with kids?
• Ties to families of origin?
• Closeness with in-laws?
14. Ensure Transparency
• Create a common glossary of
business terms
• Make metadata easy to access
and discoverable
• Use plain language to
communicate about data
governance
14
• Regularly share information
across the organization about the
work of data governance
• Regularly share information
about the value that is being
created by teams who are
practicing good data governance
• And the penalties experienced
because of poor data governance
15. Speak Plainly
• Tell your partner how you feel
• Be honest with each other
• Communicate using your
partner’s love languages
• Share your needs
• Request changes in behavior
• Schedule regular time to talk
15
16. Commitment
Data governance is not a project
or a program or an isolated
capability.
Data governance is part of how an
organization chooses to conduct
operations and decision making on
a day to day basis.
Commitment
Marriage does not end with the
vows in a wedding ceremony, a
reception, and a honeymoon.
Marriage requires the ongoing
daily choice of a couple to remain
committed to one another.
17. Key Lessons
• Data governance has to be perceived as something that drives the
achievement of business objectives.
• Successful data governance includes cultural change and ongoing
relationship development.
• To sustain results, data governance requires not just the one-time
effort of a data governance team, but for everyone to make the daily
choice to remain committed to its purpose.
• Data governance has to be perceived as something that drives the
achievement of business objectives.
17
18. Actions Items
• Write down how your current or planned data governance initiatives are
supporting the organization’s goals.
• Is that how the broader organization sees it?
• Change your messaging to emphasize this purpose.
• Write down what else your data governance initiatives are currently spending their
time doing.
• Is it really necessary?
• Find a way to deemphasize or stop doing things that don’t fit this purpose.
• Consider how else data governance could make a direct impact on the
organization’s goals.
• Prioritize these items to the top of your list.
18
19. Resources
• Non-Invasive Data Governance book by Robert S. Seiner
• Data Governance book by John Ladley
• Data Stewardship book by David Plotkin
• Agile / Lean Data Governance Best Practices essay from Scott W Ambler
• The Speed of Trust book by Steven M.R. Covey
• Start with Why book by Simon Sinek
• The Phoenix Project book by Gene Kim and Kevin Behr
• AmitechSolutions.com for other data and analytics resources
• Check out http://www.aamft.org to improve your marriage.
19
The Data Governance Institute does have a good description of what some of the outcomes for a successful data governance program should be.
And I pulled out some key points from various resources about what some of the habits in a successful marriage are.