6.3 OBS, CBS, and the Responsibility Assignment Matrix (RACI)

6.3 OBS, CBS, and the Responsibility Assignment Matrix (RACI)

Core Principle: Creating a Work Breakdown Structure (WBS) identifies what work must be done, but a project cannot succeed in an organizational vacuum. To execute the work, the project manager must systematically determine who will execute and govern each task, and how much money is allocated to fund it.

In the APM Body of Knowledge (BoK7), project governance relies on the deliberate synthesis of three hierarchical dimensions: the Work Breakdown Structure (WBS), the Organizational Breakdown Structure (OBS), and the Cost Breakdown Structure (CBS). When these three structures intersect, theoretical project planning transforms into rigorous operational accountability and financial control.

---

The Breakdown Structure Trinity

                     +--------------------------+
                     |   THE GOVERNANCE TRINITY |
                     +-------------+------------+
                                   |
         +-------------------------+-------------------------+
         |                         |                         |
+------------------+      +------------------+      +------------------+
|       WBS        |      |       OBS        |      |       CBS        |
|  "WHAT WORK?"    |      |     "WHO?"       |      |  "HOW MUCH?"     |
|  Work Packages   |      |  Resource Units  |      | Cost Categories  |
+--------+---------+      +--------+---------+      +--------+---------+
         |                         |                         |
         +------------+------------+                         |
                      |                                      |
             +------------------+                            |
             | CONTROL ACCOUNT  |<---------------------------+
             | Single-Point CAM |  Allocated Cost Codes
             +--------+---------+
                      |
             +------------------+
             |   RACI MATRIX    |
             | Governance Rules |
             +------------------+

1. Organizational Breakdown Structure (OBS)

The Organizational Breakdown Structure (OBS) is a hierarchical representation of the organization delivering the project. It maps the project team, internal functional departments (e.g., Engineering, Procurement, Quality Assurance, Legal), and external entities (e.g., prime contractors, specialized trade subcontractors, design consultants, regulatory inspectors).

Unlike a routine corporate organization chart (which reflects permanent corporate hierarchies), the OBS is specifically tailored to the project endeavor. It identifies the reporting lines, operational boundaries, and human resources available to execute project activities.

2. Cost Breakdown Structure (CBS)

The Cost Breakdown Structure (CBS) is a hierarchical framework that categorizes project costs across accounting codes, ledger classifications, and expenditure types. It breaks down the total project budget into:

• Direct Costs: Directly traceable to specific work packages (e.g., labor hours of project staff, specialized fabrication materials, hired heavy equipment, subcontractor invoice costs);
• Indirect Costs (Overheads): Shared operational costs required to support the project but not attributable to a single work package (e.g., project site office rent, IT network infrastructure, executive administration, corporate insurances);
• Reserves: Financial provisions set aside for risk management, encompassing Contingency Reserves (budget allocated for identified 'known-unknown' risks) and Management Reserves (funds retained by the Sponsor for unforeseen 'unknown-unknown' strategic risks).

By linking the CBS to the organization's Chart of Accounts, project costs can be collected, committed, tracked, and audited against enterprise financial systems.

---

The Intersection: Control Accounts and Single-Point Accountability

When a terminal work package from the WBS is mapped against an organizational unit from the OBS, it forms a Control Account (historically termed a Cost Account).

Control Account Features:

• The Focal Point of Management: A Control Account represents the precise management intersection where scope, schedule, and budget converge for a specific deliverable.
• Single-Point Accountability: APM governance dictates that every Control Account must have exactly one designated Control Account Manager (CAM). The CAM is granted the authority and budget to lead the team and is held personally accountable for delivering the specified scope within the baselined timeframe and financial limits.
• Earned Value Measurement: Control Accounts are the fundamental accounting nodes where Earned Value Management (EVM) metrics are calculated. Planned Value (PV), Earned Value (EV), and Actual Cost (AC) are measured at the control account level, providing early warning of cost and schedule variances.

---

The Responsibility Assignment Matrix (RAM) and RACI Framework

While a Control Account establishes high-level delivery ownership, complex work packages involve multiple participants, technical specialists, advisors, and corporate decision-makers. To eliminate role ambiguity and streamline communication, project managers construct a Responsibility Assignment Matrix (RAM).

The most widely recognized and authoritative RAM format in modern project management is the RACI matrix.

