Resource Center

5 Common BI Problems

5 Common BI Problems 5 Common BI Problems

How can you set up a business intelligence initiative that provides an impact across your organization? Consultancy DecisionPath suggests addressing these prime concerns at the start of your BI strategy.

Lack of Business Intelligence Strategy Lack of Business Intelligence Strategy

BI must have a well-communicated value proposition, DecisionPath says. Symptoms of poor or lacking strategy include: requirements stated as lists of data elements rather than articulated business questions; reluctant approvals from the executive level; specific plans for embedding BI in processes; and vague or generic value returns.

Lack of BI Readiness Lack of BI Readiness

There are a few questions your organization should be able to answer to best gauge the conditions for a successful implementation. Does your organization have and consistently use a framework for prioritizing and managing BI investments? To what level do you know the quality of your data? Do people within the organization possess necessary BI skills and methodology? Can your organization identify and address risk and change management associated with a BI initiative?

Lack of Direction Lack of Direction

There may be multiple data warehouses, BI environments and user communities within an organization over time, so coordination is in order to prevent rogue management. To prevent multiple unintegrated BI systems, data repositories and “versions of the truth,” make sure an overarching strategy/roadmap and a BI data architecture plan are in place.

Lack of Execution Lack of Execution

BI strategy and tools are crucial, but so is the follow-through. This can cause, among other problems, issues for end users with ease of use, response time and accuracy, report processing and dashboard motifications, and delivery on functionality. Successful, repeatable BI execution requires sufficient and sustained funding and support, internal or external BI staff, and use of BI-specific development methodology.

Lack of BI Impact Lack of BI Impact

The time to develop business benefits is at the very start of the BI lifecycle. The requirements-gathering process for BI must connect requirements for information to its use, users, KPIs and strategic objectives in the business process.
All images were used with permission from ThinkStock.

Business intelligence and data warehousing consultancy DecisionPath outlined a handful of BI problems that often trip up projects and implementations in blogs earlier this year (read part one here and part two here).


Please note you must now log in with your email address and password.