People expect a new tool to solve their problems. But sometimes, the real problem isn't the tool. It's the data behind it. I'm still working on our data strategy. One principle is already clear to me: Data by Design.
Every new tool or system creates or collects data. People who work with the system usually see only the interface, not the database behind it.
Whether we build or buy a solution, sooner or later, someone will want a report from it. And that's often when the data team hears about the system for the first time.
A few questions worth asking before decisions are made:
- What data will the system collect?
- Where will the data be stored? On premise or on cloud?
- Who owns and maintains it?
- How can we access it? Is there an API? Is export data free?
- Does it fit the definitions we already use?
Data shouldn't be an afterthought. It should be part of the design from day one.
When does your data team hear about a new system: at the requirements stage, or when someone asks for the first report?
This is part of my "100 Days of Year One" series. Follow along as I share what I've learned in my first year as Head of Data and Cloud.