+---+-------------------------------------------------------------------------------------+
| R | RESPONSIBLE: The "Doer"                                                             |
|   | - The role or individual who performs the actual physical or intellectual work.     |
|   | - Multiple people can share 'R' on a collaborative task.                            |
+---+-------------------------------------------------------------------------------------+
| A | ACCOUNTABLE: The "Owner"                                                            |
|   | - The single individual who holds ultimate approval authority and decision power.  |
|   | - The buck stops here. Golden Rule: Exactly ONE 'A' per activity.                   |
+---+-------------------------------------------------------------------------------------+
| C | CONSULTED: The "Advisor"                                                            |
|   | - Subject matter experts (SMEs) providing two-way technical or regulatory input.    |
|   | - Consulted BEFORE decisions or actions are finalized.                              |
+---+-------------------------------------------------------------------------------------+
| I | INFORMED: The "Observer"                                                           |
|   | - Stakeholders who receive one-way updates regarding progress or completed outcomes.|
|   | - Kept informed AFTER decisions; has no veto or editing authority.                  |
+---+-------------------------------------------------------------------------------------+

Deconstructing the RACI Definitions:

1. Responsible (R) — The "Doer": The individual, functional group, or contractor tasked with executing the work to produce the deliverable. 'R' is action-oriented. Depending on the size of the work package, multiple individuals may be assigned 'R' to collaborate on execution.
2. Accountable (A) — The "Owner": The single individual with ultimate veto, sign-off, and approval authority. They ensure that the deliverable meets all quality standards, contractual requirements, and business objectives. While work can be delegated to those who are Responsible, accountability cannot be shared or delegated.
3. Consulted (C) — The "Advisor": Individuals or groups whose specialized expertise, legal counsel, or operational perspectives are required. Consultation is two-way communication: the project team seeks advice, and the consulted stakeholder provides critical input before the work is completed or approved.
4. Informed (I) — The "Observer": Stakeholders who need to be kept up to date on project progress, key milestones, or completed deliverables. Communication is one-way: informed parties are notified after actions are taken or decisions are ratified. They do not have approval, advisory, or veto authority.

---

Practical Application: Project RACI Matrix

The following matrix illustrates a realistic RACI allocation for a major enterprise infrastructure project across key governance roles:

Analytical Breakdown of Matrix Assignments:

• In Task 1.1 (Business Case), the Project Manager is Responsible (R) for drafting the document, but the Project Sponsor is strictly Accountable (A) for authorizing capital investment. Operations and Procurement are Consulted (C) to provide realistic cost and maintenance assumptions.
• In Task 3.2 (Procurement), the Procurement Lead is Responsible (R) for commercial negotiations and supplier vetting, while the Project Manager is Accountable (A) for ensuring the contracts align with overall project scope and schedule baselines.
• In Task 5.2 (System Testing), the QA / Test Manager is Responsible (R) for executing stress tests, while Design Engineering is Consulted (C) to evaluate anomalies.

---

Golden Rules of RACI Governance

To ensure a RACI matrix provides clarity rather than confusion, project professionals must enforce several non-negotiable rules:

1. Exactly ONE 'A' Per Activity (The Golden Rule)

Every single task or work package must have one, and only one, individual marked as Accountable ('A').

• The Hazard of Multiple 'A's: When accountability is shared between two or more individuals, diffusion of responsibility occurs. If a failure happens, each party blames the other, decisions deadlock, and governance collapses ("If everyone is accountable, no one is accountable").
• The Hazard of Zero 'A's: A task with no 'A' is an orphan activity. No one owns the outcome, quality assurance is ignored, and the deliverable inevitably drifts.

2. At Least One 'R' Per Activity

Every task must have at least one person or team designated as Responsible ('R'). An activity without an 'R' is merely theoretical intent—there is no one assigned to perform the physical or intellectual labor.

3. Keep 'Consulted' ('C') Lean to Prevent Analysis Paralysis

Consulting too many stakeholders is a frequent project trap. While stakeholder engagement is important, assigning excessive 'C's leads to endless committee meetings, conflicting advice, scope bloat, and severe schedule delays. Only consult stakeholders whose technical, legal, or operational expertise is genuinely indispensable.

4. Enforce One-Way Boundaries for 'Informed' ('I')

Stakeholders marked as 'Informed' must understand that their role is purely observational. A common project dysfunction occurs when 'Informed' parties attempt to debate decisions, request design modifications, or exercise an unearned veto. Project managers must firmly protect delivery momentum by distinguishing between consultation and notification.

5. Separate 'Responsible' from 'Accountable'

Avoid the temptation to assign 'A' and 'R' to the same person on every task. While a small project may require the project manager to both do the work and approve it, healthy organizational governance in larger projects separates execution ('R') from final verification and sign-off ('A') to maintain objective quality assurance.