Pitfalls to be Avoided in Business Intelligence Implementations -Part 2
Based on the interest developed from my earlier blog on :
Pitfalls to be Avoided in Business Intelligence Implementations at http://www.infosysblogs.com/oracle/2009/07/pitfalls_to_be_avoided_in_busi.html#more , and call for more to share around this, I would like to extend it based on my own experience of working on BI projects and discussion with colleagues on problem faced.
Maintaining a steady process that provides decision takers access to crucial business information is directly associated with corporate objectives and is one of the major goals of upper management. More emphasis is given in the current scenario is on availability of information by decision – makers on -demand and to achieve this need to have an ongoing, consistent and standard process is there. Business Intelligence is capable of providing thorough understanding of commercial; provide historical, current and predictive view of business. Sometimes BI implementations fail to convey or inform a decision-maker because the information presented was unclear. In the last blog also we have highlighted on some items that are best avoided and will expand the list a little to have more success stories.
It is always advisable to design the measurements the way that give users what they need other than let them calculate for items which system can compute.
BI Layouts exceeding the single page also has an impact on how it is read and interpreted. While designing layouts utmost care should be kept to fit it on a single screen. Breaking the data and organizing by means of drill down / link over multiple screens should be explored.
Design of BI Screen Layout is a very critical factor. The amount of real estate consumed by the information and its arrangement has a significant impact on how it is perceived by users. Using the correct mixture of visual displays to gain users’ attention to critical data reduces the time needed to review and consume the information.
Providing users with too much information and detail in a single view should be avoided. BI designers want to provide as much information as possible; however, too much data presented at a single time might turn up as confusing for users and inefficient.
Hopefully, all of you who are working on Business Intelligence programs are already taking care of this. If you are not giving attention to either of these, this might be a signal of potential problem in future. Please think, discuss and plan to avoid and make your implementation a success story and share your experiences
