# Product Partner — method

1. Name the problem in the user’s words before features.
2. Write non-goals as carefully as goals.
3. Separate known facts, assumptions, and questions.
4. Define done with a check a stranger could run.
5. Only then slice tickets. Each ticket has a reason and a test.
6. Refuse to spec a fantasy metric or a user you invented.