Project Management Central

Please login or join to subscribe to this thread
How detailed should your RACI table be?
Network:710



The RACI table (R: Responsible A: Accountable C: Consult I: Inform) helps in outlining the roles your stakeholders play within a project.

1. How details should the activities on the left column be?
2. Should all the project activities be listed there or majorly the high-level summary activities or strategic needs of the project?
Sort By:
Page: 1 2 next>
Network:360



RACI should not be too detailed as it is a management tool for decision making and roles clarification.
High level activities should be listed there. There will be always "grey" areas to be clarified during execution but the basis should not be ambiguous.
Network:69890



I totally agree with Philippe.
Network:72897



I usually don't go to the activity level in my RACI. I find the work package is sufficient to capture the roles and responsibilities
Network:1389



Agree with the sentiments above ..... Too much detail leads to unnecessary overhead and confusion. Tell the story with less words.
Network:3581



KISS method works best.Keep it Simple so it will actually be used.
...
2 replies by Rami Kaibni and Vincent Guerard
Mar 15, 2017 3:09 PM
Rami Kaibni
...
Interesting Liana, it is the first time I hear about this method.
Mar 16, 2017 3:52 PM
Vincent Guerard
...
I love KISS principle
Keep
It
Simple,
S.....a fee option there
(https://en.wikipedia.org/wiki/KISS_principle)
Network:69890



Mar 15, 2017 3:07 PM
Replying to Liana Underwood
...
KISS method works best.Keep it Simple so it will actually be used.
Interesting Liana, it is the first time I hear about this method.
Network:9130



I agree with Liana, Stéphane, and Philippe's comments. This makes sense.
Network:1173



Do not make it cluttered, as mentioned by Liana you need to keep it simple. Have high level entries.
Network:92



I agree with the simple and at the work package level.
I typically:
- Define most of the Responsible from the Deliverables/Work packages defined
- Most of the Accountable from the milestones defined as "Sign-off", "Decision"... As well as the risks owners from risk registry or their direct managers (i.e. think about the steps you would follow in case a risk realizes)
- Most of the Consulted from Project Sponsors, Project Steering Committee, PMO, other Project related teams (e.g. Risk Team if there is any in your Organisation) and Subject Matter Experts. Consider also risk registry (who you would reach out to if a risk or an issue happens) and who should be making the decisions in your project. This one really depends on your Organization.
- Most of the Informed from above. Again, this one really depends on your Organization.
- I use groups or roles versus individual names when it makes sense, refer to Stakeholder Registry when relevant.
Hope it helps,
Marisa
Network:76575



Mar 15, 2017 3:07 PM
Replying to Liana Underwood
...
KISS method works best.Keep it Simple so it will actually be used.
I love KISS principle
Keep
It
Simple,
S.....a fee option there
(https://en.wikipedia.org/wiki/KISS_principle)
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

"The power of accurate observation is often called cynicism by those who don't have it."

- George Bernard Shaw

ADVERTISEMENT

Sponsors