less than 1 minute read

https://docs.google.com/presentation/d/1NrqG1DPxW4NaUVN9y49gZH5P4jQ5-cLuc5qdVk-ocs4/edit#slide=id.g23972ffdc81_0_752

Businesses are a socio-technical system

Organizations are composed of the connections between humans in your organization chart. We often design business systems with a primary goal of facilitating those connections.

What if we’re doing it backwards? Instead of designing for what people already have in common, design for what you want them to have in common

Aligning data insights with stakeholder requests

  • Removing barriers between analytics teams and stakeholders (e.g. CEO)
  • Align on data asks in real-time

Solving this problem with semantic layer

  1. Represent your business entity layer
  2. Define your most important metrics
  3. Deployment, documentation, and versioning
  4. Configure Data Access and Contracts
    • Questions to ask
      • Who needs to be able to modify the underlying data powering your metrics?
      • Is access to sensitive data required to correctly validate the accuracy of the metric? (e.g. DEI metrics)
      • Who should have this access?
      • What APIs do I want to provide other teams to enable them to use data I built, if at all?