Overview
The RACI framework is a tool used for clarifying roles and responsibilities within a project or organization. The acronym RACI stands for Responsible, Accountable, Consulted, and Informed. These four designations are used to define the level of involvement and responsibility for each person or group involved in a project.
- Responsible (R): The person or team who is supposed to βdo the workβ of completing the task.
- Accountable (A): The person who is ultimately in charge of the task's success. The buck stops with them when it comes to the task.
- Consulted (C): Someone who is tapped by the responsible party for guidance or advice on the task. They may provide input or feedback on the task but are not responsible for its completion.
- Informed (I): A person or team who is kept informed of the task's progress or outcome. They are not responsible for the task's completion but may need to know its status for their own work.
All tasks must have a single person who is Responsible, and a single person who is Accountable. Sometimes that is the same person. Tasks can have any number of Consulted and Informed people, or none at all.
The people involved with tasks, projects, and even organizations can be categorized using this framework. This is helpful to know who is in charge and who needs to do what.
In our Production team, here are common types of work and the typical RACI assignments for each.
This chart outlines the RACI for typical design/dev work within the Production team. Obviously, for other kinds of work, other roles would hold responsibility.
Work | Responsible | Accountable | Consulted | Informed |
---|---|---|---|---|
Understanding the clientβs business, regularly reviewing their metrics, and making proactive suggestions | π€ Strategists | π€ Strategists | π§ββοΈ PMs | π©π½βπ» Designers/Devs |
Gathering client goals/problems, proposing solutions, writing specs/SOWs | π€ Strategists | π€ Strategists | π§ββοΈ PMs | π©π½βπ» Designers/Devs |
Running meetings, taking notes, sending action items | π§ββοΈ PMs | π€ Strategists | π©π½βπ» Designers/Devs | |
Monitoring overall project budgets, invoicing | π§ββοΈ PMs | π€ Strategists | π©π½βπ» Designers/Devs | |
Creating, clarifying, and scheduling Tasks | π§ββοΈ PMs | π€ Strategists | π€ Strategistsπ©π½βπ» Designers/Devs | π Sprint Owner |
Initial task assignment (within Core Team) | π©π½βπ» Designers/Devs | π§ββοΈ PMs | π Sprint Ownerπ€ Strategists | |
Contributor task assignment (when Core Team is not the best choice) | π§ββοΈ PMs | π§ββοΈ PMs | π Sprint Ownerπ€ Strategists | |
Completing design/dev work on spec, on time, and on budget | π©π½βπ» Designers/Devs | π§ββοΈ PMs | π§ββοΈ PMsπ€ Strategists | π Sprint Owner |
Delivering weekly internal & client updates | π§ββοΈ PMs | π€ Strategists | π©π½βπ» Designers/Devs | |
Managing project software tools (Harvest, Asana, etc) | π§ββοΈ PMs | π§ββοΈ PMs | π€ Strategists | |
Managing production team software tools | π Sprint Owner | π Sprint Owner | π§ββοΈ PMsπ€ Strategists | π©π½βπ» Designers/Devs |