Home > Articles > Information Technology

📄 Contents

  1. Management Reference Guide
  2. Table of Contents
  3. Introduction
  4. Strategic Management
  5. Establishing Goals, Objectives, and Strategies
  6. Aligning IT Goals with Corporate Business Goals
  7. Utilizing Effective Planning Techniques
  8. Developing Worthwhile Mission Statements
  9. Developing Worthwhile Vision Statements
  10. Instituting Practical Corporate Values
  11. Budgeting Considerations in an IT Environment
  12. Introduction to Conducting an Effective SWOT Analysis
  13. IT Governance and Disaster Recovery, Part One
  14. IT Governance and Disaster Recovery, Part Two
  15. Customer Management
  16. Identifying Key External Customers
  17. Identifying Key Internal Customers
  18. Negotiating with Customers and Suppliers—Part 1: An Introduction
  19. Negotiating With Customers and Suppliers—Part 2: Reaching Agreement
  20. Negotiating and Managing Realistic Customer Expectations
  21. Service Management
  22. Identifying Key Services for Business Users
  23. Service-Level Agreements That Really Work
  24. How IT Evolved into a Service Organization
  25. FAQs About Systems Management (SM)
  26. FAQs About Availability (AV)
  27. FAQs About Performance and Tuning (PT)
  28. FAQs About Service Desk (SD)
  29. FAQs About Change Management (CM)
  30. FAQs About Configuration Management (CF)
  31. FAQs About Capacity Planning (CP)
  32. FAQs About Network Management
  33. FAQs About Storage Management (SM)
  34. FAQs About Production Acceptance (PA)
  35. FAQs About Release Management (RM)
  36. FAQs About Disaster Recovery (DR)
  37. FAQs About Business Continuity (BC)
  38. FAQs About Security (SE)
  39. FAQs About Service Level Management (SL)
  40. FAQs About Financial Management (FN)
  41. FAQs About Problem Management (PM)
  42. FAQs About Facilities Management (FM)
  43. Process Management
  44. Developing Robust Processes
  45. Establishing Mutually Beneficial Process Metrics
  46. Change Management—Part 1
  47. Change Management—Part 2
  48. Change Management—Part 3
  49. Audit Reconnaissance: Releasing Resources Through the IT Audit
  50. Problem Management
  51. Problem Management–Part 2: Process Design
  52. Problem Management–Part 3: Process Implementation
  53. Business Continuity Emergency Communications Plan
  54. Capacity Planning – Part One: Why It is Seldom Done Well
  55. Capacity Planning – Part Two: Developing a Capacity Planning Process
  56. Capacity Planning — Part Three: Benefits and Helpful Tips
  57. Capacity Planning – Part Four: Hidden Upgrade Costs and
  58. Improving Business Process Management, Part 1
  59. Improving Business Process Management, Part 2
  60. 20 Major Elements of Facilities Management
  61. Major Physical Exposures Common to a Data Center
  62. Evaluating the Physical Environment
  63. Nightmare Incidents with Disaster Recovery Plans
  64. Developing a Robust Configuration Management Process
  65. Developing a Robust Configuration Management Process – Part Two
  66. Automating a Robust Infrastructure Process
  67. Improving High Availability — Part One: Definitions and Terms
  68. Improving High Availability — Part Two: Definitions and Terms
  69. Improving High Availability — Part Three: The Seven R's of High Availability
  70. Improving High Availability — Part Four: Assessing an Availability Process
  71. Methods for Brainstorming and Prioritizing Requirements
  72. Introduction to Disk Storage Management — Part One
  73. Storage Management—Part Two: Performance
  74. Storage Management—Part Three: Reliability
  75. Storage Management—Part Four: Recoverability
  76. Twelve Traits of World-Class Infrastructures — Part One
  77. Twelve Traits of World-Class Infrastructures — Part Two
  78. Meeting Today's Cooling Challenges of Data Centers
  79. Strategic Security, Part One: Assessment
  80. Strategic Security, Part Two: Development
  81. Strategic Security, Part Three: Implementation
  82. Strategic Security, Part Four: ITIL Implications
  83. Production Acceptance Part One – Definition and Benefits
  84. Production Acceptance Part Two – Initial Steps
  85. Production Acceptance Part Three – Middle Steps
  86. Production Acceptance Part Four – Ongoing Steps
  87. Case Study: Planning a Service Desk Part One – Objectives
  88. Case Study: Planning a Service Desk Part Two – SWOT
  89. Case Study: Implementing an ITIL Service Desk – Part One
  90. Case Study: Implementing a Service Desk Part Two – Tool Selection
  91. Ethics, Scandals and Legislation
  92. Outsourcing in Response to Legislation
  93. Supplier Management
  94. Identifying Key External Suppliers
  95. Identifying Key Internal Suppliers
  96. Integrating the Four Key Elements of Good Customer Service
  97. Enhancing the Customer/Supplier Matrix
  98. Voice Over IP, Part One — What VoIP Is, and Is Not
  99. Voice Over IP, Part Two — Benefits, Cost Savings and Features of VoIP
  100. Application Management
  101. Production Acceptance
  102. Distinguishing New Applications from New Versions of Existing Applications
  103. Assessing a Production Acceptance Process
  104. Effective Use of a Software Development Life Cycle
  105. The Role of Project Management in SDLC— Part 2
  106. Communication in Project Management – Part One: Barriers to Effective Communication
  107. Communication in Project Management – Part Two: Examples of Effective Communication
  108. Safeguarding Personal Information in the Workplace: A Case Study
  109. Combating the Year-end Budget Blitz—Part 1: Building a Manageable Schedule
  110. Combating the Year-end Budget Blitz—Part 2: Tracking and Reporting Availability
  111. References
  112. Developing an ITIL Feasibility Analysis
  113. Organization and Personnel Management
  114. Optimizing IT Organizational Structures
  115. Factors That Influence Restructuring Decisions
  116. Alternative Locations for the Help Desk
  117. Alternative Locations for Database Administration
  118. Alternative Locations for Network Operations
  119. Alternative Locations for Web Design
  120. Alternative Locations for Risk Management
  121. Alternative Locations for Systems Management
  122. Practical Tips To Retaining Key Personnel
  123. Benefits and Drawbacks of Using IT Consultants and Contractors
  124. Deciding Between the Use of Contractors versus Consultants
  125. Managing Employee Skill Sets and Skill Levels
  126. Assessing Skill Levels of Current Onboard Staff
  127. Recruiting Infrastructure Staff from the Outside
  128. Selecting the Most Qualified Candidate
  129. 7 Tips for Managing the Use of Mobile Devices
  130. Useful Websites for IT Managers
  131. References
  132. Automating Robust Processes
  133. Evaluating Process Documentation — Part One: Quality and Value
  134. Evaluating Process Documentation — Part Two: Benefits and Use of a Quality-Value Matrix
  135. When Should You Integrate or Segregate Service Desks?
  136. Five Instructive Ideas for Interviewing
  137. Eight Surefire Tips to Use When Being Interviewed
  138. 12 Helpful Hints To Make Meetings More Productive
  139. Eight Uncommon Tips To Improve Your Writing
  140. Ten Helpful Tips To Improve Fire Drills
  141. Sorting Out Today’s Various Training Options
  142. Business Ethics and Corporate Scandals – Part 1
  143. Business Ethics and Corporate Scandals – Part 2
  144. 12 Tips for More Effective Emails
  145. Management Communication: Back to the Basics, Part One
  146. Management Communication: Back to the Basics, Part Two
  147. Management Communication: Back to the Basics, Part Three
  148. Asset Management
  149. Managing Hardware Inventories
  150. Introduction to Hardware Inventories
  151. Processes To Manage Hardware Inventories
  152. Use of a Hardware Inventory Database
  153. References
  154. Managing Software Inventories
  155. Business Continuity Management
  156. Ten Lessons Learned from Real-Life Disasters
  157. Ten Lessons Learned From Real-Life Disasters, Part 2
  158. Differences Between Disaster Recovery and Business Continuity , Part 1
  159. Differences Between Disaster Recovery and Business Continuity , Part 2
  160. 15 Common Terms and Definitions of Business Continuity
  161. The Federal Government’s Role in Disaster Recovery
  162. The 12 Common Mistakes That Cause BIAs To Fail—Part 1
  163. The 12 Common Mistakes That Cause BIAs To Fail—Part 2
  164. The 12 Common Mistakes That Cause BIAs To Fail—Part 3
  165. The 12 Common Mistakes That Cause BIAs To Fail—Part 4
  166. Conducting an Effective Table Top Exercise (TTE) — Part 1
  167. Conducting an Effective Table Top Exercise (TTE) — Part 2
  168. Conducting an Effective Table Top Exercise (TTE) — Part 3
  169. Conducting an Effective Table Top Exercise (TTE) — Part 4
  170. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part One
  171. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Two
  172. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Three
  173. The 13 Cardinal Steps for Implementing a Business Continuity Program — Part Four
  174. The Information Technology Infrastructure Library (ITIL)
  175. The Origins of ITIL
  176. The Foundation of ITIL: Service Management
  177. Five Reasons for Revising ITIL
  178. The Relationship of Service Delivery and Service Support to All of ITIL
  179. Ten Common Myths About Implementing ITIL, Part One
  180. Ten Common Myths About Implementing ITIL, Part Two
  181. Characteristics of ITIL Version 3
  182. Ten Benefits of itSMF and its IIL Pocket Guide
  183. Translating the Goals of the ITIL Service Delivery Processes
  184. Translating the Goals of the ITIL Service Support Processes
  185. Elements of ITIL Least Understood, Part One: Service Delivery Processes
  186. Case Study: Recovery Reactions to a Renegade Rodent
  187. Elements of ITIL Least Understood, Part Two: Service Support
  188. Case Studies
  189. Case Study — Preparing for Hurricane Charley
  190. Case Study — The Linux Decision
  191. Case Study — Production Acceptance at an Aerospace Firm
  192. Case Study — Production Acceptance at a Defense Contractor
  193. Case Study — Evaluating Mainframe Processes
  194. Case Study — Evaluating Recovery Sites, Part One: Quantitative Comparisons/Natural Disasters
  195. Case Study — Evaluating Recovery Sites, Part Two: Quantitative Comparisons/Man-made Disasters
  196. Case Study — Evaluating Recovery Sites, Part Three: Qualitative Comparisons
  197. Case Study — Evaluating Recovery Sites, Part Four: Take-Aways
  198. Disaster Recovery Test Case Study Part One: Planning
  199. Disaster Recovery Test Case Study Part Two: Planning and Walk-Through
  200. Disaster Recovery Test Case Study Part Three: Execution
  201. Disaster Recovery Test Case Study Part Four: Follow-Up
  202. Assessing the Robustness of a Vendor’s Data Center, Part One: Qualitative Measures
  203. Assessing the Robustness of a Vendor’s Data Center, Part Two: Quantitative Measures
  204. Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part One: What Did the Team Do Well
  205. (d) Case Study: Lessons Learned from a World-Wide Disaster Recovery Exercise, Part Two

