5 BRUTAL Truths About Qlik Sense Most Teams Still Haven’t Accepted

Read time: 2.5 minutes

What Leaders Must Fix Before Qlik Complexity Becomes Operational Drag

1. Stop Viewing Qlik Limited to the Analytics Function

Qlik is not solely about analytics; it is now involved in a wider variety of things, including:

• Data integration

• Governance

• Automation

• AI

• Process flows via applications.

As such, it requires you to think at a platform level, and not just within the context of dashboards.

2. Redefine Roles for Operationalizing Qlik as a Platform

The role has transitioned from:

• Developing Apps

To:

• Defining Semantic Logic

• Governance of Apps

• Enabling Access to Apps

• Scaling Apps

Modern Qlik teams need operators, not just developers.

3. Centralize Semantic Ownership

Without centralization rules for governance associated with KPI’s, the result will be:

• Differentiating KPI’s across apps

• Sprawl of apps

• Fragmented business logic in apps

Standardize the following:

• KPI Ownership

• Dimensions that are governed

• Certified Apps

Trust will be built through alignment.

4. Improve Your Architecture Prior to Scaling AI

AI can compound inconsistency quickly. Before you begin deploying AI, consider investing in:

• Quality of metadata

• Governed Association Models

• Clear definitions of the business

To be prepared for AI, an architectural discipline is very important.

5. Treat Qlik as Similar to a Business Critical Infrastructure and Fund Accordingly

Utilizing dashboard-based personnel to run a platform-scale analytics environment cannot work. Qlik should be viewed as:

• A Platform

• A Product

• A Business-critical System

An effectively reliable operation requires an investment in operations.

💡Key Takeaway: 

Qlik didn't stop using dashboards… it moved past the old model it had used to develop them.

The Qlik teams who are succeeding are not creating additional apps, but instead creating more robust decision platforms than previously.