Role-to-jobs map

The decision it supports

Use the role-to-jobs map to compare unlike items without forcing them into one undifferentiated ranking. The working view makes workflow stages, jobs, and role applicability visible so discussion can move from general opinion to a specific action or decision.

When to map the portfolio

Use the role-to-jobs map when a list in hiring and organization contains materially different cases that should not receive the same response. The matrix is useful only when the anchors for workflow stages, jobs, and role applicability can be supported with evidence.

How the matrix works

The role-to-jobs map is a two-dimensional comparison that gives different positions different management responses. Its core working elements are workflow stages, jobs, role applicability, and proficiency. Those elements belong together because each changes how the others should be interpreted or acted on.

Axes and responses

Workflow stages

Use a small controlled set of states, define the entry and exit condition for each, and record the date of the latest change. Within the role-to-jobs map, connect this entry to jobs so the relationship can be reviewed rather than inferred.

Jobs

Capture jobs only at the level needed to answer: Which recurring jobs should each role perform across an end-to-end workflow? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the role-to-jobs map, connect this entry to role applicability so the relationship can be reviewed rather than inferred.

Role applicability

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

Proficiency

Capture proficiency only at the level needed to answer: Which recurring jobs should each role perform across an end-to-end workflow? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the role-to-jobs map, connect this entry to frequency so the relationship can be reviewed rather than inferred.

Frequency

Set a review rhythm and define the evidence, threshold, or event that should trigger an earlier review. Within the role-to-jobs map, connect this entry to support so the relationship can be reviewed rather than inferred.

Support

Capture support only at the level needed to answer: Which recurring jobs should each role perform across an end-to-end workflow? Use observable evidence, name any unresolved judgment, and state what action or choice this entry can change. Within the role-to-jobs map, 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 role-to-jobs map, connect this entry to support so the relationship can be reviewed rather than inferred.