# Head of Product Operating Review

## When to use

Use this template when leadership needs a synthesis of mixed product, growth, delivery, support, and business signals — not just a status report.

## Output goal

Produce a leadership-grade operating view that identifies the dominant pattern underneath mixed signals and turns it into a usable next-period focus.

## Hard requirement

The review must produce a **dominant operating diagnosis**.
That diagnosis should explain why at least two positive signals and two warning signals can be true at the same time.
If the output only restates signals one by one, it is not finished.

---

# Head of Product Operating Review

## 1. Period summary

- Review period:
- Core product objective:
- Business context:

## 2. Bottom line

- What is actually going well:
- What is off track:
- Overall call for this period:

## 3. Signal pattern

### Positive signals

-
-

### Warning signals

-
-

### What the mixed pattern likely means

-

### Dominant operating diagnosis

- One sentence that explains the main underlying pattern behind the mixed signals:

### What not to overreact to

-

## 4. Core diagnosis

- What is the most important underlying product / operating diagnosis?
- What bottleneck is currently dominating outcomes?
- Why is this more important than the other signals right now?

## 5. Product / growth / delivery / cross-functional view

### Product

-

### Growth

-

### Delivery / execution

-

### Cross-functional friction

-

## 6. Current call

- What should leadership treat as the main next-period focus?
- What should not be treated as top focus, even if it is noisy?

## 7. Above the line / below the line

### Above the line

-
-
-

### Below the line

-
-
-

## 8. What would change this call

- Which assumptions or upcoming evidence could change the diagnosis or priority focus?

## 9. Leadership decisions needed

1.
2.
3.

## 10. Ask to leadership

- Decision / support needed:
- Resource implication:
- Review checkpoint:
