![rw-book-cover](https://hex.tech/static/781ee676fc2a7e85ddc09e992a0cdeb4/47498/data-roi.jpg) ## Metadata - Author: [[barry-mccardel|Barry Mccardel]] - Full Title:: Don’t Tell Your Data Team’s ROI Story - Category:: #🗞️Articles - Document Tags:: [[Measuring a data team impact|Measuring A Data Team Impact]] - URL:: https://hex.tech/blog/data-team-roi/ - Finished date:: [[2023-04-17]] ## Highlights > for most teams, their impact is created indirectly: they are partners, acting in support of functions like Marketing, Operations, or Engineering to affect company performance ([View Highlight](https://read.readwise.io/read/01gy60p913c6zq3jn4hb2xxh2e)) > even harder for infrastructure investments: how do you quantify the impact of a better schema, or a more reliable pipeline? ([View Highlight](https://read.readwise.io/read/01gy60pqepjg9ptbwkdnntkkz6)) > If your Data team is truly providing value, the leaders of other functions should be lining up to sing your song. ([View Highlight](https://read.readwise.io/read/01gy60qqfzbgg42ckbz10zq7vr)) > Infrastructure-level objectives — like implementing a new data warehouse — can live separately, but should still have explicit callouts for how those investments are supporting the higher-level objectives. ([View Highlight](https://read.readwise.io/read/01gy60s33byz0bp3n7snk3860v))