January 15, 2020
How to plan a business intelligence project strategically
Business intelligence, or the art of utilizing data to find hidden patterns and insights, has become integral to strategy development for leading organizations, including Fortune 500 companies, government agencies, and academic institutions.
However, companies still struggle when implementing BI solutions. Completing these projects is no simple task but the one requiring the company to define the specific business problem, allocate resources, evaluate the outcomes from a business perspective, and operationalize the modeling process recommendations.
While companies employ several methodologies for implementing business intelligence projects, the same rigor is rarely applied when planning them. Successful implementations require that expected outcomes be clearly defined, resources earmarked, ballpark delivery estimates published, and risks captured in advance. Project managers then work within these constraints to deliver the final project.
However, to prepare even these basic inputs, companies should follow a structured approach to developing the business cases, which senior management can then evaluate. The most compelling of these use cases can then be added to the implementation queue.
This article details a high-level framework for streamlining your BI project plan. Utilizing this four-step approach will enable companies to make informed decisions about committing time and resources to data mining and analytics projects by using comprehensive cost/benefit analysis.
In order to appreciate this proposed framework’s nuances, consider a large retailer that’s attempting to leverage a BI intelligence plan to improve sales while reducing acquisition costs. The chief marketing officer (CMO) has been tasked with this strategic objective and need to develop an approach that earns buy-in not only from senior management, but also from the heads of every department whose cooperation would be imperative for successful delivery. How should the CMO proceed?
Below is a four-step approach to translate this objective into viable and tactical delivery assignments:
So, what does “improve sales while reducing acquisition costs” mean to someone other than the CEO or shareholder? This is a rather loaded remit, but what could it mean tactically? We’ve broken this down into smaller problem statements:
This step involves breaking down one high-level business objective into specific problem statements that make sense from a data perspective. Every possible interpretation above will have different data requirements, modeling approaches, risks, and cost/benefit profiles, but these would be impossible to assess without dividing the larger objective into smaller data problems.
Managers can frame problem statements by analyzing how the larger objective relates to every department and by identifying each department’s specific optimizations. This inclusive approach not only allows the capturing of potential optimization options from all parts of the business, but also helps keep key stakeholders engaged.
Say, you have over 50 possible analytical options that might deliver on the larger business objective. Marketing, product management, finance, customer service, and supply chain have all contributed, resulting in a bloated agenda. How do you set priorities?
Individual optimization options must be further elaborated and subjected to cost/benefit analysis. Take the example above: suppose that this analysis is needed for implementing dynamic pricing. This would entail the following considerations:
In this step, high-level estimates are developed for the benefits and costs of each option while key project constraints and assumptions are outlined. This information allows managers to make objective assessments of which options to prioritize or reject. For example, implementing personalization and dynamic pricing might benefit business in the long term, but it might be possible to drive higher sales by simply optimizing the campaign spend.
This step’s key deliverables include:
At this point, you should have a clear list of options with high-level cost estimates, but which are still based on many assumptions that need to be further validated. Yet, this step is the first filter in screening out options that don’t make sense to pursue, even on the basis of a cursory analysis.
Once the prioritized list of implementation options is available, the next step is developing SMART goals for each one. For dynamic pricing, these could be:
These goals typically require a combination of acute business judgment, extensive familiarity with data preparation and modeling techniques, project management experience, a highly collaborative working environment, and, above all, senior stakeholders’ acceptance that the final results might be different.
In most cases, the effort is formidable, but having objective benchmarks provides constraints for implementation teams and impacts everything from data integration technology choices and modeling techniques to the quality and quantity of resources deployed.
Step 3 is also the most technical and hands-on step in the proposed planning process. For example, why settle on $X as the sale target? The number would typically come by establishing a relationship between sales and individual personalization parameters (number of browsing sessions in a specific time, pages used in those sessions, time per page, past purchase history, any customer service interactions, etc.). This requires experienced data scientists, ETL specialists, statisticians, and product experts to sketch out analysis details, including a high-level overview of key influencing parameters, data quality requirements, modeling techniques to be deployed, and so on. For now, the objective is to make assumptions and some ballpark calculations to generate a SMART objective.
Managers should also further refine the cost estimates from the previous step. More importantly, this step places numerical values on benefits, thereby making the requirements unambiguous. Additionally, other details including resource requirements, hardware/software purchase required (if any), and a refined list of key assumptions and risks should become available.
Steps 1-3 are repetitive and specific to individual business objectives. However, a successful enterprise-wide BI implementation project plan involves creating a set of global practices, assets, tools, staffing arrangements, and delivery methods that can be applied across projects with minimal customization. Regarding business intelligence, some of these activities might include:
Lining up roles and responsibilities. Business intelligence requires business consultants, data specialists, statisticians, and project managers. Other roles may be necessary depending on specific contexts, but at minimum the key responsibilities for these roles should be clarified as part of global staffing strategy.
Picking up the right data mining tool. For data mining to be successful for business, models must be developed quickly and deployed cost-effectively within current operational systems and business processes. Various tools (SAS, SPSS, R, etc.) exist for automated model development, data integration, and model testing, and it is usually best to decide these at the global level, rather than let it be done differently for individual business intelligence projects.
Standardizing a data mining method. Adopting a consistent data mining methodology lies at the heart of realizing benefits from investments into analytics. This would typically involve:
A structured approach developed along these lines ensures purpose and repeatability in addition to allowing data mining to be implemented as discrete projects with defined budgets and timelines. CRISP-DM is the de-facto method of several organizations worldwide, although many have tailored it to their own specific business context.
If this framework is for planning business intelligence engagements, what are the steps of the implementation phase?
In order to appreciate this distinction, notice that the philosophy of the approach outlined above is ensuring that time and resource investments in business intelligence are prioritized through an objective assessment of cost/benefit analysis of various options. This assessment largely relies on assumptions, business judgments, and quick calculations with minimal hands-on work.
Thereby the actual data integration steps, sampling, data preparation, model development, and model testing activities are deferred to the implementation phase. These steps need to follow their own delivery method, but unlike the planning framework, that method is strikingly different regarding focus, approach, and the level of detail.
When applied properly, this planning framework results in a concrete, repeatable set of steps for translating high-level business objectives into specific project initiatives and ballpark estimates for time, cost, and resource requirements. Developing this strategic context helps maximize the value of data mining investments and avoid the “ad-hoc trap” that often wastes enterprise resources because of the wrong priorities set or the absence of advance insight into investment returns or business outcomes.
Itransition puts together real-life examples of our business intelligence projects to illustrate analytics embedding levels.
Itransition’s BI team presents the reactive data analytics strategy for uncertain times. Learn more.
We tap into big data and its business impacts to show how to keep it under control and avoid common big data management pitfalls.
Find out about Itransition's high-profile BI consulting for a Canadian bank, including data architecture analysis and a BI strategy.
Find out how Itransition migrated a BI suite to the cloud and delivered brand-new cloud business intelligence tools for the automotive industry.
Read how Itransition built a secure BI portal with online data gathering tools, third-party software modules, and a data processing center.