<!-- Team staffing plan · from Chapter 04 of The Product 360 Handbook -->

# Team staffing plan · [Initiative] · [Date]

**Owner:** [PM]   **Approver:** [Leader]   **Review date:** [Date]

## Outcome and appetite
- Outcome the team owns: [metric and target]
- Appetite: [weeks or quarters] for [scope boundary]

## Team type
Stream-aligned / Platform / Enabling / Complicated subsystem. Why:

## Roles
| Role | Named person | Allocation (%) | Responsibilities | Backfill or gap |
|---|---|---|---|---|
| Product manager | | | | |
| Product designer | | | | |
| Tech lead | | | | |
| Engineers | | | | |
| Applied AI engineer (AI features) | | | | |
| Forward-deployed engineer (if used) | | | | |
| Product marketing | | | | |
| Other (data, security, docs) | | | | |

## Interaction modes with neighboring teams
| Team | Mode now (collaboration / X-as-a-Service / facilitating) | Until | Target mode | Interface or agreement |
|---|---|---|---|---|
| | | | | |

## Capacity
| | Engineer-weeks per quarter |
|---|---|
| Gross (people × weeks × allocation) | |
| Less on-call | |
| Less maintenance and support | |
| Less migrations and other keep-the-lights-on work | |
| **Net capacity for this initiative** | |

Net capacity versus appetite: [fits / doesn't fit, by how much]

## Binding constraint
[The one role or team that limits throughput, and the decision needed: add, borrow, sequence or cut.]

## Dependencies and risks
-

## Asks
-