<!-- Team charter · from Chapter 36 of The Product 360 Handbook -->

# Team charter · [Team name] · v[n] · [Date]

**Review date:** [3 to 6 months out]   **Charter owner:** [PM or lead]

## Mission
[One sentence: why this team exists.]

## Customers and problems we own
-
-

## Outcomes and metrics
| Outcome | Metric | Baseline today | Target | By when |
|---|---|---|---|---|
| | | | | |

Hard constraints (must never be violated): [for example, zero unapproved actions]

## Out of scope
[What this team does not own, and who does.]

## Members and roles
| Name | Role (PM, design, tech lead, engineering, applied AI, PMM) | Accountable for | Top 3 to 5 responsibilities |
|---|---|---|---|
| | | | |

Overlapping responsibilities and their named primary owner:

## Decision rights
| Decision type | Who decides | Must agree | Consulted |
|---|---|---|---|
| Roadmap priorities within our area | | | |
| Shipping to general availability | | | |
| Customer-specific requests | | | |
| [Other recurring decision] | | | |

## Key stakeholders and engagement
| Stakeholder | What they need from us | Cadence and channel |
|---|---|---|
| | | |

## Working agreements
- Core hours and time zones:
- Channels (urgent, async, decisions):
- Meetings (purpose, cadence, sync or async):
- How we give and receive feedback:
- How we raise bad news (eval regressions, incidents, slipped dates):

## Escalation path
When we can't agree: [step 1], then [step 2], decided by [role] within [time]. Decisions shared via [channel] and logged in [location].

## Interfaces and dependencies
| Team or system | What we depend on, or what depends on us | Contact |
|---|---|---|
| | | |