So I have started documented all risk related issues in a RAID log. I am showing my stakeholder it weekly, so that he is aware of all product related risks, but not sure if there is much value in doing so?
What do you think?
Project Management Stack Exchange is a question and answer site for project managers. It only takes a minute to sign up.Sign up to join this community
The purpose of the log is to keep you, as the PM, and your team on the same page as to the high priority things on which you are working. It is not a communication vehicle. To communicate with it means you need to scrub it and make it customer/stakeholder ready. You will end up working on the log as if it were a product of and in itself and that is not what it is supposed to be for. Who cares if the log is ugly, with spelling errors, grammar errors, etc. But you would care if you have to "deliver" it.
Extracting the elements in the log and communicating it out in other communication vehicles--weekly reports, monthly reports, audit analysis, etc.--is not only a good thing but is your job. And of course, exposing or hiding information based on the stakeholder is a political action you need to consider, too. Be transparent but be smart about it.
In my experience, there is certainly value in keeping a RAID log, and making it accessible for project stakeholders to view. However, I wouldn't take it to them weekly unless specifically requested to do so. At most I'd send them a link to it, or attach it in my regular project update emails, and then they can choose to view it or not if they have the time/inclination to do so.
The exception to this would be if I came across a major risk, but then I would flag it independently of the RAID log to the stakeholders, and document it in the log also.
TL;DR: Give them the choice by making it accessible.
Depending on the current state of your project, the frequency of you sharing RAID Logs with your stakeholder depends, IMHO.
In an average project, risks may not need review each week, but in a high-risk project the risk log may need to be reviewed more often. Each project has a different makeup, which should dictate the frequency with which each category in a RAID log needs to be considered & discussed.
Based on the current state of your project, and also based on how your customer is "perceiving" the project state, you can determine if showing RAID logs is adding any value or not.
If your customer is asking you to discuss "weekly" these RAID logs, then I suggest you should properly prioritise your RAID Log items. Make sure to discuss high priority RAID Log items upfront such as High risks, important dependencies etc.