A Five-Skill Product Management Decision Workflow

Direct answer

The Product Management Decision Skills collection provides a five-stage path from discovery evidence to launch readiness. The prompts are designed to produce explicit decisions, assumptions, risks, owners, and acceptance criteria rather than generic product advice.

Who should use it

Product managers, product operations teams, founders, and cross-functional leads can use the collection when a decision must survive review by design, engineering, data, go-to-market, security, or leadership. It is most valuable for work with incomplete evidence and competing priorities.

The workflow

1. Product Discovery Evidence Mapper organizes research signals, contradictions, coverage gaps, and confidence without turning anecdotes into demand estimates. 2. Product Prioritization Decision Memo compares options against strategy, user impact, evidence, effort, risk, and opportunity cost. 3. Product Requirements Risk Reviewer checks a requirement for ambiguity, edge cases, dependencies, privacy, security, observability, and testability. 4. Product Experiment Design Auditor reviews hypotheses, metrics, guardrails, allocation, contamination, stopping rules, and interpretation risk. 5. Product Launch Readiness Coordinator consolidates evidence across product, engineering, support, legal, analytics, and go-to-market into a release decision.

Example use

For a proposed AI-assisted support feature, map evidence from customers, agents, ticket data, and policy owners. Write a prioritization memo that compares the feature with reliability work. Review requirements for human escalation, auditability, unsafe outputs, and latency. Design an experiment with quality and harm guardrails. Before launch, require monitoring, rollback, support documentation, ownership, and explicit acceptance of residual risk.

Limits

The prompts do not supply missing customer evidence, engineering estimates, legal advice, or executive authority. They make gaps visible. Teams should protect confidential research, avoid false scoring precision, and record the final human decision separately from the AI-assisted draft.

FAQ

Is the prioritization memo a substitute for a roadmap decision? No. It creates a comparable evidence package; accountable leaders still decide and record tradeoffs.

Can launch readiness be reduced to a checklist? A checklist helps, but readiness also requires verified evidence, named approvers, rollback capacity, and an explicit treatment of residual risk.