Product management operating system

The question it helps answer

Use the product management operating system to organise the reasoning behind this question: How should product requirements, reviews, launch readiness, and retrospectives work as one system? The working view makes pRD, road map, and review visible so discussion can move from general opinion to a specific action or decision.

When to use it

Use the product management operating system when people working on product leadership are using different mental models for pRD, road map, and review, and that difference is changing choices or coordination.

What it is

The product management operating system is a set of connected concepts for examining one situation from several necessary angles. Its core working elements are pRD, road map, review, and launch calendar. Those elements belong together because each changes how the others should be interpreted or acted on.

Core elements

PRD

Capture pRD only at the level needed to answer: How should product requirements, reviews, launch readiness, and retrospectives work as one system? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product management operating system, connect this entry to road map so the relationship can be reviewed rather than inferred.

Road map

Capture road map only at the level needed to answer: How should product requirements, reviews, launch readiness, and retrospectives work as one system? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product management operating system, connect this entry to review so the relationship can be reviewed rather than inferred.

Review

Set a review rhythm and define the evidence, threshold, or event that should trigger an earlier review. Within the product management operating system, connect this entry to launch calendar so the relationship can be reviewed rather than inferred.

Launch calendar

Capture launch calendar only at the level needed to answer: How should product requirements, reviews, launch readiness, and retrospectives work as one system? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product management operating system, connect this entry to readiness so the relationship can be reviewed rather than inferred.

Readiness

Capture readiness only at the level needed to answer: How should product requirements, reviews, launch readiness, and retrospectives work as one system? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product management operating system, connect this entry to retrospective so the relationship can be reviewed rather than inferred.

Retrospective

Capture retrospective only at the level needed to answer: How should product requirements, reviews, launch readiness, and retrospectives work as one system? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product management operating system, connect this entry to owners so the relationship can be reviewed rather than inferred.

Owners

Assign one accountable owner and distinguish final accountability from contributors, reviewers, and people who must be informed. Within the product management operating system, connect this entry to cadence so the relationship can be reviewed rather than inferred.

Cadence

Set a review rhythm and define the evidence, threshold, or event that should trigger an earlier review. Within the product management operating system, connect this entry to health so the relationship can be reviewed rather than inferred.

Health

Set a review rhythm and define the evidence, threshold, or event that should trigger an earlier review. Within the product management operating system, connect this entry to cadence so the relationship can be reviewed rather than inferred.