Item: Qlik Sense
Rating: 10
Author: Jay Mistry

Use Cases and Deployment Scope

Currently, Qlik Sense is being used across the Finance function but the intention is for Sales/Marketing and the Supply Chain function also to have access as we roll out projects relating to those areas. Many of the business problems we are trying to resolve are around having one source of data and a one-stop-shop to access that data.

Pros and Cons

Visualizations that interact with the user.
Associations help users understand the data and can provide answers.
Handling of large volumes of data with ease.
Restrict who can see what especially with functional data.

From a development point, be able to replicate variables more easily and be able to use the find/replace function.
More flexibility around waterfall charts and making them easier to build.
Ability to do cyclical groups (as in QlikView) so save canvass space.

Return on Investment

Less manual input and reduction in Excel workbooks.
Man hour savings from month-end reporting preparation.
Less time generating reports and more time analyzing.

Alternatives Considered

QlikView and Microsoft Power BI

We were already using QlikView so moving to Qlik Sense was the right step. From a development point, this meant the learning was not as steep as when we first started using QlikView. We also use Power BI where the volume of data is a lot less than in the Qlik Sense projects.

Other Software Used

QlikView, Microsoft Power BI

Likelihood to Recommend

Qlik Sense is ideal where is there is a large volume of data (millions of rows), where there are many data sources and information needs to be restricted as to who and what they can see. In terms of development time required, Qlik Sense may not be suited where data rows are only in the thousands and where information can only add value if presented as tables (I.E., where visuals are not required).

Qlik Sense for Quick Insights!

Software Version

Overall Satisfaction with Qlik Sense