Product-design-engineering responsibility map

The question it helps answer

Use the product-design-engineering responsibility map to organise the reasoning behind this question: How should product, design, and engineering divide ownership while resolving overlap? The working view makes outcome, vision, and experience visible so discussion can move from general opinion to a specific action or decision.

When to use it

Use the product-design-engineering responsibility map when people working on product leadership are using different mental models for outcome, vision, and experience, and that difference is changing choices or coordination.

What it is

The product-design-engineering responsibility map is a set of connected concepts for examining one situation from several necessary angles. Its core working elements are outcome, vision, experience, and architecture. Those elements belong together because each changes how the others should be interpreted or acted on.

Core elements

Outcome

Describe the observable result, who benefits, and the evidence that would show meaningful progress. Within the product-design-engineering responsibility map, connect this entry to vision so the relationship can be reviewed rather than inferred.

Vision

State the intended contribution in plain language and distinguish the enduring purpose from the current plan. Within the product-design-engineering responsibility map, connect this entry to experience so the relationship can be reviewed rather than inferred.

Experience

Capture experience only at the level needed to answer: How should product, design, and engineering divide ownership while resolving overlap? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product-design-engineering responsibility map, connect this entry to architecture so the relationship can be reviewed rather than inferred.

Architecture

Capture architecture only at the level needed to answer: How should product, design, and engineering divide ownership while resolving overlap? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product-design-engineering responsibility map, connect this entry to prioritization so the relationship can be reviewed rather than inferred.

Prioritization

Capture prioritization only at the level needed to answer: How should product, design, and engineering divide ownership while resolving overlap? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product-design-engineering responsibility 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-design-engineering responsibility map, connect this entry to decisions so the relationship can be reviewed rather than inferred.

Decisions

Name the decision, the person or body with final authority, the date, and the rationale that should remain visible later. Within the product-design-engineering 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: How should product, design, and engineering divide ownership while resolving overlap? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the product-design-engineering responsibility map, connect this entry to decisions so the relationship can be reviewed rather than inferred.