# Product Operations Decision-Flow Charter

**Use:** define a Product Operations function by the decisions it enables, not by a list of tools or ceremonies. This is a Strategica template, not a universal organisation design.

| Decision flow | Decision owner | Failure mode today | Product Ops contribution | Evidence/latency measure | Boundary and escalation |
| --- | --- | --- | --- | --- | --- |
| Customer evidence | Product leader / product manager |  |  |  |  |
| Prioritisation | Product leader / product manager |  |  |  |  |
| Planning and roadmap | Product leader / product manager |  |  |  |  |
| Experiment design and rollout | Product manager / experiment owner |  |  |  |  |
| Outcome learning | Product leader / product manager |  |  |  |  |

## Charter test

For each proposed Product Ops activity, answer:

1. Which product decision becomes more evidence-based, timely, explainable, or reusable?
2. What work, ambiguity, or rework disappears for product teams?
3. Who retains the authority to decide?
4. What evidence would show that the intervention helped rather than simply increased compliance?
5. Which adjacent function already owns this responsibility, and what interface—not duplication—is needed?

Do not use template completion, meeting attendance, tool adoption, or report volume as the only success measure. They can be useful operating signals, but need an explicit link to a decision-flow improvement.