RAID stands for Risks, Assumptions, Issues and Dependencies and a RAID log tracks these key aspects for every project. The entries in the log at the start of the project almost certainly will not be the same as at the end of the project because it’s likely that not all of these critical components of project success are known at the start. It is important that your log is updated regularly – at the very least after team meetings – and that everyone involved has access to the latest version.
Let’s look at each element in detail:
Risks
We’ve all heard the phrase attributed to Benjamin Franklin: “Failing to plan is planning to fail” and the risk part of your RAID log should be where much of that planning takes place.
A risk is an action or event that could negatively affect the project, together with the likelihood that it will happen. Likely events need contingency plans, also contained in the log, which will be put into action if, or when, the event occurs. Remember that not all risks can be predicted at the outset of a project and may only become apparent as tasks are completed or defined in more detail.
Assumptions
Everything we do as project managers is based on a set of preconceived ideas – assumptions. By writing down what has been assumed about the project we can ensure that everyone has the same set of preconceived ideas. But that’s easier said than done. One of the greatest project management skills is being able to identify hidden assumptions. These are aspects of a projects that seem so obvious to some people that they don’t even think to mention them. You will need to clearly document every assumption, why you have made that assumption and any tests you need to perform to ensure that the assumption is, in fact, a valid one.
Issues
The risks section is the planning – the issues section lists when a problem or difficulty has occurred so that the damage caused by the issue can be minimised. Seemingly small issues, such as running out of stock of something or a key member of the team being ill, can quickly snowball into major issues if not dealt with in a timely manner. Issues need to be identified through a formal risk management process, their impact assessed and a note made of actions being taken to remedy the issue.
Dependencies
The final section of a RAID log lists everything that the project hinges on and (importantly) vice versa. Your work will affect others in the same way that their work affects you. The log contains notes on who you are dependent on, what you are expecting them to provide you with and when that will be. A comprehensive RAID log also includes what aspects of the project you are providing others and when.
Benefits of a RAID log
Your RAID log is a snapshot of the project. Should a stakeholder want a report on the project status you should be able to create one quickly using the log. And this is where the greatest benefit lies – a RAID approach keeps all the data on project progress together in one easy to analyse file meaning, as a project manager, you don’t have to seek out team members or dig around to find answers.
Good maintenance of the log allows you to use it to direct project planning. It gives you an insight into the future and allows you to schedule efficiently. It also ensures that nothing is forgotten, overlooked or assumed without good reason.
