Product manager role map

The question it helps answer

Use the product manager role map to organise the reasoning behind this question: What outcomes should product managers own across strategy, prioritization, execution, and communication? The working view makes vision, customer, and priorities visible so discussion can move from general opinion to a specific action or decision.

When to use it

Use the product manager role map when people working on product leadership are using different mental models for vision, customer, and priorities, and that difference is changing choices or coordination.

What it is

The product manager role map is a set of connected concepts for examining one situation from several necessary angles. Its core working elements are vision, customer, priorities, and trade-offs. Those elements belong together because each changes how the others should be interpreted or acted on.

Core elements

Vision

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

Customer

Identify the relevant people or groups, their needs, and any important differences in influence, access, or impact. Within the product manager role map, connect this entry to priorities so the relationship can be reviewed rather than inferred.

Priorities

Capture priorities only at the level needed to answer: What outcomes should product managers own across strategy, prioritization, execution, and communication? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager role map, connect this entry to trade-offs so the relationship can be reviewed rather than inferred.

Trade-offs

Make the competing benefits explicit and record what is deliberately being prioritized, delayed, limited, or given up. Within the product manager role map, connect this entry to execution so the relationship can be reviewed rather than inferred.

Execution

Define the work that must happen, the accountable owner, the first observable milestone, dependencies, and the signal that execution is off track. Within the product manager role map, connect this entry to lifecycle so the relationship can be reviewed rather than inferred.

Lifecycle

Capture lifecycle only at the level needed to answer: What outcomes should product managers own across strategy, prioritization, execution, and communication? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager role map, connect this entry to communication so the relationship can be reviewed rather than inferred.

Communication

Match the message, level of detail, channel, sender, timing, and feedback path to the audience and consequence. Within the product manager role map, connect this entry to interfaces so the relationship can be reviewed rather than inferred.

Interfaces

Describe what each side provides, when it is needed, how readiness is confirmed, and where unresolved issues escalate. Within the product manager role map, 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: What outcomes should product managers own across strategy, prioritization, execution, and communication? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager role map, connect this entry to interfaces so the relationship can be reviewed rather than inferred.