The dashboard nobody opens

There's a scene that repeats itself in practically every company that decides to invest in Qlik Cloud, and it usually starts with enthusiasm: the team responsible for the platform spends a few weeks building a polished dashboard in the Hub, with the right indicators and the filters in an order that makes sense, everything carefully reviewed, and when presentation day arrives everyone applauds, someone takes a screenshot to send to the leadership group, and the impression left is that this will change the way the company makes decisions. The problem shows up about three months later, when you open the access log and find that the dashboard was opened by five people in the entire period, almost always the same five.

At Cluster we have seen this happen often enough to stop treating it as bad luck or as a one-off failure of a specific client. It isn't that the dashboard is badly built, nor that the data is wrong, since it's all there, correct and updated every day. The reason is simpler and a little more uncomfortable to admit, because most of the people the dashboard was built for never had, and probably never will have, the habit of opening a dashboard to get their work done.

It's worth separating two things we tend to treat as if they were one. On one side are the people who deal with data all day long, the analyst and whoever works directly in Qlik, people who enjoy cross-referencing tables, building a new view and testing a hypothesis. For that profile, the Qlik Cloud Hub is exactly what it needs to be: a powerful, complete environment, full of paths to explore, filter and dig deeper, and it's precisely all that power that makes it the right home for anyone who lives off investigating data. On the other side is everyone else in the company, which is where the majority lives: the salesperson who just wants to know whether they hit the month's target before calling the next client, the store manager who needs to check a stockout in the rush of putting together an order, the director who wants a round number in mind before walking into a meeting. For people like that, opening an environment designed for exploration means running into far more than the occasion calls for. There's nothing wrong with the tool; what happens is that these people didn't come to explore. They came for a specific answer by the shortest possible route, so they can get back to what they were doing.

It turns out this second crowd is almost always much larger than the first, and that's what turns the mismatch into a real problem. When we look at the actual use of Qlik licenses inside our clients, the pattern repeats with an almost boring regularity: a small group uses it a lot and a wide majority barely logs in. These are what we call dormant licensees, people who have paid access to Qlik Cloud and who could be deciding based on data, but who in practice keep asking for the number over WhatsApp from someone who masters the platform every time they need it. This dynamic ends up charging a price from everyone at once, because the business becomes hostage to a middleman, the data team slowly turns into a kind of help desk answering the same questions several times a week, and the investment in Qlik, which should show up as value, ends up being read by leadership as one more line of cost that's hard to justify.

The most common reaction to this is trying to turn everyone into an analyst, with a workshop, a recorded tutorial and a nice manual that almost no one opens after the first week. It helps a little, but it always runs into the same wall, because deep down you're asking someone to change the way they work because of a tool, and that's a trade almost no one truly accepts. The salesperson will keep wanting the quick answer instead of a free afternoon to learn how to build a chart, and it makes complete sense that it's this way.

That's why we believe it makes more sense to flip the logic inside out: instead of pulling the person into an analysis environment that isn't their world, the path is to bring the answer to where they already are, in the format they understand, which in practice means being able to ask in plain language and get the number back without needing to know where it's stored or how it was calculated. None of this replaces the Hub or the work of whoever builds the data; on the contrary, it depends entirely on both, because the model still lives in Qlik Cloud, the calculation ruler remains the same for everyone and governance stays exactly where it always was. What changes is only that last stretch of the journey, the one that separates the finished data from the person who needs it to decide something.

That stretch is what we call the consumption layer, and it's the reason NewHub exists. The idea was never to compete with the Qlik Cloud Hub or to suggest that exploring data has stopped being valuable, but rather to recognize, without drama, that most of a company will never be analysts and that this is perfectly fine, because these people don't need to learn how to dig, they need a short path to an answer that already exists somewhere in the model. If you already have Qlik Cloud and still feel that data doesn't circulate through the company the way it should, it's quite likely that the problem is neither the data nor the platform, but precisely that last stretch, and it's about that stretch that we intend to write a good deal here.