Use RASI to Define Responsibilities!

Use RASI to Define Responsibilities!

I frequently see the use of RACI and RASCI in defining responsibilities.? I have always found this confusing and every organization that I’ve work with has as well, so I use a different approach.

I prefer RASI to define the areas of accountability and responsibility for each given task, project, etc.? It enables people to define and understand who is Responsible, who Authorizes/Approves, who Supports, and who must be Informed while RACI stands for Responsible, Accountable, Consult, and Informed.? The "C" and the "S" are used the same way.? The difference is in how the "A" is defined.? With RACI and RASCI, it is defined as "Accountable".? This confuses people because it’s not clear the difference between Responsible and Accountable – in life, if you are responsible, you are also held accountable, so it is confusing (otherwise if I’m responsible and do poorly, someone else gets the blame, held accountable??).? I define them as "Responsible" and "Authorize/Approve" because if I'm responsible I need to know who authorizes or approves my work (i.e., who signs off) making the roles and responsibilities clearer.

RASI

I define the matrix at multiple levels, e.g., one level for a portfolio of projects, one for the project overall, and one for the tasks.? Matrices stack so in a project; the project manager is Responsible for the overall project (one level) whereas an analyst may be Responsible for one of the tasks (a lower-level matrix).? The four are:

  • R – Responsible – who is held Responsible for the success and completion of a given task, project, etc.? This who you might fire if it’s not done.
  • A – Authorizes/Approves – (Authorize before and Approve after) who signs off on the method or results of a given task, project, etc.? This is who you go to for permission to start or to approve completion.
  • S – Supports – who aids, provides information, etc., for a given task, project, etc. – if requested.? This is the same as Consults.
  • I – Informed – who must be kept informed of the progress or results of a given task, project, etc.

What this means…

  • There is one and only one R (responsible) per task, project, etc.? If two people are Responsible, who is held accountable?
  • There is at least one A (Authorizer or Approver) who is not R (Responsible), i.e., you cannot be both Responsible and an Approver (“I did it and I approve it.? Any questions?” – a slight conflict of interest).? There are frequently more than one Approver for any given task, project, etc. (I have seen up to nine Approvers for a project).
  • There are from zero to many S (Supports) but only if help is requested, i.e., you don’t have to ask for help.
  • There are from zero to many I (informed) but only if this person or organization MUST be kept informed (avoid just giving someone an “I” to fill in the matrix.? That’s called ‘junk mail.’).

Implications are:

  1. R implies A, S, I
  2. A implies S, I
  3. S implies I

I have always found RASI easier to explain and easier to understand.?

Have you tried RASI?


Adriana Páez Pino

Inteligencia Artificial en el Trabajo | Divulgadora de IA | Mentora Profesional | Diversidad y Género en STEM

3 个月

Excelente explicación, Gary. Me gusta cómo desglosas las diferencias entre RACI y RASI, especialmente la distinción entre "Responsable" y "Autoriza/Aprueba". Creo que la claridad que ofrece RASI al especificar quién autoriza y quién es responsable realmente facilita la comprensión y evita confusiones. Además, la forma en que defines los niveles dentro de la matriz para proyectos y tareas es muy útil para garantizar que todos los roles estén bien definidos. Definitivamente, RASI parece ser una herramienta más directa y fácil de aplicar.

Emilio Planas

Strategy, Strategic Thinking, Innovation, Sustainability, Circular Economy, Strategic Planning, Negotiation, Startups , International Trade, Supply Chain, Digital Business, Technology, Finance Management, Business .

3 个月

Gary, congratulations on another insightful article! Your breakdown of RASI provides a refreshingly clear and practical approach to defining responsibilities, addressing the confusion often caused by RACI and RASCI. Your emphasis on making roles unambiguous truly empowers teams to function more effectively and collaboratively. An additional insight worth exploring is how RASI can streamline conflict resolution within projects. By clearly defining who Authorizes and who is Responsible, teams can avoid disputes about decision-making authority or accountability, saving time and fostering a more cohesive working environment. This added layer of clarity enhances both trust and efficiency across teams.

Marcel Velica

Senior Security Program Manager | Leading Cybersecurity Initiatives | Driving Strategic Security Solutions | Cybersecurity Excellence | Cloud Security

3 个月

It's essential that we tailor our strategies to ensure everyone's roles are unambiguous, enhancing collaboration and performance. Gary Rush IAF Certified Professional Facilitator Master

要查看或添加评论,请登录

Gary Rush IAF Certified Professional Facilitator Master的更多文章

  • Mastering SWOT – a Methodical Approach

    Mastering SWOT – a Methodical Approach

    I teach and facilitate SWOT a unique way. I have seen typical SWOT quadrants and find them unfulfilling.

    6 条评论
  • Use RASI to Define Responsibilities!

    Use RASI to Define Responsibilities!

    I frequently see the use of RACI and RASCI in defining responsibilities. I have always found this confusing and every…

    7 条评论
  • JAD, FAST, FoCuSeD?…

    JAD, FAST, FoCuSeD?…

    JAD (Joint Application Design)… In 1979, JAD was created. (In 1979, Chuck Morris of IBM Raleigh, and Tony Crawford of…

    4 条评论
  • Pursuing Dreams

    Pursuing Dreams

    I’m not talking about those you have when you sleep. I’m talking about the pursuit of happiness.

    5 条评论
  • Wow… 40 Years in business and Still Going…

    Wow… 40 Years in business and Still Going…

    We started MG Rush Systems, Inc. now MGR Consulting, Inc.

    10 条评论
  • Building a Data Warehouse following Agile Concepts

    Building a Data Warehouse following Agile Concepts

    Many data warehouse projects take a long time to complete. Often, companies who are implementing Agile skip some of the…

    4 条评论
  • Reaching Consensus Delivers Better Outcomes

    Reaching Consensus Delivers Better Outcomes

    I’ve been thinking about collaboration since it is core to what I do in Facilitation. I believe that decisions made by…

    7 条评论
  • Working with People Problems…

    Working with People Problems…

    People can be difficult. People cause problems only for a certain time.

    3 条评论
  • What’s an IAF Certified? Professional Facilitator (CPF)?

    What’s an IAF Certified? Professional Facilitator (CPF)?

    On my LinkedIn profile, I am “Gary Rush, IAF CPF | Master”. I’ll bet that a lot of people have no idea what “IAF CPF |…

    7 条评论
  • You’ve been Brainstorming the Wrong Way

    You’ve been Brainstorming the Wrong Way

    I’ve been reading several posts that talk about Brainstorming that cast a shadow over its use and effectiveness. The…

    11 条评论

社区洞察

其他会员也浏览了