Report / BI builder × model
Anyone who builds reports must understand and help shape the semantic model — otherwise shadow logic and KPI drift follow.
Data Steward
Focus
Data Steward
Keeps meanings, quality rules, and use workable in the domain — the operational engine behind catalog, contracts, and DQ. Escalates to the owner; does not alone decide purpose and access.
Decision boundaries
Owns
- Term and field definitions in the domain
- DQ rules, gates, and issue triage
- Catalog care and contract reviews with the architect
- Escalation to the owner when purpose or access is unclear
Does not
- Purpose binding and access approvals (owner)
- Product roadmap and prioritization (product owner)
- Platform runtime and rights enforcement (custodian)
- Setting grain and interface standards alone (architect)
Typical tasks
- Keep definitions and synonyms current in the catalog Domain catalog / glossary
- Operate DQ gates and exception lists Pipeline / DQ dashboard
- Review contract changes with the architect Data contract review
- Collect and prioritize consumer gaps Intake / stewardship cadence
- Escalate access conflicts to the owner Approval cadence
Works with
Bridge patterns
See all bridge profiles on the Roles hub
Steward × architect
Domain definitions plus grain/contract questions in one person — works when scope is small and the domain is clear.
Spans
Recommended learning paths
- Governance foundations Shared language and decision rights for stewardship path
- DQ with dbt Anchor DQ rules operationally in dbt path
- Trusted metrics Write KPI contracts with owner and architect path
- Metadata operating model Catalog and metadata as an operating mandate path
- Find, do not expose Separate visibility layers: find the work without exposing the person path
Recommended tools
Stories
Glossary
Short definition for shared language — not the starting point for this role.