RAID Log

RAID Log is an organizational Tool that helps professionals to identify and control Critical Factors in the projects they manage.

 

Its name is an acronym for the 4 Factors it Focuses on:

• Risks.
• Assumptions.
• Issues.
• Dependencies.

1. Risks: What could Compromise the Project.

• Possibility of new regulations.
• New Competitors.
• A Change in trend.
• etc.

 

2. Assumptions: What the Project takes for Granted without any Evidence.

• Economic Projections.
• Market Stability.
• Demand.
• etc.

 

3. Issues: Events that have Already occurred that affect or may affect the Project.

• A problem in the manufacturing line.
• A Supplier that have problems.
• An Increase in the prices of raw materials.
• etc.

 

4. Dependencies: What is Vital to Achieve for the Project to be Successful.

• A special license.
• The adequate professional team.
• Good packaging.
• etc.

RAID Log Factors

 

Let’s see the first example:

 

If you think your project may suffer setbacks, think about Space Missions.

• On a Space Mission, a small mistake costs lives and also a lot of money.

 

What would a RAID analysis look like for a space mission?

 

The actual analysis must be extremely thorough and detailed.

However, we’ll propose some simple Factors that could be included:

 

Risks

• Radiation can disrupt the navigation system.
• Collision with space debris.
• A small internal bubble in certain materials can cause some components to break.

 

* These events could take place but are difficult to foresee.

 

Assumptions

• The materials will behave and resist as always.
• The spacecraft will not collide with space debris.
• The crew will have no health problems.
• Communication Satellites won’t fail.

 

* These Points are taken for granted (we are sure that in reality, everything is perfectly checked).

 

Issues

• There will be a Storm the day of the launch.
• Sometimes the (toilet) flush system gets blocked.

 

* These events have been already confirmed.

 

Dependencies

• The Fuel tanks must not explode.
• The Navigation System must be accurate.
• The Air system must work perfectly.
• The Power System must not fail.
• The Heat Shield must resist.

 

* You can afford to have a problem with a particular software, or with the lab, but if any of these 5 points fails (Dependencies) the mission is over.

You may already have noticed something:

• It is very easy to have the same Critical factor in different Areas.

 

For example: In this last example you could have:

• Risk: A member of the crew could have a heart attack.
• Assumption: Everybody is, and will be healthy.

 

The last thing you want is to have duplicate points.

• Duplicate points mean duplicate work for the same conclusion.

 

This is why now, we will give you some Tips on How to develop a proper RAID Log Analysis:

One single person should be responsible for the entire RAID Log.

• He/ she will remember what has been already taken into account.
  • This way you’ll avoid  (or at least reduce) duplicate Points.

 

Start with the Assumptions.

• We all make certain Assumptions when developing a Project.
  • It is better to highlight them clearly at the beginning.

 

Take some extra time to find the Dependencies.

• The Dependencies can be very useful for finding the Real Flaws of your Project.
  • Risks on the other hand evaluate events that may not occur.

 

Leave Risks for the end.

• With all Issues, Assumptions and Dependencies in front of you, it will be much easier to identify the Risks of your Project.

Once the Critical Factors have been identified, you can use the FMEA process to solve them.

• If you are interested about it, check our “FMEA Process” Page.

The RAID log is solely focused on identifying them.

 

Now, let’s look at some examples to give you a better understanding of how RAID Log works:

To give you a better understanding of how to use the RAID Log, let’s imagine that you are starting your own Project.

• You’ll Open your own Restaurant.

Your Restaurant will be specialized in Italian food.

 

As you are a very methodical person, you decide to use the RAID Log.

 

Let’s see How it looks:

 

For your Italian Restaurant, you’ll Assume that:

• People in your Town like Italian Food.
• Your town is not saturated with Italian Restaurants.
• You can offer something new or better.
• Your Suppliers will keep their quality and prices.

 

While you are launching your New Restaurant you find out that:

• Someone is going to open a Mediterranean Restaurant in your town.
• As you are in the US, you won’t be able to offer certain products (cured meat, certain cheeses…).
• Finding all the employees you need is not easy, specially a Chef and good waiters.
• People in your town don’t love red wine so much.
  • A large portion of your revenue would come from wine.

 

To have a successful restaurant, you need:

• A Restoration License.
• A Good menu that offers something new or/ and better.
• Pizzas: Many people love pizza, so like it or not, you have to offer pizza.
• A Properly Decorated restaurant.
  • You won’t have a fast food restauran so, you need to diferentiate.

 

After thinking about it carefully, you believe that the biggest risks your restaurant may face are:

• The Demand can be lower than you expected.
• If you are successful, other people can open new Italian restaurants.
• People may not like the new dishes you plan to offer.
• Being associated with just a “Pizza restaurant“.
  • If this happens, your prices will be compared with those of fast food.

RAID Log is an organizational Tool that helps professionals to identify and control Critical Factors in the projects they manage.

 

Its name is an acronym for the 4 Factors it Focuses on:

• Risks: What could Compromise the Project.
• Assumptions: What the Project takes for Granted without any Evidence.
• Issues: Events that have Already occurred that affect or may affect the Project.
• Dependencies: What is Vital to Achieve for the Project to be Successful.

 

Tips on how to develop an effective RAID Log Analysis:

• One single person should be responsible for the entire RAID Log.
• Start with the Assumptions.
• Take some extra time to find the Dependencies.
• Leave Risks for the end.