submit to reddit

About Lowell Fryman, CBIP-CDMP

Lowell is responsible for directing thought leadership and advisory services in the Customer Success practice of Collibra. He has been a practitioner in the data management industry for three decades and is recognized as a leader in data governance, analytics and data quality having hands-on experience with implementations across most industries. Lowell is a co-author of the book “Business Metadata; Capturing Enterprise Knowledge”. Lowell is a past adjunct professor at Daniels College of Business, Denver University, a past President and current VP of Education for DAMA-I Rocky Mountain Chapter (RMC), a DAMA-I Charter member and member of the Data Governance Professionals Organization. He is also an author and reviewer on the DAMA-I Data Management Book of Knowledge (DMBOK). He focuses on practical data governance practices and has trained thousands of professionals in data governance, data warehousing, data management and data quality techniques. You can read his Data Governance Blogs at,

  • Satoshi Mizutani

    The eight steps are practical, very clear and helpful.
    Now that a personal data is owned by each indivitual, we have to redefine the word “owner”.
    The meaning of “owner” has multiple meanings. “Business owner” or “accountable party” are good comprimisation for practitioners, but we have to find another word for traditional data owners within an enterprise.

  • BigJ62

    Rather than focus on individual data items, why not begin with entities that meet the criteria of being an individual subject such as Customer, Patient or Prospect. Then Identify items representing attributes of that person entity. Then identify related entities that ‘belong’ to that person, or could be used to identify that person (even if names were obfuscated) such as Address, Account, Card. What about Order or Transaction entities? Could these be used to identify the person even if the root person record is obfuscated – especially with those BI Data Warehouses and Big Data pits you spent years and lots of money filling up with all that useful data…
    You will find the implications of GDPR have an impact on more entities and therefore tables in your databases than you might at first imagine. Some of those data assets you’ve accumulated may quickly become liabilities if mis-managed!
    One last tip. If you don’t know how to model object lifecycles using State Machines, look into them – they’re very helpful in this context.

We use technologies such as cookies to understand how you use our site and to provide a better user experience. This includes personalizing content, using analytics and improving site operations. We may share your information about your use of our site with third parties in accordance with our Privacy Policy. You can change your cookie settings as described here at any time, but parts of our site may not function correctly without them. By continuing to use our site, you agree that we can save cookies on your device, unless you have disabled cookies.
I Accept