by Davin Wilfrid, Managing Editor, ERP Expert
Jim Holincheck has an interesting post over at his blog on the subject of business intelligence (BI). More specifically, he has some reservations about what is presented at a typical BI product demo (he's an analyst -- he sees a lot of them).
While glossy dashboards and fancy drill-down capabilities are well and good, Jim argues, they should not be the focus of evaluation. He posits an example where a regional bank manager discovers that customer satisfaction levels have dipped below a tolerable level:
This is a moment of truth for business intelligence. What would that regional bank manager do? At best, I might login to the system and see which branch(es) have the problem (or I might even get an alert that tells me). However, do you think they are going to go into a Business Intelligence system and drill down through all of the data to find what might be the potential root cause of the issue? Do you think that the business intelligence system will have drill down paths to all of the potential root cause data? I do not. This user does not have the time (remember, this person is overseeing 20 bank branches) even if they had the skills to do so.
The problem, he says, is that BI is sold on the strength of its automation, when in fact the most important functions of BI can only be executed manually:
Why can’t that knowledge be captured in a system? Why can’t someone design a business intelligence system with actual intelligence about the business domain built-in?
Go read the whole thing at Jim's blog.
Putting the intelligence back in BI [BlogERP]