Jump to content

Talk:Responsibility assignment matrix/Archive 1

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Philoserf (talk | contribs) at 17:11, 30 December 2022 (OneClickArchiver adding A is for Approver?). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.
Archive 1

Variations

The final sentence of the Methodology section mentions a "Variations" section but there is not one present. Suggest removing this part for the timebeing to avoid confusion. If someone has variations on the definitions, they can add them later on. — Preceding unsigned comment added by 70.79.128.249 (talk) 18:08, 18 October 2007 (UTC)

Versions and Category

I added the Versions information in from the page history and added the category back to the page. For the individual who removed that information, if you feel that it does not belong with this page information please give a reason. The version information is valuable and the Category of Project Management is appropriate. Thanks. JOE-- —Preceding unsigned comment added by 199.90.35.11 (talk) 16:45, 23 October 2007 (UTC)

A is for Approver?

I got some feedback that A is for Approver.  ?? --64.214.85.60 (talk) 16:23, 31 January 2008 (UTC)
--12.10.219.38 (talk) 20:39, 19 August 2008 (UTC) In essence, the original scheme has a single "Accountable" but can have several "Responsible"; this can cause confusion over the difference betwween definitions. Changing "Accountable" to "Approver" helps to clarify that. However, the alternative scheme defined here removes the two-tier responsibility at the task level and specifies that, for each task, one person is responsible for its execution; they may be assisted by others and will need to communicate (two-way "Consultation" and one-way "Inform"). Where a higher authority is needed to approve a task, that is added as a subsequent task where approver/authority is "Responsible". It may sound cumbersome but, if applied consistently, it works well.Steve @ Aberdeen <>< (talk) 08:28, 6 June 2008 (UTC)
To remove the problem of A meaning Accountable and R meaning Responsible, which can cause confusion. Have you heard of the alternative system ADICO? A= Accountable (accountable for the completion of the activities, able to commit resources for completion), D= Does it (actually does the work), I= Informed(one way conversation), C= Consulted (2 way conversation), 0= zero or not required for the activity.Fredsocks (talk) 21:07, 16 May 2009 (UTC)

Not heard of this one before. If you can find some references for it, you should include it. Greyskinnedboy (talk) 19:40, 17 May 2009 (UTC)

Approvers and those Accountable for ensuring an activity is completed are not synonymous. For example, the Project Manager is tasked with ensuring the project and all artifacts within it are completed and approved. In the case of approver, three could be many that need to sign-off and they are most likely cross departmental. For example, the project manager is "Accountable" for ensuring a requirements document is created and approved by all required stakeholders--One of which is the Project Business Sponsor. Other approvers might include VP Marketing, CFO, Legal etc... and therefore you would not list all of them in the RACI since only one role gets the "A". User:Goldy —Preceding unsigned comment added by 24.12.147.177 (talk) 20:51, 26 August 2010 (UTC)


Concur with above ... Accountable discusses 3 roles : "approving authority", "the one ultimately answerable" and "the one who delegates" they are not necessilary synomonus.