# 20241217 - Long-term Data topics with Rich

We sit to discuss on 2024-12-17.

# Recap on what the Data team does

What we should do:

- Supervise data across the org: catalogue all the data and data products we have
- Build and own company wide Data infrastructure
- Build and own stable, company wide reports, dashboards, etc.
- Provide brain power for complex analysis
- Build Data Literacy across the company

What we shouldn’t do:

- Own absolutely every little report that exists in Superhog (and become a bottleneck in doing so)
- Act as a poorly designed patch/release-valve on other product shortcomings
- Miraculously overcome lack of data and poor-quality data

# Recap on our capabilities

[Check this whiteboard](https://guardhog-my.sharepoint.com/:wb:/g/personal/pablo_martin_superhog_com/ERy6GpPt0S9Ht_vhl6jF8EsBWE9fzDX8DIv7vQv3whNo7A?e=pHw8C9).

# Long-term topics

Topics:

- Grow team to sufficient size to increase bus factor
- Implant analyst roles within business functions
- Long-term capabilities that we lack:
    - Enable application runtimes to access DWH data
    - Embedding data products within customer-facing applications
    - Advanced orchestration of workloads
    - Automated, one off, file based reports to internal and external users
    - Full end-to-end lineage from data sources to data products + tracking of data products usage
- Improve relationship with stakeholders:
    - Mature data contracts approach with upstream teams
    - Mature tracking and communication with end-consumers
    - Improve priorities setting with the business
- Keep on improving analyst experience to maximize productivity/avoid going into maintenance hell
- Transfer out accumulated responsibilities that make no sense (invoicing and other shadow-product-engineering areas)

Stuff to do to achieve the above:

- Hire a DE
- Migrate from PBI into a better tool
- Carefully add new tooling to the Data Platform
- Build SOP with other teams for upstream/downstream relationships