liveBook · Manning

RACI matrix

As explained in Think Like a Software Engineering Manager

RACI is a responsibility assignment matrix that specifies who is Responsible, Accountable, Consulted, and Informed for project work.

A project can have the right mix of engineers, designers, testers, and domain experts yet still lose time when ownership is unclear. A RACI matrix is a responsibility assignment chart that identifies who is Responsible, Accountable, Consulted, and Informed for project activities and deliverables. It sets expectations and helps prevent duplicated work. section 9.2.2

Put the chart to work:

  • Identify the project’s activities, deliverables, and participants, then assign RACI roles so ownership is visible. section 9.2.2
  • Include the roles in the communication plan alongside milestones, dependencies, channels, and update frequency. section 9.2.3
  • At kickoff, review the completed chart with stakeholders and get their signoff. section 10.1.3

Use “Informed” to protect meeting time

Someone assigned to the Informed category may not need to attend every meeting. They can catch up through meeting minutes instead. section 14.2.4

Figure 10.2 A sample RACI matrix for Project Accessible defines roles and responsibilities
figure

View a sample project RACI matrix as a model for making responsibilities visible before seeking stakeholder signoff. section 10.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Defines the acronym and describes assignment and stakeholder signoff, but does not specify rules for filling every chart entry.
Examples
Shows sample RACI charts and an Informed participant who skips meetings and reads the minutes.
What it assumes
Defines RACI from zero while assuming a project with identifiable participants, activities, and deliverables.
What you can do after
Practice/perform it: Assign roles to project work, seek stakeholder signoff, and use Informed status to avoid unnecessary meetings.
How it connects
Links responsibility assignment to cross-functional teams, communication planning, project kickoff, and time management.

Also explained in

Compare how 2 books explain RACI matrix →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.