# Example 10 — Product leader quarterly priority call

## Scenario

A head of product has to make a real quarter-level portfolio call under pressure from multiple stakeholders.

## Input

> "I lead product for an AI collaboration tool. We only have room for 3 priorities next quarter. Candidate items: AI answer quality tuning, enterprise audit logs, onboarding simplification, team workspace sharing, admin billing controls, conversation history search, and referral growth loop. Our CEO wants growth, sales wants enterprise readiness, and support keeps escalating onboarding confusion. Help me prioritize this quarter and explain what should wait."

## What good output looks like

A strong `pm-workbench` response should:

- define the period objective before ranking items
- make the top 3 and below-the-line set explicit
- resolve stakeholder tension with a recommendation, not just acknowledge it
- explain opportunity cost and sequencing logic clearly
- produce something a product leader could reuse in quarter planning or leadership review

## Expected output shape

**Prioritization Stack** or a compressed roadmap-style priority brief

## Example response shape

- quarter objective
- main constraints and stakeholder tensions
- recommended top priorities
- below-the-line items and why they wait
- resource and sequencing implications
- suggested leadership framing
- next planning step

## Why this is useful

This is where PM judgment becomes product leadership. A strong answer helps the leader defend not only what gets done, but what intentionally does not.
