All Technology Projects are Data Projects

One of the biggest ideas in Driving Data Projects (the book) is that "all technology projects are data projects." Yet data is still an afterthought in many organizations—even with AI on the horizon (or now, in many firms' backyards).

Author of Data Quality: The Field Guide, Tom Redman, popularized the idea that the most important moments in a piece of data's lifetime are the moment it is created and the moment it is used. These moments often occur outside of IT. The business consumes vast amounts of data, emphasizing the importance of business involvement in data quality management. Those who have provisioned and consumed data know from experience that bad data dies hard. It will get rid of you if you don't get rid of it.

4 Perspectives to drive effective data translation

When driving data projects, you will encounter business stakeholder challenges that often go unspoken. This is not always because people hold back but because they don't fully know how to vocalize their constraints.

If they can't directly address their requirement, chances are we can't either. To hear others' speech, we start by asking questions from different perspectives.

What does it take to become data-driven?

Since most people don’t know a lot about IT organizations or data teams it’s important to understand why moving from ad hoc efforts to a mature approach to driving data projects makes sense. The timing might not be right (now). Becoming data-driven through data as a service requires a serious investment of resources, finances, staff, equipment, services, etc.; scaling efforts will only increase those topline demands. It’s a serious ongoing commitment many organizations find themselves surprised by—even today.

© 2025 DATIVE.WORKS

SEATTLE, WA

Info

Action