# Example 02 — Feature Evaluation Memo

## Scenario

A team proposes a feature that may be a gimmick, and the PM needs a clear recommendation.

## Input

> "Operations wants a daily AI fortune card feature to improve engagement. I’m worried it’s a gimmick. Help me evaluate it."

## What good output looks like

A strong `pm-workbench` response should:

- ask about the minimum critical premises if they affect the recommendation
- evaluate user value, business value, strategic fit, and opportunity cost
- avoid jumping straight from enthusiasm to shipping
- produce a decision-ready memo

## Expected output shape

**Feature Evaluation Memo**

## Example response shape

- request summary
- problem behind the request
- target user and scenario
- expected value
- evidence and confidence
- cost, complexity, and risk
- recommendation
- conditions that may change the decision
- next actions

## Why this is useful

Many PM decisions fail because evaluation stays verbal and vague. A structured memo makes the recommendation easier to discuss, challenge, and act on.
