Team Operating Plan

Written during Phase 4 (Days 61-90). Socialized with peers and manager before announcing to the team. Kept to two pages. The "what we're stopping" section is not optional — it forces prioritization to be honest.

# [Team Name] Operating Plan — [Quarter or half]

## Mission
[One sentence. Why this team exists. What breaks if we don't do our job. If you can't say it without corporate language, you don't understand it yet.]

## How we ladder up
[One or two sentences: how this team's work connects to company priorities. Cite the specific goal.]

## Priorities this period
1. **[Priority 1]** — Why: [context]. Success: [what we'll see]. Owner: [name].
2. **[Priority 2]** — Why: [context]. Success: [what we'll see]. Owner: [name].
3. **[Priority 3]** — Why: [context]. Success: [what we'll see]. Owner: [name].

*(Three is a soft cap. Four means you haven't decided.)*

## What we're stopping
- [Thing we used to do that we're not doing anymore, and why]
- 
- 

*(If this list is empty, you haven't actually prioritized — you've just added.)*

## How we work
- **Meeting cadence:** [standups, planning, retros, all-hands]
- **Decision-making:** [who decides what, and how disagreement resolves]
- **Communication:** [where updates live, response time norms]
- **On-call:** [rotation and expectations]

## Success criteria
[What we'll be able to point to at the end of the period to say this worked. Ideally measurable, but honest-and-qualitative beats fake-and-quantitative.]

## Risks
- 
- 

## Open questions
-