HKSM

A responsibility matrix is a chart that maps project work to roles to clarify who is responsible, accountable, consulted, and informed. It reduces ambiguity about ownership, decision rights, and communication expectations across stakeholders.

Key Points

• Also known as a RACI or Responsibility Assignment Matrix (RAM).
• Links activities or deliverables to roles to clarify R, A, C, and I participation.
• Prevents gaps, overlaps, and conflicting approvals by making decision rights explicit.
• Works best when aligned to the WBS and schedule for clear traceability.
• Aim for one Accountable per work item to avoid confusion and delays.
• Create early and maintain as scope, organization, or resources change.

Purpose

• Clarify who does the work and who owns the outcome for each work item.
• Accelerate decisions and approvals by defining authority and escalation paths.
• Set expectations for consultation and communication among stakeholders.
• Support onboarding and handoffs across functions or vendors.
• Provide inputs to the communications and governance approaches.

Field Definitions

• Work Item: The activity, deliverable, or work package being assigned.
• Role/Org Unit: The role or team accountable for or participating in the work.
• R - Responsible: Performs the work to produce the output.
• A - Accountable: Owns the outcome and gives final approval; exactly one is recommended.
• C - Consulted: Provides input or expertise; two-way communication.
• I - Informed: Receives status updates or decisions; one-way communication.
• Notes: Assumptions, constraints, or clarifications for the assignment.

How to Create

• List the work items from the WBS or backlog that need clear ownership.
• Identify roles or organizational units involved in delivering or approving the work.
• Select a responsibility model (e.g., RACI or RASCI) and define what each letter means.
• Assign R, A, C, and I for each work item; aim for one A, verify sufficient R, and keep C/I purposeful.
• Review with stakeholders to resolve gaps, overlaps, or conflicting authorities.
• Publish the matrix in a shared repository, version it, and link it to the WBS and schedule.

How to Use

• Reference it during planning and execution to confirm who approves, who performs, and who is consulted or informed.
• Embed responsibilities into meeting invites, change requests, and workflow steps.
• Use it to streamline approvals and escalate decisions per the defined accountabilities.
• Leverage it for onboarding, handoffs, and vendor coordination.
• Update it whenever roles, scope, or governance change, and communicate updates.

Ownership & Update Cadence

• Owner: Project manager maintains the matrix with input from sponsors and functional leads.
• Baseline: Establish during planning once key roles and work items are known.
• Updates: At phase gates, organizational changes, major scope changes, or resource shifts.
• Governance: Control through change management and store under version control.

Example Rows

Roles: Sponsor (SP), Project Manager (PM), Business Analyst (BA), Technical Lead (TL), Quality Lead (QL).

• Approve Project Charter — SP: A; PM: R; BA: I; TL: I; QL: I.
• Define Requirements — SP: A; BA: R; PM: C; TL: C; QL: I.
• Develop Work Package A — PM: A; TL: R; BA: C; QL: C; SP: I.
• Quality Review — PM: A; QL: R; TL: C; BA: C; SP: I.
• Release Deliverable — SP: A; PM: R; TL: C; QL: C; BA: I.

PMP Example Question

A team is missing deadlines because approvals are unclear and stakeholders are unsure who to consult for inputs. Which artifact will best resolve this issue?

1. Stakeholder register
2. Responsibility matrix
3. Issue log
4. Work breakdown structure

Correct Answer: B — Responsibility matrix

Explanation: A responsibility matrix defines who is responsible, accountable, consulted, and informed for each work item, clarifying approvals and communication. The other artifacts do not map decision rights to work items.