meetings It’s built by people who don’t deliver Definitions are stupid; everyone disagrees Governance creates gatekeepers Governance is for compliance, not builders I’m a developer. I don’t have time for this Governance is a business thing, not an IT thing We are agile so we don’t do governance I’m a DBA. I don’t have time for this It’s documentation
stuff without breaking things? Can I access it without drama? Can I trust it without a meeting? Can I use it without ROI? Is the data good enough? Where do I get help? (c) InfoAdvisors 2026. All rights reserved
Frees up time they don’t want to spend explaining things Enables scale-up of teams Increased collaboration Faster requirements and implementations Drill down for the win (c) InfoAdvisors 2026. All rights reserved
Is it confidential? Does it need special controls? Will I know how to figure that out? Are classification policies enforceable? How do I know what to mask, encrypt, or restrict? What if I have data lifecycle requirements?
it Safer, Faster, and Less Annoying 1. Inventory your data, prioritizing and triaging Current Projects? Most painful ones? Compliance? Critical data? 2 . Set Stewards, Owners, and Experts first Before rules, policies, and glossaries
Safer, Faster, and Less Annoying 3. Target useful over complete metadata •Owners/Stewards •Detailed scans •Don’t skip glossaries 4. Do analytics on your governing, but start with it just as a baseline 5. Plan to automate much of this going forward, but not now (c) InfoAdvisors 2026. All rights reserved
it Safer, Faster, and Less Annoying 6. Get metadata into the hands, minds, and keyboards of engineering and development. Plus everyone else. Visibility failures damage trust, a lot Reduce guesswork Reduce rework Not just catalogs and glossaries Get metadata to where they work Discovery before creation
Safer, Faster, and Less Annoying 7. Overcommunicate Data Quality as just another measure, not a shame game Information about data, not blockages Not all data is the same, so there is flexibility on quality pillars Not all quality pillars need to be applied to all data Triple-check your quality rules (c) InfoAdvisors 2026. All rights reserved
Safer, Faster, and Less Annoying 8. Prioritize lineage as a rework reduction, not just documentation Scan first Integrate/upload Manually build it Will this break something? Is it Friday? What other things depend on this table? (c) InfoAdvisors 2026. All rights reserved
SiteGround - Reliable hosting with speed, security, and support you can count on.
datachick
techniczna
karad
shoki_hata
akiratameto
oikon48
uhyo
p0n
hirosatogamo
kotaoue
shotashiratori
kazzpapa3
hootaki
reverentgeek
sachag
chrisshort
ipullrank
aleyda
honzajavorek
cassininazir
rocio
inesmontani
khoart
marktimemedia
nonsquared
