Qlik Sense for Enterprise Self-Service BI
Qlik Sense Enterprise
Overall Satisfaction with Qlik Sense
We were already using Qlik View as our enterprise dashboard solution. When we were looking for a self-service BI solution for our business users, Qlik Sense was chosen as it dovetailed nicely with our current architecture and offered several features that we are looking for.
Qlik Sense is now currently deployed for a pilot set of users across the organisation. Together with the deployment, we also rebuilt our data models, made granular data available, and provided training to our users so that they can help themselves to get answers to questions they have without having to wait for IT to service their requests.
- Ease of use: Qlik Sense is relatively simple to pick up once users start playing around with it.
- Works on mobile devices: Unlike Qlik View, Qlik Sense is designed to work with mobile devices.
- Listening to customer feedback: Qlik Sense seems to be listening to customer feedback and addressing missing features and issues with every release.
- Fast release cycle: Qlik Sense comes with a fast release cycle - new release every 3-4 months, if an important feature is currently missing, it may be in the next release.
- Still maturing: Qlik Sense is still a relatively new product and there are missing features. The good thing is the fast release cycles that addresses some of these issues. E.G. Users were not able to upload data files themselves initially but this is now addressed in a later release. The issue now is that the data file that is uploaded sits in the C drive and cannot be reconfigured within Qlik Sense and has to be fixed using a Windows junction which is not ideal.
- Fast release cycle: The fast release cycle has a negative impact as well. Internal testing efforts to certify everything continues to work is not insignificant.
- Controls: There are 2 sides to the control issue. There is a lack of ability to control stuff like how much space a user is using. There is on the other hand to much restrictions on users in published apps - they cannot even see the data model, create their own dimensions etc which severely limits the amount of self-service they can do.
- Map layer support: The current control supports only a single geo-spatial data layer. It would be great if it can support 2 or more - this can be done currently by buying 3rd party products (but support for those products in our area is not good) or building an extension ourselves (but we would rather not be doing that).
Microsoft Power BI was also considered as most of our users were familiar with Excel. However, we found Qlik Sense to be a better fit for our purposes.