We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.


Limiting Business Intelligence Project Failures: Some Practical Hints, Part 2

Originally published August 10, 2010

This two-part series concludes by offering tips for developing business intelligence solutions based on addressing business pains and gaining overall information availability to make more informed decisions.

You must be a member to view this content. Membership is free and gives you full access to all content across the Network. Login or sign up today.

Sorry there was a problem with your login or password. Please try again.
Member Login

Not a member? Signup now!
Forgot your password? Get it now.



 

Comments

Want to post a comment? Login or become a member today!

Posted August 10, 2010 by

Interesting post.

I would like to address issues 3 and 4 - good advice, but utterly impossible to follow.

Actually most BI implementations fail just because they are required to do so much planning ahead of time, while there really is no way for a consumer to know in advance what the requirements are and whether what they need now is what they would need 6 months from now.

Getting to the point where the "consumer" can provide REAL feedback, not theoretical feedback using traditional business intelligence software means extensive IT effort, i.e. significant upfront investment.  This cycle repeats until the consumer is happy, and would usually take months or even years.

Incidentally, I wrote a blog post regarding this exact issue if you're interested.

http://elasticube.blogspot.com/2010/08/catch-22-of-traditional-business.html

 

Thanks,

Elad

SiSense

Is this comment inappropriate? Click here to flag this comment.