Picture a product launch that went wrong. Not because the product was bad. Not because the team lacked talent. It went wrong because three different people thought they were responsible for getting legal sign-off, and none of them actually did it. The marketing team found out about the delay only when the launch date had already been announced to customers. Senior leadership found out when a customer complained.

Nobody was lazy. Nobody was incompetent. The project simply had no clarity about who was supposed to do what, who had the final say, who needed to be asked before decisions were made, and who simply needed to know what was happening. This is the most common failure mode in projects of every size, not a skills problem, but a clarity problem. RACI exists to solve exactly this.

RACI is a framework for assigning roles and responsibilities on any task or project. The letters stand for:

• R, Responsible — the person who does the work.
• A, Accountable — the person who owns the outcome and answers for it.
• C, Consulted — people whose input is sought before or during the work, a two-way conversation.
• I, Informed — people who are told what is happening, a one-way update.

These four roles, applied consistently across a project, remove the ambiguity that caused the product launch story above to go wrong.

RACI is also known by a more formal name, the Responsibility Assignment Matrix, or RAM. The "matrix" part refers to how it is typically displayed: tasks listed down the side, people or teams listed across the top, and each cell in the grid filled with one of the four letters. This visual format is what makes RACI so effective, a complex project with dozens of tasks and many stakeholders can be summarised in a single page that anyone can scan and understand in minutes.

Think about what happens when roles are unclear on a project.

Duplicated effort. Two people quietly do the same task because each assumed the other was not doing it, or neither assumed anyone was doing it so they both stepped in defensively.

Dropped tasks. The opposite problem, everyone assumes someone else has it covered, so nobody actually does it. This is precisely what happened in the legal sign-off story above.

Decision paralysis. When it is unclear who has the authority to make a call, decisions get stuck in endless discussion because nobody feels they can simply decide and move forward.

Conflict. When something goes wrong, and nobody was clearly accountable, the natural response is finger-pointing. This damages trust within a team far more than the original mistake did.