RACI¶

Overview¶

RACI is a responsibility assignment framework used in project and process management. The name RACI represents four roles that describe how individuals or groups participate in completing tasks or deliverables:

• Responsible (R): Performs the work to complete the task.

• Accountable (A): Owns the outcome and approves the work.

• Consulted (C): Provides input or expertise before work is done.

• Informed (I): Is kept updated on progress or decisions.

A RACI matrix maps project activities to roles, making responsibilities explicit and reducing ambiguity.

What RACI Is Used to Support¶

RACI supports the following project management objectives:

• Clarifying ownership and decision authority
• Reducing role overlap and gaps in responsibility
• Improving communication across teams and stakeholders
• Supporting governance, auditability, and accountability
• Scaling coordination as team size and complexity increase

Use of RACI in Small and Large Teams¶

RACI is applicable to both small and large teams, but the way it is used differs.

• Small teams
• Often informal and lightweight
• Used to clarify ownership when individuals wear multiple hats

• Helps prevent assumptions such as “someone else is handling it”

• Large or distributed teams

• More formal and structured
• Used to manage dependencies across departments, vendors, or regions
• Often required for compliance, governance, or enterprise delivery models

RACI is widely used by global organizations such as IBM, Microsoft, Accenture, and Deloitte as part of their project governance practices. In Vietnam, RACI is commonly adopted by large enterprises and technology-driven organizations such as Viettel, FPT Software, Vingroup, and multinational companies operating in software development, construction, and manufacturing.

Configuration and Definition¶

RACI Role Definitions¶

Core Rules¶

• Each task must have at least one Responsible
• Each task must have exactly one Accountable
• One person may hold multiple roles for a task
• Roles are assigned to activities, not job titles

Detail About RACI¶

Core Components¶

Example RACI Matrix¶

How RACI Is Applied¶

Step-by-Step Application Procedure¶

Step 1: Identify Activities:

List all key tasks, decisions, or deliverables within the project or process.

Step 2: Identify Roles:

Define the roles involved, using role names rather than individual names where possible.

Step 3: Assign RACI Roles:

For each activity:

• Assign one or more Responsible
• Assign exactly one Accountable
• Assign Consulted roles as needed
• Assign Informed roles as needed

Step 4: Validate the Matrix:

Check for:

• Missing Responsible or Accountable roles
• Too many Consulted or Informed roles
• Individuals overloaded with Accountable assignments

Step 5: Communicate and Maintain Share the RACI matrix with all stakeholders and update it when scope or roles change.

Best Fit Scenarios¶

RACI works best when:

• Projects have multiple stakeholders or teams
• Decision authority must be explicit
• Work spans functional or organizational boundaries
• Processes are repeatable and auditable

Scenarios Where RACI Is Less Effective¶

RACI is not ideal when:

• Teams are very small and co-located with constant communication
• Work is highly exploratory or research-based
• Organizational culture resists formal role definition
• Responsibilities change daily without stable activities

Key Problems When Applying RACI¶

Common Issues¶

• Multiple Accountables Leads to unclear decision authority and conflict.

• Overuse of Consulted Role Causes delays and excessive communication overhead.

• Using Names Instead of Roles Makes the matrix fragile when personnel change.

• Treating RACI as Static Outdated matrices reduce trust and usefulness.

• Assuming RACI Replaces Communication RACI clarifies responsibility but does not replace collaboration.

Mitigation Practices¶

• Enforce one Accountable per activity

• Keep the matrix lightweight and focused

• Review RACI at major project milestones

• Align RACI with organizational decision-making models

Scope and Applicability¶

• Domain: Project management, process management, governance
• Scale: Small teams to large enterprises
• Industry: Technology, construction, manufacturing, finance, public sector
• Platform: Methodology-agnostic; applicable across tools and frameworks

Reference¶

• Project Management Institute (PMI), PMBOK® Guide

• ISO 21500: Guidance on Project Management

• Harvard Business Review, articles on responsibility assignment matrices

• Official PMI resources on RACI and responsibility modeling