<!-- Dedicated team charter · from Chapter 23 of The Product 360 Handbook -->

# Dedicated team charter · [Bet name] · [Date]

**Single-threaded leader:** [Name, and the scope they gave up]
**Executive champion:** [Name]   **Form:** Structural (separate team) / Contextual (protected time inside a team)
**Why this form:** [Distance from the core: buyer, price, channel, risk profile]

## Explore and exploit alignment
| Element | Core (performance engine) | This bet (dedicated team) |
|---|---|---|
| Strategic intent | | |
| Critical tasks | | |
| People and skills | | |
| Structure and decision rights | | |
| Metrics and rewards | | |
| Culture and norms | | |
| Funding | Annual plan | Tranches at evidence milestones |

## Split of work
| Task (build to scale) | Fits core routine? | Owner: dedicated team or shared staff | Named person | Conflict to manage |
|---|---|---|---|---|
| Build | | | | |
| Evals and quality | | | | |
| Pricing and billing | | | | |
| Selling | | | | |
| Support and escalation | | | | |
| Security and risk review | | | | |
| Operations and on-call | | | | |
| Release and deployment | | | | |

## Supporting policies
| Policy area | Current rule | Exception or new rule | Approved by | Ends when |
|---|---|---|---|---|

## Reviews
Learning review: [cadence, forum, separate from performance reviews]
Disputes with the core are settled by: [champion or senior team]