How I work as a technical product owner

Start with the user's decision

I begin by identifying what the user is trying to decide or accomplish. A feature list is not a product definition; the product is the change in what a person can do with confidence.

Make the system legible

I turn the problem into explicit workflows, data shapes, constraints, and acceptance criteria. This creates a shared object for product, engineering, and documentation conversations.

Keep scope honest

I prefer a small end-to-end path that can be tested and explained over a large collection of disconnected capabilities. Limits and non-goals belong in the product record.