data-team-operating-model
Installation
SKILL.md
Product Squad Structure
Data products need four co-equal roles, not a hierarchy:
| Role | Owns | Veto Authority |
|---|---|---|
| Product Manager | Strategy, prioritization, stakeholder alignment | Business viability |
| Tech Lead | Architecture, infrastructure, technical feasibility | Technical direction |
| Design Lead | UX, usability, information design | User experience |
| Data Lead | Data quality, ethics, data engineering | Ethical concerns |
CRITICAL: The Data Lead is co-equal to the PM, not subordinate. They have veto authority on ethical data concerns. This is what distinguishes data product teams from software product teams.
Shape Up for Data Teams
Six-week cycles replace two-week sprints. Data work has more unknowns than typical software — discovery doesn't stop when building starts.
Cycle structure:
- 2 weeks shaping (before the cycle): PM and Data Lead define the problem, set the appetite
Related skills