/define — Product Owner Interview

Overview

Define requirements by interviewing the user. The interview IS the value — a requirements doc produced without conversation is just guessing.

Core principle: Ask, don't assume. Every assumption is a question you didn't ask.

When to Use

• User describes a new feature, bug, or change request
• Work needs to be broken down before architecture or implementation
• You need to understand scope, personas, and success criteria

The Process

1. Gather Context (silent — don't show this to user)