{"id":505,"date":"2015-09-26T13:52:02","date_gmt":"2015-09-26T18:52:02","guid":{"rendered":"http:\/\/waife.com\/home\/?p=505"},"modified":"2016-06-14T14:15:42","modified_gmt":"2016-06-14T19:15:42","slug":"erase-raci-clinical-researcher-october-2015","status":"publish","type":"post","link":"http:\/\/waife.com\/home\/erase-raci-clinical-researcher-october-2015\/","title":{"rendered":"Erase RACI (Clinical Researcher, October 2015)"},"content":{"rendered":"

\u201cRACI has met the common fate of other time-worn jargon: it is now misused, misunderstood, and misleading.\u201d<\/em><\/p>\n

\"Fingers-pointing-blame-to-man\"<\/a>One of the operating assumptions widely used in biopharma process analysis is the \u201cRACI\u201d model. RACI stands for Responsible, Accountable, Consulted and Informed, referring to what role any particular person, job or department has in a particular project or process. The point of RACI is to provide a handy structure for teams or complex organizations to sort out, and document clearly, who is going to do what. But RACI has met the common fate of other time-worn jargon: it is now misused, misunderstood, and misleading.<\/p>\n

Unless you are a sapphire-belt sixty-sigma facilitator, the RACI model has long outlived its usefulness. Flawed at birth, its failings are ever more manifest. And yet the RACI model lives on like Tang on the Space Station.<\/p>\n

Perhaps you have never heard of the RACI model, in which case you have been spared. Each component of the model, in actual use<\/u><\/em><\/strong> today (not as it was originally conceived) is problematic. It is not enough to say, \u201cwell, people just aren\u2019t using it correctly.\u201d If the original definitions are forgotten or are no longer intuitive, then it\u2019s the model, the language, that has to change. This is important for two reasons: the purpose of the RACI model is still a compelling notion \u2013 not everyone involved in a process has the same responsibilities (lower case \u201cr\u201d!). But further, the misuse of the individual R, A, C, I words contribute to the opposite effect: people misunderstanding<\/u><\/em><\/strong> their responsibilities, not least because the labels are made somehow holy by the jargon. And the cost of this mistake is that reams of SOPs and other control documentation is created using the RACI model, which is then auditable, and more importantly, adds complexity and time to the very processes we are trying to make more efficient.<\/p>\n

Let\u2019s look first at the \u201cR\u201d and the \u201cA\u201d. \u201cR\u201d is supposed to be, in the model, the person who does the work \u2013 a worker, a doer. Almost no one understands this correctly. The letter R is defined as standing for \u201cResponsible,\u201d but the word<\/u><\/em><\/strong> responsible, to almost everyone, means the person who is in charge, who is supposed to lead the work, whose head will roll if things go wrong. Sorry, in RACI that is the definition of the \u201cA\u201d word \u2013 \u201cAccountable\u201d. Everyone we\u2019ve ever worked with to try and use RACI, or has already had RACI imposed on them, confuses the R and the A, to the point where deciding who is R and who is A becomes arbitrary, and therefore meaningless. Most importantly, things that are confusing, contradictory or illogical become unmemorable<\/u><\/em><\/strong>, and that makes the whole RACI effort a costly waste.<\/p>\n

The \u201cC\u201d and the \u201cI\u201d are also flawed. Can there be any less sincere roles for people than who is \u201cConsulted\u201d and who is \u201cInformed\u201d? The time spent delineating the C and the I in the standard RACI workshop is not only time wasted, it is the opportunity for more misleading behavior. Too often, people labeled \u201cC\u201d are people who actually should be doing something but don\u2019t want the responsibility. They are mollified with the C, as are those who don’t want to do anything but want to be able to express an opinion about what others are doing. Should we be officially codifying such wasteful and passive-aggressive behavior? And what about \u201cInformed\u201d? Unless you\u2019re working in the NSA, is there anyone who shouldn’t be informed, and is there anyone who needs to be officially informed they qualify for this obvious, passive position? The \u201cC\u201d and the \u201cI\u201d are simply a fancy justification for the phenomenon I call \u201ceverybody into the loop!\u201d, i.e., if you aren\u2019t actually responsible for anything, we don’t want you to feel left out, so we will keep you \u201cinformed,\u201d and if you\u2019re someone we\u2019re afraid of, we will make sure you are \u201cconsulted\u201d. This is much like everyone on the kids\u2019 soccer team getting a trophy for \u201cparticipation\u201d. Maybe we could give everyone on the project team a trophy at the first meeting and then disinvite them for the rest of the project! I can see that my replacement for RACI should be \u201cRDT\u201d \u2013 Responsible, Doing something, gets a Trophy.<\/p>\n

Because of these misunderstandings, the worst aspect of using RACI in real life is that no one is actually assigned to do any work! You can be the one who is blamed (RA), you can be the one who gets to kibbitz (CI), but no one is assigned to do anything specific, which was the original point.<\/p>\n

 <\/p>\n

There are only two roles worth delineating when designing clinical development processes: the person who governs the work, and the person who does the work. If you are re-defining or creating new processes in your research organization, there are many other techniques other than RACI that will clarify responsibilities. Stick to the two categories: Govern, and Do. If someone or some function falls into neither bucket, they get the trophy and can go home. Finance? See you at budget time. Quality Assurance? You have your own chance to Govern and Do in QA processes. IT? Make sure the intranet is working.<\/p>\n

It\u2019s very important to clarify roles in the multiplexed world of clinical development. The key is to clarify for the sake of simplicity, not for the sake of inclusion. Productivity over Ego; Govern and Do. Erase the RACI and get back to working smarter.<\/p>\n","protected":false},"excerpt":{"rendered":"

\u201cRACI has met the common fate of other time-worn jargon: it is now misused, misunderstood, and misleading.\u201d One of the operating assumptions widely used in biopharma process analysis is the \u201cRACI\u201d model. RACI stands for Responsible, Accountable, Consulted and Informed, referring to what role any particular person, job or department has in a particular project or process. The point of RACI is to provide a handy structure for teams or complex organizations to sort out, and document clearly, who is going to do what. But RACI has met the common fate of other time-worn jargon: it is now misused, misunderstood, and misleading. Unless you are a sapphire-belt sixty-sigma facilitator, the RACI model has long outlived its usefulness. Flawed at birth, its failings are ever more manifest. And yet the RACI model lives on like Tang on the Space Station. Perhaps you have never heard of the RACI model, in which case you have been spared. Each component of the model, in actual use today (not as it was originally conceived) is problematic. It is not enough to say, \u201cwell, people just aren\u2019t using it correctly.\u201d If the original definitions are forgotten or are no longer intuitive, then it\u2019s the model, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[50,54],"tags":[],"class_list":["post-505","post","type-post","status-publish","format-standard","hentry","category-recent-columns","category-recent-postings"],"_links":{"self":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts\/505","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/comments?post=505"}],"version-history":[{"count":1,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts\/505\/revisions"}],"predecessor-version":[{"id":506,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/posts\/505\/revisions\/506"}],"wp:attachment":[{"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/media?parent=505"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/categories?post=505"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/waife.com\/home\/wp-json\/wp\/v2\/tags?post=505"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}