The RACI framework

Have you ever went through projects and forgot who to include and who to inform about different stages? Have you ever experienced stakeholders not feeling included? Or ever stopped and asked yourself, did I forget to talk with someone?

That’s when and where the RACI framework will help you out! I use it consistently and always draft it up before starting a new project and for me, it’s been a lifesaver at times.

This week I’ll walk you through the framework, how to create a RACI chart, and how to avoid common pitfalls. I’ll also share how I use it to manage RevOps projects effectively.

What the RACI framework is

RACI is an acronym that stands for:

• Responsible: The person or people who do the work to complete the task.

• Accountable: The person who owns the task and ensures it’s completed successfully.

• Consulted: Stakeholders whose input is required before moving forward.

• Informed: People who need updates but don’t contribute directly.

For example, if you’re rolling out a new CRM system, the Responsible person might be the operations specialist configuring the tool, the Accountable person could be the RevOps lead overseeing the project, the Consulted group might include sales managers providing requirements, and the Informed group might be the executive team awaiting updates.

It’s important to remember that one person could be wearing multiple hats, so one person is not limited to only be sorted into one of the letters. For instance, the person being responsible could also be the accountable person.

How to create a RACI chart

Creating a RACI chart is straightforward:

1. List tasks: Break down the project into individual tasks or deliverables.

2. Identify roles: For each task, assign individuals to the RACI categories.

3. Validate: Review the chart with your team to ensure everyone agrees on the roles.

4. Use visual tools: Tools like Google Sheets, Excel, or project management software can help visualize the chart.

Here’s an example for a RevOps project like onboarding a prospecting tool:

Structuring the RACI framework before starting the project is a great way to really think though who the stakeholders are and who the decision makers are. But it’s also a great way to start thinking about what different stages the project has and how you should progress through it. If you’ve done this before the project kicks off, you’ll always have the blueprint to look back at and to help you steer the project forward.

For me, I see it as a flexible framework, meaning that I do adjust it over the length of the project as needed. So don’t see it as set in stone once you done the first draft, let it be an iterative process.

The chart can either be something you keep for yourself to as your own steering material or it can be a shared document that people in the project can refer to. If you use it as a shared document I’d strongly advise have a single person responsible for the document and also being the sole editor of it. If multiple people edit it over time, it can quickly be hard to keep track of and then it can loose its decisiveness as a steering tool.

Benefits of using the RACI framework

I’ve already touched upon some of the benefits I see but to sum it up

• Clarity: You, or everyone, knows their role, making it easy to always know who to include and in what capacity.

• Driving the project forward: When in doubt, you can always look back at the plan set out in the document to know what to do next.

• Efficiency: Avoids bottlenecks and accelerates decision-making.

In RevOps, where collaboration is key, RACI can bridge the gaps between departments, ensuring smoother execution of initiatives.

Common pitfalls and how to avoid them

• Overcomplicating the chart: Keep it simple. Too many roles per task can create confusion. As well as too detailed tasks firstly makes it hard to predict all tasks needed to completed the project and will make you spend way too much time on drafting the RACI chart.

• Assigning multiple Accountable roles: Each task should have just one person accountable.

• Failing to revisit the chart: Projects evolve—ensure the RACI chart is updated accordingly.

• Skipping stakeholder alignment: Ensure everyone involved understands and agrees to their roles. OR if you use it for your own guidance, make sure you don’t assume wrongly about anyones involvement.

How I use the RACI framework

In my role, I’ve used the RACI framework to manage almost all projects, as long as they aren’t very small ones. Recently, while selecting a prospecting platform, I used a RACI chart to clarify who was responsible for gathering requirements, accountable for the final decision, and consulted during the evaluation process. If you haven’t read it already, here’s how I structured that project. Having the framework, with people involved and stages of the project defined, helped me move the project forward and made sure that key stakeholders felt involved throughout the process.

If you haven’t used it before, give it a try!

If you enjoy my writing and want to support this newsletter, consider buying me a coffee

Cheers

Erik