Your views, experiences on webi adhoc reporting
We have a boxi 3.1 base version implementation. Our user base consists of non-technical users, but they are very proficient in Excel and can churn out very high quality management reports too using excel.
We are trying to encourage our users to use BO/WEBI for their complete reporting needs, instead of exporting data into excel and create those reports. We have faced some challenges where it's hard to compete with Excel in terms of it's charting/visualization options.
I would love to hear your feedback on efforts you might have had to take to get your users comfortable with webi/ad-hoc reporting, steps that worked, bad ideas etc. You are welcome to share anything from high level strategies and training/BI adoption plans to individual sharing.
Thanks in advance for sharing.
Edited by: ramaks on Apr 9, 2010 6:12 PM
Thank you for clarifying your angle
just thinking of ways to let them leverage complete enterprise tool-set capabilities.
My answer: training and case history. Be open to conducting training on a recurring basis, even if the attendance is sparse at first, having a consistent and clear-cut traiining plan, and executing it well in a hands-on classroom setting will get the ball rolling. As unpopular as it may seem, having some type of "mandatory" hands-on training before granting a userid/password to the system may be one way to start (but requires full support from the higher-ups too). Case history is to observe one of your groups "doing their thing", then devising the standard report/schedule, etc, and show how much time can be saved. Presenting your findings could be done in a periodic newsletter, or a "case history" corner on your web site. The goal is to not disparage anyone, but to come alongside and show how using basic features of BOE can make a person's life easier.
Again, just some thoughts in continuing to think through the "which comes first: the chicken or the egg" syndrome.