Risk Management: Learning Outcomes
Risk Management: Learning Outcomes
Risk Management: Learning Outcomes
RISK MANAGEMENT
LEARNING OUTCOMES
After going through the chapter student shall be able to understand
Concept of Risk Management
Objective and Process of Risk Management
Importance of Risk Management
Risk Management Techniques
alternatives. Regulators started recognising the relevance and significance of the subject of risk
management and started prescribing advisories from 1980s; however, the awakening and intensity
of detailed regulatory interventions came about greatly post the global financial crisis in the year
2007.
Each strategy and business action is accompanied with its expected risk and reward. Good risk
management therefore does not imply avoiding all actions and associated, rather it implies making
informed and coherent choices. The risks that the organization wants to take in pursuit of its
objectives and in particular choices it makes to manage and mitigate those risks.
Let us study few important views on the subject of Risk and Risk Management:-
Source Views
Warren Buffet Risk comes from not knowing what you are doing
Theodore Roosevelt. Risk management is about people and processes and not about models
and technology
The Risk Management Risk management is a central part of any organisation’s strategic
Standard, The Institute management. It is the process whereby organizations methodically
of Risk Management address the risks attaching to their activities with the goal of achieving
sustained benefit within each activity and across the portfolio of all
activities.
Risk management should be a continuous and developing process which
runs throughout the organisation’s strategy and the implementation of
that strategy. It should address methodically all the risks surrounding the
organisation’s activities past, present and in particular, future. It must be
integrated into the culture of the organization with an effective policy and
a programme led by the most senior management. It must translate the
strategy into tactical and operational objectives, assigning responsibility
throughout the organization with each manager and employee
responsible for the management of risk as part of their job description. It
supports accountability, performance measurement and reward, thus
promoting operational efficiency at all levels.
Thomas S. Coleman, Risk management is the art of using lessons from the past to mitigate
Practical Guide Risk misfortune and exploit future opportunities—in other words, the art of
Management, CFA avoiding the stupid mistakes of yesterday while recognizing that nature
Institute can always create new ways for things to go wrong.
We cannot lose sight of the most important aspect of risk management—
managing risk. That means making the tactical and strategic decisions to
control those risks that should be controlled and to exploit those
opportunities that should be exploited. Managing risk cannot be divorced
from managing profits; modern portfolio theory tells us that investment
decisions are the result of trading off return for risk, and managing risk is
simply part of managing returns and profits. Managing risk must be a
core competence for any financial firm. The ability to effectively manage
stop limit within which the Board would like to restrict its business actions. For example an entity
with a networth of ` 500 Crores may have a capacity of risk taking upto ` 500 Crores while the
Board may still articulate a philosophy that the risk appetite of the entity would be limited to ` 100
Crores only or upto 20% of the networth of the entity. On account of such policy statement on the
risk appetite, the Business managers would not be allowed to take decisions that have the
potential to go beyond the risk appetite limits of the entity. Therefore, Business managers would
have to drop choices that have the potential to impair the financial stability of the company beyond
the boundary set up by the Board.
In determining the risk appetite of the company, the Board should engage with the executive/
management team and provide clear directions on the contours and definition of the risk capacity,
appetite and tolerance levels. For example, when does a company become uncomfortable if the
percentage of its revenues generated by just top four or five clients rises continually or even
becomes dominant? Another example ‘X’ company which experiences 10% growth (and still
growing) in product returns from customers. At what point does this become too big a risk to
overall customer satisfaction, company costs or general reputation? In both of these cases, one
company may have a completely different tolerance of risk to another but this needs to be explicitly
understood and capable of change when circumstances require it to do so.
1.3 Risks Appetite – Principles and Approach
The key question for all companies is how much risk do they need to take? And yet taking risks
without consciously managing those risks can lead to the downfall of organizations. This is the
challenge that has been highlighted by the UK Corporate Governance Code issued by the
Financial Reporting Council in 2010.
The following key principles have underpinned risk appetite:
1. Risk appetite can be complex. Excessive simplicity, while superficially attractive, leads to
dangerous waters: far better to acknowledge the complexity and deal with it, rather than
ignoring it.
2. Risk appetite needs to be measurable. Otherwise there is a risk that a statement may
become empty and vacuous.
3. Risk appetite is not a single, fixed concept. There will be a range of appetites or ranges for
different risks which need to be aligned and these appetites may vary over time. Like in
sourcing decisions, the Board may set vendor business share limits as they would be make
the entity dependent on few vendor companies that could eventually impact business
continuity or range of quality defects.
4. Risk appetite should be developed in the context of an organization’s risk management
capability, which is a function of risk capacity and risk management maturity. Risk
management remains an emerging discipline and some organizations, irrespective of size or
complexity, do it much better than others. This is in part due to their risk management culture
(a subset of the overall culture), partly due to their systems and processes, and partly due to
the nature of their business. However, until an organization has a clear view of both its risk
capacity and its risk management maturity, it cannot be clear as to what approach would work
or how it should be implemented.
5. Risk appetite must be integrated with the control culture of the organization. The Risk
Management framework explores this by looking at both the propensity to take risk and the
propensity to exercise control. The framework promotes the idea that the strategic level is
proportionately more about risk taking than exercising control, while at the operational level
the proportions are broadly reversed. Clearly the relative proportions will depend on the
organization itself, the nature of the risks it faces and the regulatory environment within which
it operates.
If one designs a framework around that uncertainty, then you effectively de-risk the business. And
that means one can move much more confidently to achieve your goals. By identifying and
managing a comprehensive list of business risks, unpleasant surprises and barriers can be
reduced and golden opportunities discovered. The risk management process also helps to resolve
problems when they occur, because those problems have been envisaged, and plans to treat them
have already been developed and agreed. One can avoid impulsive reactions and going into “fire-
fighting” mode to rectify problems that could have been anticipated. This makes for happier, less
stressed business teams and stakeholders. The end result is that we minimize the impacts of
threats and capture the opportunities that occur.
Risk Management Checklist (ISO 31000)
Risk architecture
● Statement produced that sets out risk responsibilities and lists the risk-based matters
reserved for the Board
● Risk management responsibilities allocated to an appropriate management committee
● Arrangements are in place to ensure the availability of appropriate competent advice on
risks and controls
● Risk aware culture exists within the organization and actions are in hand to enhance the
level of risk maturity
● Sources of risk assurance for the Board have been identified and validated
Risk strategy
● Risk management policy produced that describes risk appetite, risk culture and philosophy
● Key dependencies for success identified, together with the matters that should be avoided
● Business objectives validated and the assumptions underpinning those objectives tested
● Significant risks faced by the organization identified, together with the critical controls
required
● Risk management action plan established that includes the use of key risk indicators, as
appropriate
● Necessary resources identified and provided to support the risk management activities
Risk protocols
● Appropriate risk management framework identified and adopted, with modifications as
appropriate
● Suitable and sufficient risk assessments completed and the results recorded in an
appropriate manner
● Procedures to include risk as part of business decision-making established and
implemented
● Details of required risk responses recorded, together with arrangements to track risk
improvement recommendations
● Incident reporting procedures established to facilitate identification of risk trends, together
with risk escalation procedures
● Business continuity plans and disaster recovery plans established and regularly tested
● Arrangements in place to audit the efficiency and effectiveness of the controls in place for
significant risks
● Arrangements in place for mandatory reporting on risk, including reports on at least the
following:
• Risk appetite, tolerance and constraints
• Risk architecture and risk escalation procedures
• Risk aware culture currently in place
• Risk assessment arrangements and protocols
• Significant risks and key risk indicators
• Critical controls and control weaknesses
• Sources of assurance available to the Board
Some of the Risk Enabled and Managed organisations used the following techniques.
Technique Description
Risk Questionnaires Designed to identify the relevant risks and create risk history
Flow Charts with Risk Flags Designed to identify operational risks embedded in the
processes
Identify Controls to manage Recognize controls and test their adequacy and operative
risks effectiveness
Risk Event Maps Identify potential events that can have a significant impact on
business to avoid negative surprises
Risk Scorecards A Monitoring tool to track progress of risk management
Capital Budgeting A financial analysis tool to evaluate the future cash flow benefits
arising from risk management actions against the costs of risk
consequences
Value at Risk A financial analysis tool to evaluate the impact of the worst case
scenario of a risk event
Risk Heat Maps A Monitoring tool to track progress of risk management using
qualitative assessment of probability and impact of risk
Case Study 3
Staff at Barclays repeatedly filed misleading figures for interbank borrowings. First, between 2005
and 2008 – and sometimes working with traders at other banks - they tried to influence the Libor
rate, in order to boost their profits. Then between 2007 and 2009, at the peak of the global banking
crisis, Barclays filed artificially low figures. This tactic sought to hide the level to which Barclays
was under financial stress at a point where their peers were being forced to accept state funding.
When the scandal came to light it led to the resignation of the bank’s chief executive Bob
Diamond, along with Barclays chairman Marcus Agius. Barclays was fined €290m by UK and US
regulators for rigging Libor and investigations are continuing. Barclays have set up an independent
review to assess the bank’s current values, principles and standard of operation and determine to
what extent those need to change. It will also test how well current decision-making processes
incorporate the bank’s values, standard and principles and outline any changes required.
(BCC Website, 2012) (Barclays Press Release, 2012)
Case Study 4
Improving Cross Organizational Processes through Risk Management Working Group – A Carrier
Team One Case Study
An aircraft carrier is a floating city with power plants, satellite telecommunications, convenience
stores, and medical, dental, and hotel facilities. Maintaining and modernizing these ships can
involve up to fifty different organizations simultaneously conducting all sorts of work, from painting
to structural repair to electronic, electrical, and mechanical system upgrades. As an added project
management challenge, the ship’s crew typically lives on board during a major overhaul, which
means that work cannot be conducted day and night, and services such as telecommunications,
heating, ventilation, air conditioning, electricity, sanitation, and fresh water supply must remain
intact as much as possible. With up to 500,000 man-days of work scheduled during an eleven-
month dry docking period, you can imagine the tremendous amount of activity that must be carried
out in a confined space and on a tight schedule.
The Naval Sea Systems Command (NAVSEA) established Carrier Team One (CT1) in 1997 to
define, champion, and improve cross-organizational processes for planning and executing these
complex aircraft carrier overhauls, known as “availabilities.” CT1 provides the structure for
managing and systematically improving cost, schedule, and quality performance by focusing on
key planning and execution processes. They also integrate the efforts of numerous contributing
organizations into an effective total-maintenance process.
CT1 took notice when two aircraft carrier availabilities were completed a number of weeks late in
2006. The team identified many factors that contributed to the delays, including large work
packages with a number of high-risk items, critical path work with minimal margin, significant new
and expanded work, and project team inexperience and turnover. All these issues affected both
projects, yet project managers lacked an effective means of identifying, assessing, mitigating, and
communicating the risks they posed to their project’s timely completion. As a result, the carrier
maintenance community was unaware that help was needed until it was too late to take steps to
avoid or limit delays. In response to the problems encountered on those projects, CT1’s Executive
Steering Committee formed a Risk Management Working Group (RMWG) and tasked them to (1)
develop a standard process for comprehensive availability of risk management that could be
applied consistently across all aircraft carrier shipyards and (2) support and monitor a risk
management pilot project to be implemented on nine carrier availabilities at five different locations.
CT1 used the existing Northrop Grumman Shipbuilding Newport News Operations (NGSB-NN)
Risk Management Program (already in compliance with Department of Defence guidance) to
develop a formal process for all aircraft carrier availabilities.
NGSB-NN based their 1998 risk program on a NASA-proven practice. NASA’s Goddard Space
Flight Center conducted a number of risk management training sessions at NGSB-NN and
provided copies of their risk management procedures. Building on this knowledge transfer from
NASA, NGSB-NN developed a risk management process designed specifically for ship
construction and repair. This process included the development of a risk management strategy;
developing and conducting risk management training; identifying program risks; analysing potential
technical, quality, cost, schedule, and human-capital impacts; determining likelihood of problem
occurrence; developing plans to mitigate risks; developing and maintaining a risk tool for capturing
and updating project and shipyard risks; capturing risk management lessons learned; and
continually improving the process to reflect customer feedback. To indicate the probability and
impact of risks, the process uses the red/yellow/green risk cube described in the Defence
Acquisition University Risk Management Guide for Department of Defence Acquisition. It adds
environmental and safety risks to cost, schedule, and technical /quality risks. Proving its value
over time, NGSB-NN’s risk management program is now used company wide.
The CT1 risk management pilot project focused on the cultural journey required to convince naval
shipyard aircraft carrier project teams of the value of a formal risk management process and to
actively engage in it. That journey included the following essential elements.
Catalyst: As in any cultural journey, a catalyst for change is essential. In this case, the catalyst
was the late completion of the two 2006 aircraft carrier overhauls in an environment that lacked a
formal risk management process.
Infrastructure: The Executive Steering Committee formed the RMWG to establish a formal risk
management program and associated training tools.
Initial Buy-In: Once the infrastructure was in place, the RMWG leader met with key stakeholders
to share risk management background and procedures and develop their implementation plan and
customer expectations.
Launch: As Executive Steering Committee chairman, Captain Daniel Seigenthaler, United State
Navy (assistant chief of staff for carrier maintenance at Commander, Naval Air Forces Pacific
Fleet), signed a letter directing the implementation of a risk management pilot program for nine
aircraft carrier availabilities over a one-year period. This was followed by the RMWG leader
meeting with project leaders at the headquarters of all three aircraft carrier shipyards to discuss
ideas for implementation.
During the pilot project, the RMWG leader provided peer assistance and training for each project’s
assigned risk manager to support skills development and team acceptance.
Integration into the Organization’s Culture: From the outset, each project team’s leadership
needed to perceive the value of risk management to encourage their engagement. The initial
direction and expectations set by CT1 provided the “push;” the challenge was to create a “pull”
from the project teams. This was done by integrating risk management into command briefings,
progress briefings, meeting agendas, team training, awards and recognition, newsletter articles,
project strategies, retrospects, and the “hot wash” meeting at project completion. (“Hot wash” is a
military term for a meeting used to capture learning and develop related recommendations at the
end of a major activity or engagement.) CT1 thinks of a hot wash as a carrier-overhaul project
team’s “gift” to future project teams. Establishing a cross-project risk manager community of
practice for knowledge sharing and comparison was the key to the pilot’s accelerated adoption.
This community provides a peer-assist environment for the risk managers to communicate and
collaborate. It is also a forum for risk managers to discuss their challenges and share experiences
and learning.
Retrospect and Process Maturity: The one-year pilot involved eight different overhaul projects
that were either planned and less than a year from starting or in the process of executing four- to
six-month-long repair projects. The pilot work proved to be process easy, but the implementation
was hard. Early in the project, team leaders wanted to see value before engaging, but the best
way to see risk management’s value for their project team was to engage in it. At the conclusion of
the risk management pilot, project leadership interviews captured what went well and what could
be improved. A risk management process retrospect was held to capture lessons learned and
recommendations from the one carrier project whose risk implementation extended from the start
of planning to availability completion. Resistance occurred on all projects, but the quickest
adoption came from the one that was furthest from their start date (ten months of planning
remaining). As one would expect, the team that was a month into their six-month overhaul and
focused on executing the work that was already under way saw the least value in the risk program.
Data gathered during the pilot showed that project teams who embraced the formal risk
management process quickly achieved risk-exposure reductions similar to those NGSB-NN teams
that had been using it for years. These metrics helped convince other project teams of the value of
the process and encouraged their engagement. Captured risks were shared via CT1’s portal. The
commonality of risks gave valuable insights to shipyard and program leadership personnel. Some
examples of frequent risk categories were material availability, work package size and changes,
constraints from shipyards or naval bases, planning performance, key event management,
unidentified work and weather impacts, scheduling conflicts, worker availability, funding, ship’s
crew readiness, and project team turnover.
Following the pilot project, feedback from leadership showed that they were all fully engaged and
appreciative of this tool’s ability to help communicate and mitigate their biggest concerns. Matt
Durkin, Norfolk Naval Shipyard’s project superintendent for United State Ship Harry S. Truman’s
(CVN 75) 2009 overhaul, commented, “Risk management provided me with more visibility of our
project’s key issues. I’m not sure we would have completed our last availability on time without the
Risk Management process.” And Tim Ferguson, Puget Sound Naval Shipyard and Intermediate
Maintenance Facility’s project superintendent for USS Abraham Lincoln’s (CVN 72) 2009 overhaul,
said, “Our project team leveraged the risk management program to support open and honest
discussion of issues that could have impacted delivering the ship on time.” Pilot participant
suggestions for taking the risk management program to the next level included:
• Adapting the process to address potential problems that were beyond the program manager’s
scope of influence.
• Using the risk management process to identify and communicate potential shipyard and
ship’s crew work distribution conflicts.
• Integrating risk management into a work package’s development process during planning.
Captain Kevin Terry, USN, CT1’s chairman, summed up the work so far: “The Risk Management
Working Group has been a true success story. The pilot project was a home run. Aircraft carrier
public and private shipyards are using the same language and risk cube to mitigate and
communicate their issues.” The U.S. Navy’s Ship Maintenance Enterprise is currently building on
the success of CT1’s risk management pilot project. A NAVSEA instruction is being issued to
formalize the process for all the U.S. Navy’s ship and submarine overhauls. Over the next few
years, NAVSEA will expand from individual project teams to the entire shipyard enterprise. As
Cleve Butts, NAVSEA’s director for Carrier Support, notes, “It is absolutely essential that we
complete our maintenance periods on time and within cost, not only for aircraft carriers but for all
our ships. Risk management is a great communication and management tool for ensuring that the
right actions are being applied effectively and early. The RM [risk management] process has now
been successfully implemented at all aircraft carrier shipyards.