R2A2 Framework (Roles, Responsibilities, Accountabilities, Authorities)
R2A2 is a framework for clarifying who is responsible for what, especially for critical objectives and risks. It emphasizes separation of duties, accountability mapping, and learning from regulatory regimes like the UK Senior Managers and Certification Regime and the Australian BEAR provisions.
THE IDEA
Key Points
R2A2—Roles, Responsibilities, Accountabilities, and Authorities—must be sufficiently clear for the objectives and risks that matter most. While it is neither practical nor necessary to pin down every position in exhaustive detail, ambiguity around priority activities can leave important work undone. This begins at the top: even the most senior people need reasonable clarity about who does what, including a deliberate separation of duties (e.g., between CEO and CFO, or CEO and the board). Paterson cites the UK Senior Managers and Certification Regime and Australia’s BEAR provisions as examples of formal accountability arrangements.
Clarity is not a one‑off design exercise. Roles need a degree of flexibility to adapt to shifting circumstances, which is where “adaptive accountability” thinking becomes helpful. Tools such as RACI, RAPID, and swim‑lane diagrams can compare the intended allocation of work with what people actually do. Mapping the “as is” helps people identify disagreements about who is responsible.
Beware the assumption that clear top‑level R2A2 automatically cascades faithfully throughout the organisation. The role of a policy owner illustrates the complexity: policy owners may carry legal accountability, yet in practical terms they often lack the authority to enforce or resource risk management at the operational level. Proactive checks are therefore needed, especially for the most critical risks and sub‑risks. Review policies and accountabilities as work changes. Management information can also reveal gaps, such as repeated delays while teams dispute ownership. Internal Audit and other cross‑functional bodies can offer useful observations, but local managers must never delegate their own accountability for oversight, nor fall into the trap of relying on a regulator’s silence as assurance (“The regulator didn’t find anything, so it must be fine”).
Accountability can become harder to trace when third parties, external consultants, committees, or steering groups are involved. Emergency cover and succession arrangements must be designed to keep R2A2 working when someone is ill or moves on. Staff need a safe and visible mechanism to raise questions or concerns about who is accountable for what.
Several pressure points deserve routine scrutiny:
- The interplay between a policy owner and a business‑area manager in maintaining compliance: when a resource stand‑off occurs, is there a clear escalation and risk‑acceptance path?
- Whether managers understand that Internal Audit operates in the “third line”—it provides independent assurance, not a substitute for local checks.
- Whether managers mistake “no news from my staff is good news” for effective monitoring; active supervision is essential.
- How accountabilities operate in practice with third parties and within committee structures.
Organisational Role Analysis (ORA) can examine how people understand and perform their roles. Unclear R2A2 may contribute to a breakdown alongside staffing, incentives, or other weaknesses. A map needs to be checked against those conditions and against day-to-day work.
When to use it
Clarifying roles and accountabilities in a cross-functional team working on a high-stakes project.
Establishing clear separation of duties between executive roles during a corporate restructuring.
Mapping R2A2 for a regulatory compliance initiative to identify gaps in authority and resources.
Assessing third-party vendor responsibilities to ensure contractual accountability aligns with operational control.
Defining roles for a new cross-functional project
Clarifying accountabilities in high-risk compliance areas
Improving handover processes for key personnel
Resolving ambiguity between policy owners and business area managers
FROM THEORY TO EVERYDAY LIFE
In practice
CFO and CEO Separation of Duties
A company separates responsibility for financial reporting from authority to approve exceptions to financial controls. Its accountability map identifies who prepares reports, who reviews them, and who can authorise changes. The map supports oversight only if those arrangements operate in practice.
Policy Owner Without Authority
Suppose a policy owner is expected to oversee environmental compliance but lacks the budget or staff to address gaps across departments. Mapping accountability alongside authority makes that mismatch visible and gives managers a basis for resolving it.
Implementing a new compliance policy
A company introducing a data protection policy maps who drafts it, who approves it, who implements it in each department, and how staff report a suspected breach. It then checks whether staff understand those arrangements.
Project management handover
Before a project manager goes on leave, the team names a backup and specifies which decisions the backup can make. The handover also identifies issues that still need escalation.
A MOMENT TO REFLECT
Put it to work.
How can you ensure that R2A2 is clear for the most critical objectives and risks in your current project or organization?
What potential mismatches exist between accountability and authority in your role or team?
How might you use accountability mapping tools to surface differences in stakeholder perceptions of roles and responsibilities?
How clearly are roles and accountabilities defined in your current team or organization for critical processes?
Can you identify a recent situation where unclear R2A2 led to a problem? How could the framework have helped?
What mechanisms do you have in place to proactively detect when R2A2 becomes unclear?
CONTINUE THE CONVERSATION
Source texts
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)
- Beyond the Five Whys Root Cause Analysis and Systems Thinking (James C. Paterson)