When documents are used to track project information, a common approach is to create a consolidated workbook in MS Excel for tracking risks, actions, issues and decisions. This is usually referred to as a RAID log.
The benefit of this approach beyond having the information in a convenient, centralized location is that there are logical relationships between these disparate elements which can be easily reflected if they are consolidated. For example, negative risks which have not been successfully avoided could be realized as issues. In turn, issue resolution might be done via actions. And finally, actions may require formal decisions to be taken.
But is there an opportunity to consolidate additional list-based project data elements for greater benefit, and if so, what are some good candidates?
We frequently hear about the need to capture assumptions made by stakeholders when planning our projects so that they can be validated over time. A benefit of having the assumptions consolidated in the same workbook is that part of a regular risk register refresh could include a quick walkthrough of those assumptions which have not been validated yet to see whether any new risks can be identified or whether information regarding existing risks should be updated.
It’s rarely ideal to wait till the very end of a project to harvest knowledge. But if you choose to identify lessons regularly over the life of your project, they’ll have to be captured somewhere. As issues are often a good input into lessons identification, having the ability to link issues to a lesson will simplify the process of understanding the context behind the lesson. Another benefit of this approach is that since it’s common practice to review issues and actions in regular team meetings, having lessons also available in the same document might encourage team members to review them and identify new ones.
Finally, let’s consider stakeholders. We know that it’s a good practice to identify stakeholders early in your project, analyze them according to their impact, interest and influence, and use that information to form your engagement and change strategies. Stakeholders will be closely associated with all of the other data elements we’ve looked at so it’s likely worth including your stakeholder register too.
So if your organization doesn’t have a central project management information system, why not use a RADIALS log in place of a traditional RAID log!