# Example 07 — Prioritization Stack

## Scenario

A PM has more requests than the team can absorb and needs a defendable ranking.

## Input

> "We have room for only 3 items next quarter: conversation history search, AI answer quality tuning, enterprise admin audit logs, onboarding simplification, team workspace sharing, growth referral flow, and export improvements. Help me prioritize them and explain what should wait."

## What good output looks like

A strong `pm-workbench` response should:

- anchor on the period objective before ranking items
- reflect impact, effort, dependencies, and commitments
- clearly identify what is above and below the line
- help the PM explain why some work is intentionally not prioritized now

## Expected output shape

**Prioritization Stack**

## Example response shape

- period objective
- constraints
- prioritization logic
- recommended stack
- notes on top items
- deferred items and why
- risks and sequencing notes
- immediate planning next step

## Why this is useful

Prioritization is where PM judgment becomes visible. A good stack makes trade-offs defendable instead of political.
