Product manager archetype matrix

The decision it supports

Use the product manager archetype matrix to compare unlike items without forcing them into one undifferentiated ranking. The working view makes archetype, customer, and product context visible so discussion can move from general opinion to a specific action or decision.

When to map the portfolio

Use the product manager archetype matrix when a list in product leadership contains materially different cases that should not receive the same response. The matrix is useful only when the anchors for archetype, customer, and product context can be supported with evidence.

How the matrix works

The product manager archetype matrix is a two-dimensional comparison that gives different positions different management responses. Its core working elements are archetype, customer, product context, and strengths. Those elements belong together because each changes how the others should be interpreted or acted on.

Axes and responses

Archetype

Capture archetype only at the level needed to answer: Which blend of business, technical, design, and growth product skills does the portfolio need? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager archetype matrix, 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 archetype matrix, connect this entry to product context so the relationship can be reviewed rather than inferred.

Product context

Record only the context that changes the work, separating verified facts from interpretations and assumptions. Within the product manager archetype matrix, connect this entry to strengths so the relationship can be reviewed rather than inferred.

Strengths

Capture strengths only at the level needed to answer: Which blend of business, technical, design, and growth product skills does the portfolio need? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager archetype matrix, connect this entry to risks so the relationship can be reviewed rather than inferred.

Risks

Describe the cause, possible consequence, early warning signal, owner, and proportionate prevention or response. Within the product manager archetype matrix, connect this entry to partners so the relationship can be reviewed rather than inferred.

Partners

Capture partners only at the level needed to answer: Which blend of business, technical, design, and growth product skills does the portfolio need? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager archetype matrix, connect this entry to interview evidence so the relationship can be reviewed rather than inferred.

Interview evidence

Name the evidence, its date and owner, and any limitation that affects how confidently it can be used. Within the product manager archetype matrix, connect this entry to mix so the relationship can be reviewed rather than inferred.

Mix

Capture mix only at the level needed to answer: Which blend of business, technical, design, and growth product skills does the portfolio need? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product manager archetype matrix, connect this entry to interview evidence so the relationship can be reviewed rather than inferred.