Ask HN: What makes a 'good' data strategy?

So I've recently been given the reins of a company-wide 'data strategy' project for the large utility I work for. The goal being to bring us out of the wild west method of governance (dozens of disparate databases) and into a more streamlined, user-friendly system. I am wondering if any of you fine HN folk have gone through similar company-wide changes (either as a project manager or as an end-user), and if so: - What was your experience of the project? - What went well/bad? - What would you have done differently? - Are there any ideas/concepts you would steer away from completely? Thanks in advance for any replies/discussion.