If you make it to the 8th paragraph, you may learn that "BI" stands for "business intelligence".
And what it actually means is "visualizations and dashboards". Why make decisions based on analyzing the data from a report when you can get a vague impression from a pretty chart and go with that instead? IMX, the core problem is that all BI software is built around the idea that everything is a financial value that can always be arbitrarily aggregated meaningfully, and that looking pretty is more important than pre…
I used to work directly modeling data for various sized companies on behalf of two different BI sellers.
As I see it there are perpetually two problems:
1. BI is marketed at and sold to anyone needing any kind of data visualization capabilities, and most packages I've worked with can do this but that's not really where they shine.
2. They really shine when you have huge amounts of data stored in different systems and you are trying to build an environment up where you can coalesce that data into one place and then visualize it, and you need to routinely report on these sorts of things.
I think most BI solutions fall into the same space as JIRA does -- highly-customizable solutions that are sold as "Turn-key" without any warning ahead of time that it'll require someone (or several people) on your team become ridiculous levels of expert in areas that don't necessarily help the business.
It's a specialized skill most places don't really need when what they're looking for is a simple reporting package that can connect to just any database.
Similarly, I saw a lot of people with BI insisting they had "Big Data" and thus "needed" things like Hadoop in order to process their stuff, when in reality the MySQL, SQL Server, or Oracle DB they were already invested in would do the same job faster 99.9999% of the time.