# Example 20 — Launch readiness call under pressure

## Scenario

Marketing wants a date. Product is not fully ready. Leadership wants a confident answer tomorrow.

## Input

> "Marketing wants to lock a launch date for our new AI workflow in 3 weeks because they need campaign lead time. Product and design think the core experience is promising, but activation is still patchy and support flows are not ready. My boss wants a confident answer by tomorrow. Help me decide what to recommend and how to frame it upward."

## What good output looks like

A strong `pm-workbench` response should:

- recognize this is both a decision problem and a communication problem
- avoid fake confidence without collapsing into vague caution
- make the current recommendation explicit
- separate what should be decided now from what still needs validation
- frame the ask in a way leadership can approve, challenge, or narrow

## Expected output shape

**Executive Summary** or a compressed launch-decision brief

## Example response shape

- recommendation
- readiness gap
- consequence of launching anyway
- current recommendation
- decide now vs validate next
- leadership ask

## Why this is useful

This is a classic high-pressure PM moment. The goal is not to sound calm — it is to make a usable call under imperfect readiness.
