Showing posts with label Decision Framework. Show all posts
Showing posts with label Decision Framework. Show all posts

July 19, 2014

Risk In The Eye Of The Beholder

Should I do it or is it too risky?

That's a question we ask ourselves many times a day.


- Open our mouths at work or keep a lid on it.


- Run to catch that train or bus or slow down and go more carefully.


- Eat that greasy burger and fries or opt for a salad and smoothie.


- Invest in that highflier stock or put your money in the "G" fund.


The Wall Street Journal presents risk management as both quantifiable and qualitative. 


For example, a MicroMort (1 MM, and sounds like micro fart) is "equal to one-in-a million chance of death."


An average American has a 1.3MMs chance of a "sudden, violent end" on any given day. 


However, climb to the base camp at Mount Everest (at 29K feet), that's over 12,000 MM, base jump at only 430 MMs per jump, parachute 7 MM, and go on a roller coaster at only .0015 MM. 


So there you have it--statistics tell the risk story!


But not so fast, our risk calculations also take into account our qualitative values. For example, we tend to lower the risk in our minds of postpartum depression (10-15% or higher) because we value having a baby. 


Similarly, we tend to think driving (1 MM per 240 miles) is safer than flying (1 MM per 7,500 miles) because we believe we are in control of the automobile, as opposed to a passenger jet flown by a couple of pilots. 


The result, "Scariness of an activity isn't necessarily proportionate to its risk."


That means that you can easily make a mistake and underestimate risk, because of your personality or cultural and social biases. 


Rock climb at your own risk...BUT do you really understand what that risk even is or are you driven to do something overly dangerous and maybe stupid. ;-)


(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

May 19, 2008

ITIL and Enterprise Architecture

Both EA and ITIL are emerging disciplines that are growing in importance and impact.
Here are their basic definitions:
EA synthesizes business and technical information and develops information products and governance services to enable better decision making.
ITIL (Information Technology Infrastructure Library) “provides a comprehensive, consistent set of best practices focused on the management of IT services processes. It promotes a quality approach to achieving business effectiveness and efficiency in the use of information systems. ITIL is focused on IT Service Management, which is “concerned with delivering and supporting IT services that are appropriate to the business requirements of the organization.” (ITIL IT Service Management Essentials, Pink Elephant)
To me, EA and ITIL are mutually supportive. Here’s how:
  • EA is a decision framework that provides for planning and governance. EA answers the question, what IT investment will we make?
  • ITIL is a service framework that provides for execution of IT services. IT answers the question, how will we support and deliver on the IT investments?
In short, EA is the discipline that handles the decision processes up to the IT Investment and ITIL handles the service management once the decision to invest in IT is made.
What are the considerations for EA and ITIL:
  • EA considers such things as return on investment, risk mitigation, business alignment, and technical compliance. EA focuses on business process improvement and new introduction of new technologies.
  • ITIL practices areas include such services as incident management, problem resolution, change management, release management, configuration management, capacity, availability, service continuity, service level management and more.
How are EA and ITIL similar in terms of requirements management and their goals?
Each seeks to understand the business requirements and satisfy their customers: EA for the requirements for proposed new IT investments and ITIL for the service required to support those.
Both disciplines are goal-oriented in terms of wanting to improve effectiveness and efficiency:
  • EA prescribes in planning, what are the right things we should we be doing (effectiveness) and in governance, how should we be doing them (efficiency) relative to IT investments.
  • ITIL prescribes in service delivery, what are the right service deliverables (effectiveness) and in service support, how we should be providing service support (efficiency).
While EA and ITIL are complementary, ITIL picks up where EA leaves off—after the IT investment decision, but before the service execution.
Share/Save/Bookmark