# Example 21 — Mixed signals operating review

## Scenario

Some metrics are up. Some are flat. Some complaints persist. Leadership needs a real diagnosis, not a report dump.

## Input

> "I need to prepare a monthly product operating review. New user activation is up, but early retention is flat. Team output looks busy, but support tickets on onboarding are still elevated. Sales is happy with enterprise interest, but product quality complaints on AI reliability have not really gone away. Help me turn this into a leadership-grade operating review with a clear bottom line and next focus."

## What good output looks like

A strong `pm-workbench` response should:

- synthesize the signal pattern instead of reciting metrics one by one
- identify the dominant diagnosis underneath the mixed signals
- say what leadership should focus on next
- make above-the-line and below-the-line focus explicit
- avoid neutral status-report tone

## Expected output shape

**Head of Product Operating Review**

## Example response shape

- recommendation
- signal pattern
- core diagnosis
- what not to overreact to
- current call
- above the line / below the line
- leadership ask

## Why this is useful

Leader-grade product work is often less about individual metrics and more about which pattern matters most right now.
