QlikAdvice: Give context to your data

Hello everyone and welcome to QlikFreak. This will be our first post in a new category called QlikAdvice, where we’ll talk about dashboard design in a broader sense. Instead of focusing on technical stuff (we already cover that in our Just Qlik It posts), this section will contain functional tips that will help you present information in an efficient and elegant manner. These principles will be applied to Qlik apps (QlikView and Qlik Sense), but you’ll find out that most of them are useful in other domains as well, from web design to NPrinting Reports, or even PowerPoint presentations (or should I say Qlik Sense Stories?). Today’s topic is an old classic you should never forget: context.

QlikAdvice: Give context to the data to improve the decision-making process

When it comes to analyzing data, context is everything. If you present isolated figures, users will have a hard time trying to find out the real story behind them. As a Qlik developer, it’s easy to fall in the trap and start shooting random KPIs right away. For example, I could start my sales dashboard with something like this:

31_01

OK, we sold 3.56 M in 2016, that’s cool. However, what does this tell me? Was it a good or a bad year for our sales reps? Well, it all comes down to a simple question: “compared to what?”. In order to evaluate their performance, it would be better to have some kind of reference. For instance, the budget:

31_02 Continue reading