Home
 > Research and Reports > TEC Blog > Five Steps to Business Intelligence Project Success

Five Steps to Business Intelligence Project Success

Written By: Lyndsay Wise
Published On: September 11 2009

<

Originally published - June 18, 2007

Successful business intelligence (BI) projects encompass more than implementation of a solution on time and within budget. True success should be measured by how the BI solution improves the organization's overall performance through increased efficiency in reporting, planning, financial functions, and performance measurements. This will help ensure organizations' BI projects fall into the estimated 30 percent success rate.

Much has been written about measuring return on investment (ROI) for BI, and the general conclusion is that gaining tangible insight into the initial benefits is not easy. Identifying long-term benefits becomes more practical as planning and analysis, compliancy, and forward-looking approaches become more mainstream within organizations. To gain insight into how to implement a BI solution successfully, organizations should benchmark the success of other organizations—including their implementations and use of BI—against their own current initiatives. It is equally important that organizations learn from other organizations' failures—and avoid repeating them.

This article identifies and explores five steps organizations should take to avoid the common pitfalls encountered by many businesses when implementing a BI solution. These steps also provide an overview of items that need to be considered before implementing BI within an organization or business unit.

Step 1. Identifying the Business Problem

Identifying the BI business problem is the first step to ensuring a successful project. Once an organization knows what is broken, not only can it start to find ways to fix the problem, but it can also identify the proper resources, create user buy-in, and prioritize how to tackle the project. To produce an ROI, a BI solution needs to address specific business problems. Otherwise, implementing an ad hoc query tool, an online analytical process (OLAP) cube, or a dashboard will not result in lasting benefits.

Unfortunately, it is common for BI solutions to be pushed onto a business unit in order to meet an IT objective rather than an organizational need. Sometimes organizations get caught up with general initiatives and lose sight of the actual benefits BI provides in terms of performance management, collaboration, workflow, process improvement, etc.

To attain buy-in, the user community should be a part of the problem identification process. An implementation decision that comes from management still requires input from users as to what their requirements are, and this information can make the difference between the implementation of a tool that works as a value proposition and an implementation that may be seen as useless.

Step 2. Determining Expectations of Use

Once BI is implemented within an organization, its usage usually grows beyond initial expectations. For example, an organization may assume that its BI solution will be used by 10 to 20 users, when in reality over 400 users query data on a monthly basis. Because the initial design of the platform will have been based on a low number of potential users, the system may not be able to sustain such a high number of queries, and will most likely "crash" (fail), causing users to lose faith in the new system and potentially revert to their pre-BI environment for stability. In addition to lacking confidence in the new system, the organization may see the challenge of getting an unstable system up and running as not worth the effort, delays, and time required.

With unrealistic expectations, frustration may cause the organization to rethink its use of BI. Generally, once BI adoption occurs within one part of the organization and other departments or business units see its benefits, adoption begins to spread throughout the entire organization. For a BI solution to meet these increasing needs, organizations should anticipate the use of BI before implementation of a solution.

Another consideration is the type of BI tool use. For example, if a sales manager needs to increase sales and therefore wants to analyze trends, product distribution, and sales performance, creating a set of static reports will not be helpful. A data visualization tool to manage these items and to develop a plan based on trend analysis will more likely produce the appropriate results.

Step 3. Understanding Delivery of Data

The BI solution's ability to collect the right information for reporting and analysis is essential if it is to deliver value to organizations. Although identifying the data required is time-consuming, it is the backbone of BI. Additionally, determining how data will be delivered, what the appropriate data cleansing activities should be, and whether the data is to be delivered in batch or in real time, should all be defined in advance. If data is not cleansed or delivered when needed, then the front-end BI tools will not provide the proper value to the organization. BI solutions impart value through the analysis of data, so it is essential that data arrives when required, in the proper format, and at the right time.

In addition to extract, transform, and load (ETL) tools, data quality and data cleansing need to be inherent aspects of the delivery of BI within the organization. In reality, short of an organization-wide master data management (MDM) initiative, the responsibility of providing accurate data will fall on the shoulders of the business units implementing BI.

Some organizations are misguided and think that their BI solution will provide the tools to fix their data problems. BI solutions can provide ongoing data quality processes, but these are not innate to software offerings. Some vendors' BI tools include enhanced data quality and integration features, and other vendors assume this responsibility should fall to the organization. Organizations should implement data management structures to minimize frustrations that result from data issues.

Step 4. Rolling Out Training Initiatives

Deciding when to roll out training contributes to project success. Training initiatives should begin right before or during the implementation phase. However, in many organizations, training is rolled out months before actual implementation, creating hype among the employees about the new system and what they will be able to do with it. By the time implementation actually occurs—sometimes months later—the initial excitement and buy-in has subsided, and more importantly, users have forgotten their newfound skills. To build momentum again, training needs to be repeated—wasting time and money.

Buy-in related to change is never easily achieved within organizations. Users become attached to their current processes, whether or not those processes are productive. Buy-in does not occur immediately upon showing users the inherent value of BI because it means the entire way they do business will change. Creating a training program—and delivering that training in a timely fashion—helps users apply their newfound skills immediately, thus helping to increase user buy-in.

Step 5. Choosing a Vertical- or Horizontal-based Solution

Organizations should identify whether more value will be provided by a vertical solution that is built specifically for the organization's industry or department, or by a horizontal solution that can grow with the organization. For example, does the organization need a generic reporting, querying, and analysis tool that will extend across the organization, or does the organization need to develop a process and compliancy that will adhere to the US Sarbanes-Oxley Act (SOX) or Health Insurance Portability and Accountability Act (HIPAA) standards? The answer to this question will help the organization define which type of solution will best meet its needs.

In addition, anticipated use of BI in the future may help determine whether a horizontal or a vertical solution will best meet the organization's needs. Organizations that must adhere to compliance standards should take advantage of vertical-based solutions, because vendors have developed solutions that meet specific compliance requirements. Horizontal solutions need a large degree of customization to bring them up to par, leading to extra time and money spent on developing the solutions.

Organizations in key vertical industries should strongly consider vertical-based solutions that will meet their needs, out of the box. Vertical-based solutions are likely to meet the general requirements of a specific industry or department, but since horizontal BI solutions do not base themselves on specified data models, they may be more versatile to the changing demands of the organization. Therefore, if an organization anticipates rapid BI growth across the organization, having the ability to develop solutions based on individual needs may be more beneficial. This relates to identifying the business problem and anticipating the future needs of the organization.

Conclusion

All too often, BI projects fail to meet an organization's expectations. But with research, planning, and a solid methodology, failure can be avoided. To help ensure BI project success, organizations should work through these five essential steps: identifying the business problems, determining how a BI solution will be used, knowing how and when data is delivered, rolling out user training initiatives at appropriate times, and developing a framework for selecting the type of solution that will best fit their organizations' needs.

 
comments powered by Disqus

Recent Searches
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z Others

©2014 Technology Evaluation Centers Inc. All rights reserved.