Skip to main content

The Purpose and Value of Business Impact Analysis

When discussing Service Design I am often asked the purpose and value of a Business Impact Assessment (BIA).  The purpose of a BIA is to quantify the impact to the business that the loss of a service would have.  It is a valuable source of input when trying to ascertain the business needs, impacts and risks that the organization may face in the delivery of services.  The Business Impact Assessment is an essential element of the overall business continuity process.  It identifies the most important services to the organization and therefore will help to define the overall strategy for risk reduction and disaster recovery.  At a more granular level these assessments enable the mapping of critical service applications and technology components to critical business processes.  It is an invaluable input for Continuity Strategy, Availability Design, and Capacity Management. 
The BIA’s strategic purpose is to show which parts of the business will be most affected by a major incident and what affect it will have on the company as a whole.  The form these damages or losses may come in are:        
  • Loss of income
  • Additional costs
  • Damaged reputation
  • Loss of goodwill
  • Loss of competitive advantage
  • Breach of law, health or safety
  • Immediate and long term loss of market share
  • Political, corporate or personal embarrassment
  • Loss of operational capability
As part of the design phase of a new or changed service the BIA should be conducted to help enable a greater understanding about the function and importance of a service.   This will allow the organization to define:
  • Acceptable levels and times of a service outage.  How the degree of damage is likely to escalate after a service disruption, and the times of day, week, month or year when a disruption will inflict the greatest damage.
  • The staffing, skills, facilities and services necessary to enable critical and essential business processes to continue to operate at minimum acceptable levels.
  • The time within which all required business processes and supporting staff, facilities and services should be fully recovered.
  • The cost the loss of a service has to the business.  This is critical for Financial Management.
Additionally, it has been shown that the BIA can be a useful input to a number of other areas across ITSM and the business and would give a far greater understanding of the service then would otherwise be the case.

Comments

Unknown said…
When to do the BIA? Just at DESIGN stage or at STRATEGY STAGE too? I am reading about BIA at FINANCIAL MANAGEMENT PROCESS. So BIA is a "tool" used in which processes?
Jayne Groll said…
BIAs can be done at various stages of the lifecycle and are activitiess particularly important to processes such as Availability and IT Service Continuity Management. I would suggest performing a BIA during Service Strategy as part of the business case. Not only does this help make decisions on whether to proceed, it also avoids multiple BIAs later in the lifecycle.

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th