RAKI is a responsibility and communication matrix to clearly assign roles for tasks, decisions, and deliverables (closely related to RACI/RAM).
RAKI is used to define, for tasks, decisions, or artifacts, who executes (R), who is ultimately accountable (A), who must be consulted (K/C), and who needs to be informed (I). This reduces ambiguity, duplicate work, and decision bottlenecks. In practice, RAKI is functionally equivalent to the widely used RACI/RAM model (Responsible, Accountable, Consulted, Informed) and is commonly applied in projects, governance structures, and organizational interfaces.
Time from decision submission to final decision (A).
How often decisions require escalation due to unclear responsibilities.
Effort caused by unclear responsibilities (e.g., duplicated implementation).
A company uses RAKI to define for ADRs who performs the analysis (R), who makes the final call (A), which experts are consulted (K), and which teams are informed (I).
RAKI makes it transparent who is responsible for shared interfaces and who must be involved for changes.
RAKI helps agile teams to clearly define responsibilities and improve communication paths.
Define scope: Which tasks/deliverables/decisions are covered?
List roles/stakeholders and align on role meaning
Assign RAKI per item and facilitate conflicts (A is critical)