The purpose of both the product is different.
QlikView is the best when it comes to guided analytic. Meaning your IT would take the requirement from business and build the report.
QlikSense is best when it comes to self BI. Meaning you wont require much intervention of IT to create dashboard. Business users them self can create their own dashboard and do their analysis.
In your organization you would need to find the proper user base who will be in need of such self BI power. Like analyst who will be more beneficial with Qlik Sense as they can play around the data which they want.
Qliksense can reduce the work load on a BI team as its a self service tool. Also you have the leverage to visualize data in a very intuitive way and response to any screen resolution/device.
You have more features like, the story creation and custom visual building using extensions which can give a whole new look of your data.
these are good theoretical answers - thanks . But does anyone have any real business examples of how large Qlikview and Qliksense installs co-exist where Qlikview was already well established. Any examples mto
Hi Tim, I hear you loud and clear and though I am not experienced in this area, I do know people that can help. Allow me a few days to connect with them and see if they can produce some meaningful answers.
(Thank you Sangram and Kaushik for the replies, your participation is always appreciated and note worthy.)
When the time comes, please mark the appropriate replies as CORRECT / HELPFUL so our team and other members know that your question(s) has been answered to your satisfaction.
One thing you might do is look at it more from the standpoint of delivery and not as much the data. It is true that many of our QlikView customers using Qlik Sense will leverage the hard work they've put into building their ETL, apps, QVDs, etc, because why not? It makes sense to leverage that. You can take a QVD or a QVW built in QlikView and expose that in Qlik Sense. That is the data side and quite easy.
But the thing that Qlik Sense is enabling is a different delivery. Take a look at this post Scaling Visual Analytics with Qlik Sense and if you look at the 'delivery patterns' slide in the video, I'm willing to bet your QlikView deployment is focused around the top left swim lane. The idea is that Sense can open up the other swim lanes, too, and with that additional delivery, you will enable new players to become authors of new ways to look at things and share it, be it with new data sources, or new visualizations on top of existing data sources.
Some of the ROI then comes from increased velocity, of course, but when a user is empowered to not just consume, but become an author, and share, your organization will benefit from new insights that can be acted upon. So, that may be a little theoretical, too, but hopefully it helps, and if you watch through the first half of that video, you should get an idea of some of the capabilities in Qlik Sense that you might not yet be aware of. Hopefully that helps to spark some ideas and go after some use cases that might currently be under-served.