Pm Use Scenarios

Use Scenarios (Pragmatic Framework: Planning → Use Scenarios)

Rule: articulate problems from the persona's point of view. A use scenario illustrates a market problem as a "story" that puts it in context (including current results) — it is one component of requirements. See ../pm-copilot/references/framework.md. Personas should exist first (pm-personas).

Anatomy of a Problem Card

Map interrogatives to fields:

| Field | Interrogative | | :--- | :--- | | [Problem Name] | What problem | | [Persona] | Who has it | | has [use scenario] | Why it occurs | | with [frequency] | When it occurs |

Reframing sentence (great for turning a feature request into a problem): > [Persona] struggles with [problem] when [context] because [why it matters].

What vs. How — stay on the WHAT

| WHAT = the problem → PM → DEFINE | HOW = the solution → Team → DESIGN/BUILD | | :--- | :--- | | Name, Persona, Use Scenario, Frequency, Market evidence, Impact | Overview, flow chart, use cases, UI, prototypes, error conditions |

A use scenario ≠ a use case. A use scenario tells the problem story; a use case enumerates every interaction in the functional spec (the team's job).

Three considerations when articulating a problem

1. Avoid ambiguous terms — do not use: *flexible, adaptable, user-friendly, TBD,

adequate, rapidly/quickly/fast, fault tolerant, scalable, ASAP, maximize/minimize/optimize (any "-ize" word), and/or, etc.* Replace each with a concrete, observable statement.

1. Edge cases ("what if?") — will your persona actually do it? Don't design for

situations that won't happen.

1. Who is significant? — the U-curve: the vocal extremes (novices + experts) are

where we listen; the proficient majority is where we should listen. Write for the majority.

Interview the user (batch questions)

1. Which persona and which market problem is this scenario for?
2. Walk me through a real situation where this happens — what triggers it, what do they

do today, and what's the current (bad) result?

1. How often does it occur (frequency)?
2. What evidence shows this is real (counts across inputs) and how bad is it (impact)?

Artifact template

# Use Scenarios — 

**Company:**   ·  **Feature / Product:** 
**Author:**   ·  **Date created:**   ·  **Version:** 1.0

## Scenario 1 — 
**Problem Card**
- **Problem Name:** 
- **Persona:** 
- **Use Scenario:** 
- **Frequency:** 

**Day in the life**

**Market evidence:** 
**Impact:** 

## Scenario 2 — 
…

Deliver the artifact

Follow ../pm-copilot/references/artifact-output.md: confirm inputs, ask Markdown or .docx, write the .md, convert to .docx on request via your environment's native document-creation capability. Then offer the next stage: roll these scenarios into prioritized pm-requirements or a full pm-prd.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: julianoczkowski
• Source: julianoczkowski/product-manager
• License: MIT

Install and usage instructions live in the source repository linked above.