Tuesday, December 30, 2008

What Might Go Wrong in Business Intelligence in 2009?

Timo Elliott wrote an interesting post in his blog, about What Might Go Wrong in Business Intelligence in 2009?, where he lists what he thinks what might go wrong. Below is a summary of his list:

1 - People will try to do without BI -- and fail
BI is important, but rarely urgent. In dire economic conditions, some organizations will be too busy trying to survive to think about doing analysis. But action without analysis is called guessing, and is unlikely to help.

2 - People will revert to hand-coding and excel macros -- and waste a lot of money
Corporate cutbacks, "thou shalt not buy anything" policies, and new levels of sign-off will encourage some people to attempt to do analysis without extra software investment: hand-coded data extraction in SQL, data manipulation using Excel macros, etc.

3 - Organizations will implement standards -- but omit to change organizational structures
Keen to reduce costs, organizations will standardize their BI environments -- but will balk at the perceived cost of implementing a dedicated central BI organization. The result will be lower procurement costs, but without a BI competency center there will still be silo BI projects.

4 - Business units will find it easier than ever to implement their own solutions -- to the detriment of the company as a whole
Chafing against corporate BI standards that they didn't chose, business units will find it easier to ever to implement their own "shadow" BI systems.


The answer? Step one: BI organization
What can organizations do about this? Now more than ever is the time to implement BI shared services or a BI competency center. The first goal of the team should be to prioritize BI projects and consolidate existing projects and solutions, eliminating waste and increasing information flow.

I understand his concerns, and I agree when he said "Now more than ever is the time to implement BI shared services or a BI competency center." The companies need to organize their BI projects,and create a BICC is important to integrate and consolidade business and analytical intelligence process, and also ensure that BI knowledge (BI values, concepts, and technology) is shared throughout the organization.

No comments: