Simple answer to your question is " Get respect for your reports " from within & outside your organization.
Publish more action oriented & comparison reports, which are must for client executives. Also training to such executives shouldn't be just navigation based , but it must be supported with few case studies within QV document . These will help them understand that its not only charts & excel lookalike tables/pivots , but it is more than that in terms of interaction of data.
Just to give small example, we developed a "Retail Analytical Suite" for our client. During UAT, we bookmarked few cases to show them how they can interact within charts & get next course of action. We created cases based on their real time "Promotion " & showed them that apart from normal "Promotion Response Rate & Evaluations" how much more they further analyze by selecting filters on different set of reports. They wouldn't be able to realize so, if we could have given them basic navigation training . After that results are fabulous, and now they are using our reports for "Target Audience" saving a lot on Campaign costs .
What I personally feel is, 70-80% of reports are "without intelligence" or just delivered because of requirement and that's the point where one is loosing its interests .
For an organization to successfully leverage its investment in business intelligence, simply having the best technical infrastructure is not enough. Other factors, such as provider the right users with the right tools, having an organization setup that is built to take advantage of the BI insight, are also very important
Below is what i think, should be considered in order to deliver successful business Intelligence project..
1. This project should be Initiated and Owned by Business Executive / Champion ( He should be c level executive).
2. The Time line of BI Project should not exceed more than 4 to 5 months, as business needs keep on changing every quarter or two, so if you plan a BI project to deliver after 6 months or 1 year, then there are huge chances for this project to FAIL.
3. Business Analysts or SME from Business should be doing the business requirements, and should make sure the business requirements are met for business needs. He should be working with Business and IT to get the things done.
more to follow.
This is an interesting and useful thread. However, most of the posts seem to focus on the end product i.e. how users can get value from the reports that QV enables a company to produce.
This is of course important, but in order to produce reports, a company must first: install and configure the software; point to/manipulate data; create qvds; create shedules etc. before designing any reports.
What are people's thoughts how to successfully carry out these stages?
Every client has a story to tell. Let them tell it. Ask questions and make notes, move back, and return with a solution suggestion that is directly connected to the clients specific demands. You may show 1000 cool QlikView applications. If they won't solve the clients specific needs - they wont invest.
Don't just throw up a bar chart just because you can, and you use to. How will it solve the specific demand.
A successful QlikView project should be an iterative process, where each iteration adds new functionality. As the appetite grows, new functionality is added in each iteration. The final solution could very well be a moving target, where each iteration gives new ideas, and input to further discussion and collaboration. Let the solution change as the business need change.
In general all we are understand QV is a tool as none, is easy to resolve including user ... is highly recursive tuning
click, double click, clon, filter, bookmarks, alerts, macro, events, variables, properties, etc, etc
then about of yours points ...
1.- ROI & relation benefic/cost are common points of negociation including times
For me the important cost is the design data (schema) embodied in the script moveover then automation, all documented
2 & 3 .- The cost is proportional to expertix of profesional & users
A point 4 is the security, in general left to finish but very important
Moreover by the philosofy oriented to code 0 QV permit projects very transparent no left space to black box as ERP, CRM & BPM projects, for me this is key for results in just time.
Very thank y your time.