As mentioned in Part One, an important pre-requisite of an effective business continuity program is a thorough business impact analysis (BIA). But BIAs often fall short in delivering meaningful analyses that IT managers need to develop responsive recovery strategies. There are a variety of reasons that can cause this to happen, and I have listed the 12 most common of these in Figure 1. In Part One I discussed the first three of these common mistakes.

But did you ever wonder what role interviews play in a BIA? Or what steps should be taken to adequately prepare for these meetings? And how important is the design of BIA survey forms? In this second part, I provide answers to these questions in discussing the next three of common BIA mistakes, and how to best address them.

  1. Poorly designed survey forms. An important step of any BIA is the collection of data from business units. The manner in which this data is asked for often spells the difference between a full, timely and meaningful collection of data, and that which is delayed and complete. One of the best ways to avoid this situation is to develop survey forms that are thorough enough to capture all relevant information and simple enough for business users to complete quickly and easily.

    Two areas that are sometimes overlooked when creating BIA data gathering forms are process dependencies and past outages. Process dependencies should include all input (upstream) and output (downstream) dependencies from and to other departments, keeping in mind that the same department may have both input and output dependencies with a single process. Participants in the survey should also respond to questions concerning any sustained outages to critical processes during the past few years. This information can help confirm or refute estimates about necessary recovery times.

    1. Lack of clearly defined scope.

    2. No agreement on level of details.

    3. Marginal executive support at kickoff.

    4. Poorly designed survey forms.

    5. Inadequate preparation for interviews.

    6. Over-emphasis on value rather than urgency.

    7. Too much focus on tools instead of process.

    8. Ineffective interviewing techniques.

    9. Little thought of risk assessment.

    10. Insufficient analysis of results.

    11. Tedious presentation of results.

    12. No timely follow-up of results.

    Figure 1 The 12 Common Mistakes that Cause BIAs To Fail

  2. Inadequate preparation for interviews. Interviews are the cornerstone of a successful BIA, yet few planners prepare adequately for them to ensure their effectiveness. Interviewers need to learn as much as they can about a given business unit prior to the meeting, including a thorough review of the respondent's survey. Interviewers not only need to do their homework concerning the information that will be discussed, but should be mindful of the logistics involved as well.

    Logistical issues consist of selecting the best time of day, and day of the week to ensure the interviewee is free of distractions, is unlikely to cancel or be interrupted, and has had adequate time and reminders to be fully prepared themselves for the interview. Some BIA analysts feel it is not responsibility to ensure interviewees are suitably prepared for the interview, but those who consistently conduct successful BIA interviews have done as much as they can to ensure the respondent is ready, willing and able to participate in an effective interview.

  3. Over-emphasis on value rather than urgency. Analysts frequently make the mistake of asking business users 'what are the most important business processes within their department?' The reason this is a mistake is because virtually all critical business processes have a large degree of importance and value - otherwise they would not be designated as critical – resulting in less likelihood of it being easy to prioritize processes according to value or importance. A much better question to ask is 'how long can a business process be idle before major impact is felt? A key objective of a BIA is to prioritize business processes according to their urgency, according to how quickly impact will be felt.

    For example, in mortgage banking the processing of incoming loan payments may be viewed as an extremely important process from a financial standpoint, but it would likely be able to be delayed for a day or two in the event of a disaster. Wiring funds to close on a loan, on the other hand, may not generate immediate direct revenue but is far more urgent when not completed within a few hours because of the possibility of penalties, regulatory problems, potential loss of customers, and damage to the company's reputation. Identifying non-direct cost impact criteria such as image, stock price, penalties or loss of customers can help distinguish the differences between the value of business process and that of its urgency.

This concludes the second segment of this four part series on the 12 Common Mistakes That Cause BIAs To Fail. In the upcoming third part I will discuss the next three of these mistakes involving:

  • focusing too much on tools instead of process
  • failing to use effective interviewing techniques
  • not including risk assessments in the BIA

Part four will cover the final three causes of BIA failures.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.