Build-maintain-launch responsibility map

The decision it supports

Use the build-maintain-launch responsibility map to compare unlike items without forcing them into one undifferentiated ranking. The working view makes capability rows, lifecycle columns, and accountable owner visible so discussion can move from general opinion to a specific action or decision.

When to map the portfolio

Use the build-maintain-launch responsibility map when a list in product development and operating models contains materially different cases that should not receive the same response. The matrix is useful only when the anchors for capability rows, lifecycle columns, and accountable owner can be supported with evidence.

How the matrix works

The build-maintain-launch responsibility map is a two-dimensional comparison that gives different positions different management responses. Its core working elements are capability rows, lifecycle columns, accountable owner, and contributors. Those elements belong together because each changes how the others should be interpreted or acted on.

Axes and responses

Capability rows

Describe the capability as observable work, cite evidence of current proficiency, and choose a practical next development action. Within the build-maintain-launch responsibility map, connect this entry to lifecycle columns so the relationship can be reviewed rather than inferred.

Lifecycle columns

Capture lifecycle columns only at the level needed to answer: Who owns building, maintaining, and bringing each capability to market? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the build-maintain-launch responsibility map, connect this entry to accountable owner so the relationship can be reviewed rather than inferred.

Accountable owner

Assign one accountable owner and distinguish final accountability from contributors, reviewers, and people who must be informed. Within the build-maintain-launch responsibility map, connect this entry to contributors so the relationship can be reviewed rather than inferred.

Contributors

Capture contributors only at the level needed to answer: Who owns building, maintaining, and bringing each capability to market? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the build-maintain-launch responsibility map, connect this entry to kPIs so the relationship can be reviewed rather than inferred.

KPIs

Capture kPIs only at the level needed to answer: Who owns building, maintaining, and bringing each capability to market? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the build-maintain-launch responsibility map, connect this entry to handoffs so the relationship can be reviewed rather than inferred.

Handoffs

Describe what each side provides, when it is needed, how readiness is confirmed, and where unresolved issues escalate. Within the build-maintain-launch responsibility map, connect this entry to escalation so the relationship can be reviewed rather than inferred.

Escalation

Capture escalation only at the level needed to answer: Who owns building, maintaining, and bringing each capability to market? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the build-maintain-launch responsibility map, connect this entry to handoffs so the relationship can be reviewed rather than inferred.