Qonnections 2018 Reflections

I just wrapped up the week at Qonnections 2018.  I found it to be an inspiring conference and the most positive I’ve attended in years.

What was inspiring?  The cognitive insights demo was fantastic.  This is the future of BI.  We have well understood principles and algorithms recently formalized in the discipline of machine learning. Let’s incorporate them in the tool.   If the goal of data visualization is to amplify cognition of data, then I would say cognitive insights is to visualization as visualization is to data.

On the technical front, the previews and demos of elastic cloud and Qlik Core provided me the “aha” moment to understand how the Qlik Big Data Index will be possible.  I can see how many distributed indexing and aggregation engines can provide massively scalable access to a data lake.

The most exciting announcement to me wasn’t technical, but on the commercial side.  For a “small uptick in maintenance”,  QlikView  users will be entitled to use the same license for Qlik Sense.  To me this signals a new strategy for dealing with the two products going forward.  There was also a roundtable discussion on feature gap between the two products and the announcement that some level of pixel-perfect control will be available in Qlik Sense.

Taken together with main stage comments from CEO Mike Capone and CTO Mike Potter,  I’m seeing a needed correction to the “two product strategy” which so heavily favored Qlik Sense.  No one expects QlikView to live forever,  but loyal QlikView customers want to adopt a new product only when they see that it clearly benefits them.   Ideally we will see a converging product that blends the best features and lessons learned from both products.



9 thoughts on “Qonnections 2018 Reflections”

  1. Rob, have followed the blog for a while (thanks for the great content over the years) . Your booth was right in front of ours and had hoped to come over and say hi but alas, time…

    I have to agree on your insights and am excited to see not only what the June release brings for cognitive learning but where future releases will take that.

    Core is also a product that as a company we’re pretty excited about and the doors that will open. I think the conference was buzzing this year and have every reason to feel excited about the future of the product.

  2. Hey Rob – good to catch up again.

    I agree – for me the single biggest announcement was the much more sensible approach on QlikView to Qlik Sense licensing migration. Our clients are almost all enterprise with significant investments in QlikView, and this one move immediately removes the “new purchasing decision” aspect of a Qlik Sense migration.
    Qlik’s technology is marching on full steam ahead, but the licensing so often falls waaaay behind. The inside scoop is Mike Capone was in a high-level meeting on one of his first days on the job and when the current model was explained to him he simply swept it aside proclaiming how ridiculous that was!

    Of 48,000 customers, 36,000 are QlikView customers. Of those, 32,000 are still on QV11.2! So it is wonderful to see announcements that encourage a migration to QS rather than making staying on QV punitive.


  3. “We have well understood principles and algorithms recently formalized in the discipline of machine learning.“
    I wonder how you did. At least there is not much behind of what we have seen related to the Qlik products so far. And, it was no deeper explanation. So, I would agree if Qlik would tell us more details about what algorithms they already have integrated (no AI/ML I can see here so far, just basic stats) or will be implement into the product and how this will work, or will help, and how (!) we can control it..

    1. Admittedly short on details at this point. I look forward to seeing more details and getting my hands on it.

    1. Ralf, I did not attend any of the detail sessions on BDI — I believe you did and may have more specifics to add. I see Qlik Core as a packaging of the micro services architecture and it’s that architecture that can enable distributed processing. So perhaps not “Qlik Core the product” as a component of BDI, but the design pattern that has enabled Qlik Core.

  4. Hi , can you elaborate , “QlikView customers can user same licences for QlikSens”. You mean if, a customer have 5 named cal and 10 doc cals, will they transfer into QlikSense with 5 professional and 10 analyzer licences?

    1. I’m not sure exactly what the details of the single license entitlement will be. Details were not provided at Qonnections to my knowledge. Stay tuned for more announcements from Qlik as I’m sure there will be lots of interest.

  5. “Taken together with main stage comments from CEO Mike Capone and CTO Mike Potter, I’m seeing a needed correction to the “two product strategy” which so heavily favored Qlik Sense. ”

    I wasn’t there to hear the comments, but I’m quite curious what they were to instill this confidence.

    90% of the content posted by Qlik employees on the QlikCommunity website is aimed at QlikSense, as is the entire landing page. QlikSense gets monthly content releases while QlikView gets one per year and most of that is technical aspects and not features. Simple, low-hanging QlikView fruit such as a much-needed visual facelift or the recently-fixed-at-long-last xlsx export often goes ignored for years. Qlik seems content to release virtually no new charting capabilities for QlikView, requiring the use of external content.

    Based on the above, it’s hard for me to say Qlik is deviating from its one-product track, while they do the bare minimum to keep QlikView customers using QlikView (or migrating to QlikSense). I do believe they will continue to keep QlikView on the back burner and give it at least a modicum of effort, at least as long as more than half the customer base is using QlikView – but as made evident by the joint-licensing aspect, they’re clearly pushing very hard in that direction (assuming the “small uptick” is actually small, and not ~50% as originally floated).

Leave a Reply

Your email address will not be published.