Every data governance practitioner says the same thing when building foundations: link to business outcomes and listen to what customers ask for. Don't build a catalog just because it's governance 101. If analysts struggle finding data and that's what customers demand, then build the catalog first — but let customer demand guide the roadmap, not data governance textbooks.
Key takeaways:
Starting with foundations means linking governance outcomes directly to business outcomes, not following best practices blindly
Don't do data for the sake of data — build what solves real customer pain, not what governance playbooks prescribe
If analysts struggle finding data and customers demand discoverability, then build the catalog first as your foundation
Customer demand should guide your roadmap at every stage, not theoretical governance maturity models
Early implementation success comes from listening to users and solving their actual problems, not checking governance boxes
