Chapter 12. Measuring the Impact of Data Contracts
Measurement isn’t just a reporting function; it’s a mechanism for supporting the organizational change we outlined in Chapter 11, the culture changes we discussed in Chapter 10, and the perception changes we highlighted in Chapter 9. In addition, leaders understand that metrics aren’t created in a vacuum, and thus require thoughtful planning and communication. Specifically, leaders recognize that people within the business need to accept their metrics’ validity and agree on their meaning.
Throughout this chapter, we’ll explore how you can complement the qualitative results surfaced in previous data contract implementations with quantitative measurements. In addition, we will detail how you can effectively communicate these numbers and ensure the wider business understands the positive impact of shift left data practices and data contracts.
What’s Worth Measuring?
With respect to data contracts, we group measurements into the following three categories:
- Technical
-
Metrics that are indicative of the coverage, reliability, and functionality of any data contract implementation itself (e.g., test time length, number of assets covered, etc.)
- Team
-
Operational metrics tied to efficiency, behavior, or workload of teams related to data products and/or implemented data contracts
- Business
-
Bottom-line metrics that directly demonstrate the business value of one’s data contract implementation
As a starting point, Figure 12-1 outlines ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access