Your Qlik team inherited IT incentives. That is the whole problem.
Last week I described a typical week of a senior Qlik developer. Deployment coordination. Manual version comparison. Broken releases. Zero actual development until Thursday. Many of you said: “That is my week.”
Here is why it keeps happening.
When your analytics team reports into IT, it absorbs IT priorities: uptime, stability, “don’t break production.” All reasonable. All correct. And all completely backwards for a team whose real job is turning data into business decisions.
Think about who your senior Qlik developer actually is.
This is a person who understands your revenue model because they built the data model behind it. They know why that Set Analysis expression exists — not because they memorized the syntax, but because they sat in a meeting with Finance and learned what “recognized revenue” actually means in your company.
They are not just technical people. They are one of the very few in the organization who speak both languages: the language of data and the language of business. They understand database joins AND margin calculations. Load scripts AND customer churn logic.
That makes them rare. And incredibly misused.
Because instead of sitting next to the business and helping teams make better decisions, they are stuck playing human version control. Living deployment logs. The person everyone pings before they click Publish.
Every other engineering team has CI/CD. Automated tests. Rollback in one click. Version history going back months. They ship on Tuesday and sleep fine on Tuesday night.
Your Qlik team has a shared drive with files named “Sales_Dashboard_v3_FINAL_fixed_REAL.qvf.” And a senior developer who checks with two people before anyone can deploy.
This is not a discipline problem. This is an infrastructure problem. Your Qlik layer is probably the only mission-critical system in the building without basic engineering tooling.
And the real cost is not wasted hours. The real cost is strategic.
Your best people — the ones who could be sitting with Marketing figuring out which channel drives margin, or with Finance building a forecast model the board actually trusts — those people are coordinating file transfers instead.
You hired business-minded analysts. You turned them into deployment coordinators with developer salaries.
The fix is not “be more careful.” The fix is to give your analytics team the same engineering foundation every other team already has. Version control. Automated deployment. Rollback. Audit trail.
Free them from IT plumbing. Let them do what they were actually hired for: make the business smarter.
#DevelopersLifesMatter
This is the second post in the #DevelopersLifesMatter series — stories about the invisible work that Qlik developers do every day. Read the first post: The Senior Dev Tax: Why Your Best Qlik Developer Isn’t Developing. Follow DatalabsUa for more.
No comments yet.
Leave a comment