Importance of Enterprise Risk Management (ERM)

July 10, 2019


Enterprise Risk Management:

In many projects, risks are identified and analysed in a random, brainstorming, fashion. This is often fatal to the success of the project, as unexpected risks arise, which have not been assessed or planned for and have to be dealt with on an emergency basis, rather than be prepared for and defended against in a planned, measured, manner. Very early in the preparation and planning stage, it is essential that potential risks are identified, categorized and evaluated. There are many factors that make risk management important.

Why Is Enterprise Risk Management (ERM) Important?

  • Organizations start an endeavour to take a business opportunity. There is uncertainty about the organization will take the opportunity or not. So each endeavour has an associated risk. That is because ERM is important.
  • Organizations need to increase their risk taking capability to cash on the opportunities that keep knocking at their doors. With robust ERM, organizations can identify and analyse risks and decide which risk is worth taking.
  • Projects can only control risks and opportunities directly within their remit. Yet, the performance of a project is very much dependent upon the obstacles thrown up by the enterprise or organization and other external influences, which are outside the projects control.
  • Enterprise Risk Management (ERM) is important because its success determines the health and life of the business enterprise. If an organization fails to identify risks to its existence, it will be ill prepared to face any risk events. As an example, business enterprises recognize that dependency on a sole source supplier is a high risk (if that supplier goes out of business your business will be impacted). Therefore, they identify that risk and address it by developing multiple sources so reducing that particular risk. In the same way that risk is managed in projects to increase its probability of success, risk must be managed in an enterprise to assure its success.
  • ERM institutionalizes risk management procedures in the organization by standardizing the tools, methodology and people processes in monitoring individual project risks. This is important so that the impacts of individual project failures (in case failures do happen) are addressed appropriately.

Most sources of information about Enterprise Risk Management focus on the need to be proactive instead of reactive. The old saying “an ounce of prevention is worth a pound of cure” is right on target when it comes to planning for risk. To put ERM in its simplest form it means learning to expect the unexpected. It means that you, the project manager, must start your team thinking about risk situations, prevention ideas and “what if” scenarios at the start of project planning, not when an incident occurs.

Risks exist with all projects. Accordingly, you should always consider what might go wrong by identifying, qualifying and quantifying risks. The best way to do so is to work with your project team and a person or two from outside the project to brainstorm concerns about what possibly go wrong. When you have a list of potential risks, next determine risk value by multiply the total cost by the likelihood percentage, and you will get your factored risk value:

  • Costs to each one of your risks
  • The total cost impact if the risk occurred
  • The cost to mitigate against the risk
  • Probability of occurrence to each one of your risks. you can simply factor it out with a low percentage score)

The factored risk value should be added to your initial estimate. For risk items that are highly likely to occur, add those full costs to your initial estimate. There’s no point in lowering your estimate on the basis that you’re hoping for the best outcome. Here is an initial checklist of key potential risks that may relate to your project.

Requirement Risks

  1. Were key stakeholders not available or excluded during requirements definition?
  2. Is delivery of requirements being performed by an outside provider?
  3. Was the formal sign-off of requirements eliminated?
  4. Was the stakeholder analysis skipped?
  5. Have new requirements been identified since project kick-off?
  6. Can any of the new requirements affect scope?
  7. No WBS dictionary exists?
  8. Is there a high probability that the sponsor (or another significant stakeholder) could change?

Resources Risks

  1. Is it a key Resource?
  2. Is there the potential for a long-term absence?
  3. Do we not have suitable replacements?
  4. Is the resource assigned to the critical path tasks?
  5. Does the vendor have higher priority clients?
  6. Is Vendor known to deliver late?
  7. Is vendor located in a part of the world that is volatile?
  8. Are vendors resources unstable?
  9. Is management unaware of vacation schedules for all resources?
  10. Are there no replacements available?
  11. Will this affect schedule + deliverable’s?
  12. Will this affect quality?
  13. Is no backup equipment available?
  14. Can vendor replace equipment ASAP?
  15. Is there an alternate vendor?
  16. Are funds not available for repair/ replacement?
  17. Is replacement/implementation of new equipment not lengthy?

Budget Risks

  1. Is the budget based on expired estimates?
  2. Are resource contracts pending?
  3. Are resource costs volatile?
  4. Is scope nebulous?
  5. Have you failed previous audits?
  6. Have you neglected your internal audit system?
  7. Are your records out of date/incomplete?
  8. Have you failed to designate resources to compliance?
  9. Is there growing federal attention to your budget area?
  10. Is the budget based on expired estimates?
  11. Are resource contracts pending?

Schedule risks

  1. Is equipment overdue?
  2. Is installation behind schedule?
  3. Are there other higher priority projects?
  4. Does the customer have no fall back plan?
  5. Does vendor have higher priority clients?
  6. Is the vendor known to deliver late?
  7. Is vendor located in part of the world that is volatile
  8. Are vendors resources unstable?
  9. Do we have to order equipment from external vendor?
  10. Is material from sole source (or non-preferred) vendor?
  11. Is this new technology
  12. Is material delivered historically late?
  13. Is vendor backlogged now?
  14. Is project schedule estimates sound?

Include Risk Management in your everyday project thinking. Add Enterprise Risk Planning to your project meeting agendas. Work with your team and encourage them to think positively about risk. Most of us practice some form of risk management in our daily lives, so why not make it a part of your “project life cycle”.

Shivani Kumar


This article is provided by Shivani Kumar, Head of Marketing and Director at Kytes, formerly known as ProductDossier. Kytes is a company renowned for its flagship product, Kytes PSA Software - an Integrated Project Management Software solution. Kytes PSA assists customers in achieving Business Automation and Excellence.