• Votes for this article no votes for this yet
  • Dashboard Insight Newsletter Sign Up

Ten Reasons Your Users Won’t Use Your Business Intelligence Solution

Tuesday, October 9, 2012

Having a BI solution that is actually used/adopted by your target audience, be they targeted within your organization or to clients/external users, is critical for the investment in BI to be successful. The article below addresses some of the common reasons for user adoption failure and suggested solutions to them.

According to Gartner, over half of all Business Intelligence (BI) and Data Warehouse projects fail.

Even those that appear to succeed, eventually fail or cease being put to good use. User adoption is the key success criteria for any BI project. If your users USE it and get value from it, you have succeeded. However, if they stop using your shiny new reporting system and creep back to using Excel spreadsheets, then you have a real problem.

In this day and age, good, reliable information is even more important than ever. Managers need to make fast, well informed decisions to help the business stay ahead of the pack. The moment your managers lose access to good, up-to-date information, your entire business is at risk.

Ensuring your users continue to use your BI solution is therefore critical. So why is it so many BI solutions fail?

See if any of these strike a chord with you:

1. Project Stalled or Went Over Deadline/Budget

This could be down to your approach. The problem with most BI projects is that they start life as a typical Software Development Lifecycle (SDLC) or Waterfall project. And that’s the first mistake. Asking users what they want from a reporting solution is fraught with problems. Most users don’t know what they want, or cannot articulate their requirements to IT. Only when they SEE something can they fully engage in an intelligent conversation about their true requirements. The catch is, you have to build something first! Traditional approaches try to solve the problem in one go, and that simply cannot work when your users don’t know what it is they want. Before you know it, you’re drowning in change requests, redesigns and rewrites - and the project is over time and/or budget (usually both).

Solution: Adopt an Agile approach. Start with a high-level requirement, prototype and reiterate. In the long run, you will save much more time (by not waste it on writing user specifications which are going to be wrong anyway), plus your technical people and business will reach a shared understanding of the task at hand, allowing them to work far more cohesively.

2. The Numbers Cannot Be Trusted

If your reports show different numbers, you have data issues. This happens when there is no single version of the truth upon which your business users can rely. If your reports are running straight off your data sources or your data hasn’t been correctly cleansed, the differences in reports can be enough to put your users off using them.

Solution: Look at developing a data-mart or data warehouse. Create an environment where no-one trusts a report UNLESS it has been sourced from the data warehouse. By creating a well-ordered, structured data warehouse, you also pave the way to true self-serve reporting.

3. Reports Take Too Long To Run

If a user has to wait hours for a report to run every time they want to make an ad-hoc query, then eventually they will stop using the report - and that’s not good for business. Users demand well-architected information systems that deliver answers in seconds, not hours. If you are reporting directly from a source system, then you are impacting the speed of your reports AND the users actually performing daily transactions on the source system.

Solution:- Get a solution that can schedule reports to run out-of-hours, or build a separate data mart/warehouse so running reports with big queries won’t impact other users.

4. Requirements Have Changed Since The Project Began

Often, delivery times for BI projects take so long that the grass literally grows under your feet. By the time the project is completed, business has moved on and requirements have changed.

Solution: Aim for shorter delivery cycles – don’t try deliver everything at once. Use an approach that is adaptable – and even embraces – change. It is well-proven that change WILL happen.

5. The World Has Moved On After Delivery

Business Intelligence projects are a journey, not a destination. Times change, the world changes, your business changes, and so will your reporting requirements. Just as your business needs to adapt and change, so does your BI solution. It’s a fact of life. If you cannot embrace change, your BI solution will quickly become out-of-date – and your users will stop using it.

Solution: Build a well-architected solution that is open-ended and adaptable. Use modern tools to help build your data mart/warehouse quickly to facilitate fast changes.

To read the rest of the article click here

Source: SmartData Collective

Tweet article    Stumble article    Digg article    Buzz article    Delicious bookmark      Dashboard Insight RSS Feed
 
Other articles by this author

Discussion:

No comments have been posted yet.

Site Map | Contribute | Privacy Policy | Contact Us | Dashboard Insight © 2017