Product strategy stack

The question it helps answer

Use the product strategy stack to organise the reasoning behind this question: How should vision, product strategy, pillar strategies, roadmaps, and near-term goals fit together? The working view makes five artifact levels, purpose, and owner visible so discussion can move from general opinion to a specific action or decision.

When to use it

Use the product strategy stack when people working on product strategy and roadmaps are using different mental models for five artifact levels, purpose, and owner, and that difference is changing choices or coordination.

What it is

The product strategy stack is a set of connected concepts for examining one situation from several necessary angles. Its core working elements are five artifact levels, purpose, owner, and horizon. Those elements belong together because each changes how the others should be interpreted or acted on.

Core elements

Five artifact levels

Capture five artifact levels only at the level needed to answer: How should vision, product strategy, pillar strategies, roadmaps, and near-term goals fit together? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product strategy stack, connect this entry to purpose so the relationship can be reviewed rather than inferred.

Purpose

State the intended contribution in plain language and distinguish the enduring purpose from the current plan. Within the product strategy stack, connect this entry to owner so the relationship can be reviewed rather than inferred.

Owner

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

Horizon

Capture horizon only at the level needed to answer: How should vision, product strategy, pillar strategies, roadmaps, and near-term goals fit together? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product strategy stack, connect this entry to update cadence so the relationship can be reviewed rather than inferred.

Update cadence

Use a specific date or event, explain why it matters, and show dependencies that could change the timing. Within the product strategy stack, connect this entry to linkage rules so the relationship can be reviewed rather than inferred.

Linkage rules

Capture linkage rules only at the level needed to answer: How should vision, product strategy, pillar strategies, roadmaps, and near-term goals fit together? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product strategy stack, connect this entry to anti-patterns so the relationship can be reviewed rather than inferred.

Anti-patterns

Capture anti-patterns only at the level needed to answer: How should vision, product strategy, pillar strategies, roadmaps, and near-term goals fit together? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product strategy stack, connect this entry to linkage rules so the relationship can be reviewed rather than inferred.