A mid-sized company was redesigning its website. The Project Manager, a relatively junior team member, was told she was Accountable for the redesign. The lead designer, far more senior, with twenty years of experience, was marked Responsible for the actual design work.

At the first review meeting, the designer presented work that did not match the brief. The Project Manager pushed back and asked for changes. The designer, visibly uncomfortable, said: "You're telling me what to do? I have two decades of experience." The Project Manager held her ground. "I'm not telling you how to design. I'm accountable for this project meeting the brief and the deadline. That's my role. Your role is doing the design work, and right now it doesn't match what we agreed." This moment is exactly what RACI is designed to make clear before it becomes a conflict. Seniority does not determine who is Accountable. The task does.

The Responsible role belongs to whoever actually executes the task, the person or team with their hands on the work, writing the code, designing the materials, drafting the document, building the product. To be Responsible for something, you need two things: the skills to do the work, and the resources or time to complete it. Without both, assigning someone as Responsible sets them up to fail. There can be more than one Responsible person on a task, for example two developers pairing on a feature, but if a task has so many Responsible people that coordination itself becomes difficult, that is usually a sign the task needs to be broken into smaller pieces. Example: in a website redesign, the Web Development Team is Responsible for coding, testing, and launching the new site.

The Accountable person is answerable for whether the task succeeds or fails. They do not necessarily do the work themselves, but they ensure it gets done, meets the required standard, and is delivered on time. If something goes wrong, the Accountable person is the one who has to explain why.

Why does this matter so much? Because accountability that is shared between two people quietly becomes accountability that belongs to nobody. When something goes wrong and two people are both marked Accountable, each can reasonably believe the other was handling it. With one clear Accountable person, there is never that ambiguity. Example: in the website redesign story, the Project Manager is Accountable for delivering the website on time and within budget, even though she is not personally writing a single line of code or designing a single screen.