Weird experience in Business Intelligence projects
Case of virgin Business Intelligence reports
Yes, users know to be quite painful in repetitive pushing for requested business intelligence functionalities or contents in form of reports. We need reports a.s.a.p. or even better “yesterday”. It is essential for our board, it is a must… . Independent observer might conclude that survival of company was pure luck without requested reports. Here comes the beauty… after finished and implemented reports users do not open them…
What?
BI “users” dare to state following in defense and even for attack:
”Report is not reliable, we can’t trust it.”
”We have other priorities and did not have time to test it and to use it”, (this is favorite excuse)…
”We don’t need it any more, process has been changed”
Due to organizational changes those who asked for request diapered.
and many other reasons are named for not using something what was being heavily deployed and implemented.
How to stop deploy and implementation nobody is going to use? There are several unpopular for business action steps, first they have to make proof and will is request really needed:
Business who orders deploy need to make detailed and quality specification.
Business has to proof with business case is it reasonable to invest Capex into their order. Meaning, is there a profit behind request and this is hard to defend since most of benefit will be in faster time to make analysis and reports.
Many requests will simply disappear on this two thresholds and reasons for not using built business intelligence reports will be minimized.
Related posts, articles and documents:
loading...





Business-intelligence-secrets…
[...] something about business-intelligence-secrets[...]…
loading...