product-decision-records

name	product-decision-records
description	Maintain product decision records with problem, evidence, options, owner, rationale, expected outcome, dependencies, revisit conditions, and downstream communication.

Product Decision Records

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using product briefs, research, analytics, roadmap decisions, launch scope, and stakeholder commitments. Do not fill material gaps with assumptions when they can change the result.
3. Define which decisions deserve records, capture at decision time, link requirements/research/metrics, publish to affected teams, and revisit when triggers occur.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Teams can reconstruct why product behavior/scope exists without relying on oral history.