Basic of Enterprise Risk Management
Basic of Enterprise Risk Management
That’s the ideal situation, at least. In reality, it’s not always as simple as making a
plan and sticking to it. There’s always the risk that certain events could affect the
success of these plans.
It’s the job of management to make adequate preparations to ensure that systems
are in place to continue hitting objectives, even when the beast of unforeseen
circumstance rears its head.
By utilizing an effective ERM system, you can rest assured that the organization
will see a consistently high success rate in terms of hitting objectives and KPIs.
Equally, not having a proper system for enterprise risk management could mean
your business is perceived as less competent, and could even result in loss of
clients and damage to brand image.
In this post, I’ll discuss:
Implementing ERM
Automating ERM
To begin with, I’ll start by breaking down the full scope of an ERM system, and
some basic definitions.
“coordinated activities to direct and control an organization with regard to risk … [a]
systematic application of policies, procedures and practices to the activities of
communicating and consulting, establishing the context and assessing, treating,
monitoring, reviewing, recording and reporting risk.” – ISO 31000 – Risk
Management Guidelines
Risk management is not a new concept; historically, companies would manage risk
with insurance policies. Liability, malpractice, loss or injury, property insurance,
natural disasters – different policies to “manage” different risks relating to different
business activities.
In recent years, as standards for risk management have become more established
and seen widespread adoption, risk management has become more akin to
a business process management framework. That is to say, ERM systems will
typically focus more on control of internal processes, using principles of continuous
improvement, internal audits, compliance with standards – seeking to minimize
controlled risk as much as possible, as well as setting up preventative measures for
risks and hazards outside the scope of control of business processes.
It’s important that relevant interested parties understand the rationale for
implementing ERM; that way the whole organization can be aligned towards a
singular common objective, and adoption will be streamlined. Making sure
everyone understands the value and reasoning behind adopting an ERM system is
one of the first steps to successful implementation.
A 2008 Deloitte survey asked a group of participants to identify the benefits of ERM
in terms of how they felt benefits had already been experienced, and how they
thought benefits would manifest in the future.
When devising initiatives for ERM implementation, companies should try not to
focus too much on the negatives; risk management can and should be seen as an
opportunity for process improvement .
It also means processes can be improved and optimized , so that the end result is
not only (for example) circumvention of potential disaster down the road, but near-
term benefits and immediate benefits as a result of process changes.
Today, risk management has taken on a broader role, covering four core areas:
While not specifically relating to any one framework of ERM, the example below
clearly illustrates the relationship between risk, hazard, and exposure:
Source
2. Internal control
This is another way of saying the meta-processes that companies use to make sure
internal processes are being followed.
Internal control processes are also used to improve process efficiency in areas
such as reporting, conformity, and general process effectiveness.
Larger organizations, especially those in highly regulated industries, will often have
elaborate and expansive systems of internal control.
3. Internal audits
Simply put, internal audits are used to make sure internal controls are working
properly. This is different to risk management – it’s another meta-level process that
looks instead at the cost, efficiency, and effectiveness of the ERM processes.
Internal audits are concerned with how the risks are actually being managed in
practice, and how this evidentiality sits in-line with the documented policies and
procedures of the ERM.
4. Regulatory compliance
Certain rules and regulations must be followed by companies; this area of
enterprise risk management concerns efforts to make sure these requirements are
met.
For example, government bodies may issue requirements for site safety,
environmental policy, social responsibility, or financial reporting.
ISO 31000
ISO 31000 refers to a family of standards for risk management, defined by The
International Organization for Standardization.
As well as the wider family of standards, ISO 31000 also refers to a specific
standard within that family. ISO 31000:2018 is the most recent version at the time
of writing.
ISO 31000:2018 for risk management provides a set of guidelines for organizations
to manage risk. It is not a set of requirements, and as such cannot be certified to,
unlike other ISO standards like ISO 9001.
CAS
In 2003, the society’s Enterprise Risk Management Committee defined ERM using
two concepts: risk type, and risk management processes.
Of ERM they said the following:
1. Establish context: internal and external scope of the organization, and the
scope of the ERM system
3. Analyze severity risks: For each of the risks identified, assess (and if
possible, quantify) the severity of each risk
4. Integrate risks: Based on the results of previous risk analysis, aggregate all
risk distributions and align the analysis with the determined impact on KPIs
5. Prioritizing risks: Determine a ranked order of prioritization for each of the
risks identified
COSO
This pertains to the ethics behind worker responsibilities, codes of conduct, and the
proper comprehension of risks, as well as all associated management programs
and solutions.
Business objectives are the basis for planning and implementing strategies, while
simultaneously serving as a launch-pad for identifying, assessing, and responding
to risks.
3. Performance:
Assessing how certain risks will impact the performance of key processes is
important for risk prioritization.
The five components above are supported by an additional set of principles. These
principles are wide-ranging, covering everything from corporate leadership of the
ERM program to risk monitoring methods.
Each of the principles are short and succinct; here they are, as they appear
in Enterprise Risk Management: Integrating with Strategy and Performance (2017
Edition):
Organizations can use these principles as a clear reference point for
contextualizing and evidencing their efforts to understand and strive for an
enterprise risk management program that is firmly aligned with its strategy and
business objectives.
The process (or cycle) of enterprise risk management has five main parts:
Objectives
Identification
Assessment
Response
Monitoring
1. Setting objectives and aligning ERM with business strategy
At the heart of the COSO ERM framework is the idea of using enterprise risk
management to succeed in realizing its business objectives.
ERM alone will not realize business objectives; rather the fruits of the ERM
program are vital for strategizing to achieve and exceed those business objectives.
Using an ERM framework helps to ensure that a business is able to align objectives
with mission, vision, and core values.
That includes everything from larger, more significant risks, all the way down to
smaller risks on the level of individual projects or processes.
Simply identifying risks is not enough; impact of the risk should be understood, as
well as probability, within an estimated time-frame.
Once significant risks have been adequately documented, the next task is to
assess them in terms of their likelihood and estimated significance.
This task is especially important to make sure that all documented risks have
substantial credibility. Off-the-cuff suggestions recorded in group brainstorming
sessions might have sounded good at the time, but they need to stand up to further
scrutiny. Qualitative and predictive analysis will help sort the risks by order of
significance.
Various methods exist for assessment of documented risks, from simple qualitative
approaches like the prioritization matrix , to more in-depth mathematical models .
The point of this task is to help management determine which risks deserve the
most immediate attention.
Another option is to create a heat map of risk significance. The goal of a heat map
is to support the results of a risk assessment with an illustration to supplement an
active dialogue on how the results compare with an organization’s current risk
appetite and determine urgent solutions that might need implementing.
Risk response is intended to figure out how to respond to the high-priority risks.
Avoidance
As the name clearly suggests, this type of risk response involves simply “walking
away” from the risk.
For example, a company might decide to relocate based on risks resulting from
certain geo-political tension, or completely abandoning a product or service that is
proving to be particularly risky.
Often it will be too late to avoid risks, because the damage has been done and the
costs incurred.
That’s why preventative measures and adequate analysis of potential risks are so
important – to keep the avoidance response on the table.
Reduction
Often, risks can be reduced in a number of different ways.
Diversifying a product line may reduce the risk that changing trends or seasonal
buying poses, employing multiple stop-gaps for fault tolerance like offline backups
and multiple operations centers will reduce the risk posed by natural
disasters, automating certain tasks in a process will reduce the risk of human error,
and so on.
Sharing
Risk “sharing” is the principle of purchasing insurance to hedge or offset their risks.
To use a financial example, the concept of short calls and long puts allow investors
to hedge their bets on price movements.
Joint venture agreements can also mean businesses share potential risks and
rewards.
Basically, risk sharing is the idea of having a portion of the risk offloaded onto
another party with the understanding that you’re substituting the perceived “value”
of that risk for a more tangible monetary cost.
Acceptance
To accept a risk is to take no action.
The context in which certain risks are identified is constantly changing, and as such
risks need to be monitored to continually determine the significance they represent.
Sometimes, changing circumstances may lead to the risk becoming even greater. A
clear example of this is geopolitical unrest. Organizations need proper systems in
place to monitor and respond to changes in circumstances and adequately
determine if identified risks still pose a threat.
The case examines four aspects of risk identified in pursuit of a risk opportunity
associated with the export of a cargo of frozen chickens from Virginia and North
Carolina to St. Petersburg, Russia.
The company planned to load a number of 60-80 pound boxes on pallets for an
ocean voyage. Except, the port of St. Petersburg had no shoreside refrigeration to
allow quick unloading of an expensive reefer vessel.
Expropriation risk
If the ship wasted too long docked in St Petersburg waiting for containers to offload
the shipment, it would incur significant fees for delayed operations.
One solution would be to build a warehouse, but the risk manager identified an
expropriation risk.
A case from the mid-1990s was cited: a European-invested Hotel in St. Petersburg
incurred hefty fines after the Russian government learned it was using a foreign
bank account to handle dollar transactions. The result was the expropriation of the
hotel premises by the Russian government.
While the risk manager knew she could obtain reimbursement insurance from a
U.S. government agency, the identified expropriation risk didn’t seem to be the
answer.
Therefore, the company opted to seek a strong Russian partner with high-level
government connections and allow the partner to accept the appropriation and
storage exposure.
Lesson learned: Investigate all options for risk reduction. Don’t assume that the
obvious approach is the best answer!
Credit risk
So far so good; the company had a strong Russian partner. This was also bad
news, as it created a credit risk.
How could the U.S. company make sure the Russian partner paid in a timely
manner? It wasn’t realistic to ask for an up-front payment, neither was it reasonable
to obtain a letter of credit guaranteeing future payment.
As it transpired, the Russian partner was not able to pay for the first cargo cargo
until 30 days after receiving it. To deal with this problem of credit exposure, an
agreement was made that the Russian partner would pay for one cargo before it
received a subsequent.
This mitigated exposure to credit risk because the stream of profits from a series of
cargo shipments was significantly larger than a default payment on a single cargo.
If the Russian partner didn’t pay by day 45 after receipt of a cargo, the ship
carrying the next cargo would be diverted from Russia to a northern European port.
Lesson learned: Give other parties incentives to help your organization mitigate
risk.
Once the Russian partner accepted the chicken in St. Petersburg, the shipment
was transported by rail to Moscow, Yekaterinburg, and beyond via locked
refrigeration containers loaded onto flat railcars.
On the fifth journey, one of the containers was discovered to be empty when it
arrived in Moscow after the three-day trip from St. Petersburg. The shipment had
been stolen.
1. Purchase insurance
The first strategy was dismissed quickly. Who would insure a cargo with an
already-existing high chance of loss? Premiums would be prohibitively high.
This proved effective for a time; however, the story was not over. Several journeys
later, another container arrived empty.
Realizing that someone had a crane on a siding when the train stopped in the
middle of the night, the Russian partner considered what else should be tried.
Finally, the problem was solved by placing a boxcar on the back of the train. The
car had fitted heaters and cots, carrying guards armed with Kalashnikovs.
Whenever the train stopped, the guards stepped out to protect the containers.
Lesson learned: Sometimes it’s worth sticking with a risk management strategy,
tweaking and fine-tuning the solution until the problem is solved. Not everything will
work out-of-the-box.
Upside of Risk
While the security situation on Russian railroads has improved significantly since
the 1990s, this story also identifies the upside of risk.
Once the cargo was being protected by armed guards, the Russian partner had the
opportunity to offer insurance services to third parties to protect their cargoes as
well as the frozen chickens.
The loss incurred from managing the risk with the paid armed guards and rear
boxcar would, in that case, be offset by the confidence that the train would
experience no losses, and the additional revenue from the insurance services
offered.
Lesson learned: Risk management does not end with the mitigation of risk – always
look for an upside!
You can also investigate the potential for automating aspects of your ERM system.
For example, many repetitive tasks for review and revision of risk contexts will have
to be done over and over again. Processes can be long, complex things, and the
very process of carrying out an ERM implementation carries risks of its own!
By automating these manual tasks, you are reducing the potential for human error
to occur.
Process Street is a business process management software designed to eliminate
manual work from your daily tasks.
Check out this webinar for an introduction on how to use Process Street for
enterprise risk management: