As we just released our new iOS app, I started thinking more about where the real value lies in QlikView on Mobile. In my opinion, it's about empowering the user.

QlikView users fall into a spectrum, from IT administrators and data analysts to line of business staff, managers, and executives. Each type of user has a different set of challenges and objectives for BI.  With mobile BI, the delivery vehicle may be different, but the goals are relatively the same:

  • Business users want to gain relevant insights to make better decisions, factoring in the variety of questions that arise in mobile environments
  • Power users / app developers want to rapidly and easily create analytic apps that offer needed information to a variety of business users on the go
  • IT administrators want to create a manageable and secure infrastructure that serves a variety of mobile user communities, while ensuring data quality and governance across devices and platforms

Pretty simple, right? Well not really. The word here that makes things complicated here is “variety.”



Variety is the spice of life, but it can also make life challenging. Mobile environments are diverse in nature and BI users on the road typically face new and evolving challenges in their day-to-day lives. The unpredictability of users’ information needs in mobile environments affects everyone in the value chain including business users in the field, the developers that provide business users with analytic apps, and the IT staff that manage the data and infrastructure.

So the value that QlikView on Mobile offers is empowering all our user communities to better handle variety. A single QlikView on Mobile app enables a business user to answer a wide variety of questions and follow-up questions through simple taps. This means that a developer can deliver fewer apps that address more needs, replacing hundreds of limited-interactivity mobile reports in the process. IT administrators can deploy apps across mobile and desktop platforms,ensuring enterprise-class security and promoting data governance regardless of what device is used to access information.

With the new QlikView for iOS app on iPad, we address the need for disconnected mobile capabilities with a similar aspiration. Our approach is to enable business users to explore and discover all the data in the QlikView app when connected and then give them the option to take their unique views with them when disconnected. By enabling individuals to define QlikView bookmarks and then download these views for offline availability, we promote flexibility for large communities of users to serve their own needs. This means more relevant information and insight at the time and place of decision, even when Internet connections don’t exist.

For more information on the new QlikView for iOS app, check out the web page.

When it comes to the topic of Big Data I have to make a public admission. I have a split personality. On the one hand the geek in me, from years spent as a software engineer, relishes the challenge of installing my own Hadoop cluster, writing MapReduce algorithms, and running all sorts of performance tests to see for myself how amazing the technology is. On the other hand, as a pragmatic product marketing manager (yes, I did take the class), I just want to get stuff done and understand my data ASAP, without writing a single line of code.


A series of deep questions dawned on me. Why do I think the way I do? Why do I sometimes prefer one thing over another? What drives me to make certain decisions and not others? The quest for these answers led me to a surprising connection between our human bodies and Big Data. This connection led to five key insights which I will share through a series of blog posts.

I first searched the web for some interesting statistics on the human nervous system. If Big Data is described by volume, variety, and velocity, how does that relate to the human body? For example, our eyes have 1.2 million fibers in our optic nerve. Given that our eyes can detect flickering at around 30 times per second and we have two eyes, I’m making a rough estimate that our eyes transmit over 60 million signals per second. Our nose has 12 million receptor cells. Receptor cells fire at various intervals, usually faster when there is a new stimulus and slowing down under repeated stimulus. That’s why when you walk into a coffee shop you are at first intoxicated by the wonderful aroma but after you’ve been inside for a while you don’t notice it anymore. So between our other sensory body parts such as the tongue, ear, and the largest of all, the skin, our brain is receiving at least hundreds of millions of signals per second – covering both variety and velocity.

How about volume? The newest figures suggest we have around 86 million neurons in our brain which record a massive amount of sights, sounds, sensations, etc. Each neuron is equivalent to much more than a transistor on a CPU because each one is connected to ten thousand other neurons, on average. That means we have roughly one quadrillion (1015) connections in our brain. So our brain is basically an amazing massively parallel and scalable processing device with co-located storage – which sounds like many Big Data architectures, doesn’t it?

Where am I going with this? You are Big Data! To better understand how organizations can get value out of Big Data, it might be useful to study the human brain in a little bit more detail because it has been fine-tuned over millions of years. In my next blog post, I will delve deeper into how our brain uses all this Big Data.

Uniquely QlikViewflat_qlikie.png


When a product is unique, it is distinctively characteristic - possessing traits and qualities that distinguish it from others.  Here in the United States, one such popular creation comes to mind - Dr. Pepper. Since the late 1800s, it is still marketing its original taste to be unlike any other soft drink. “It's a different kind of drink with a unique taste all its own.” - 1

QlikView is also unique in its own right. It provides a super fast and natural path for businesses to make decisions with its associative search capability; providing immediate insight in hours and days instead of weeks and months. Combine this with the contagious enthusiasm of the QlikTech staff and a lively QlikCommunity and you have what is uniquely known as "the QlikView way”.

That being said - it should be of no surprise to also hear that QlikView Expressor provides Metadata Management - “the QlikView way”.  In order to fully appreciate this idiom, we need to dissect the term “QlikView Metadata” into smaller digestible components.


Types of Metadata

In my first article, “Let’s Not Argue Semantics – I Beg to Differ”, I introduced the importance of semantic layers and its metadata. Metadata’s purpose is to increases the value of data by providing additional context. Within in a QlikView ecosystem there are two types of metadata that can described. The first one is QlikView deployment metadata. It contains data about the structural elements that make up a QlikView deployment. A QlikView environment holds tons of metadata locked away in QlikView documents such as QVDs, QVWs, QVXs as well as server and publisher logs. This valuable metadata, when extracted and associated with one another, can provide meaningful answers to IT professionals when asking the general question “What’s going on in our QlikView deployment?” The QlikView Governance Dashboard, a free application powered by QlikView, is designed specifically for that purpose; providing metadata management on top of QlikView. It allows IT to see how and where data is used, while enforcing data governance, best practices, efficiency and effectiveness of the QlikView estate. 

The second type of metadata that can be defined in a QlikView deployment - is defined on the actual data that is used to make decisions. This is your traditional organizational or source data available from data warehouses, database tables, structured and unstructured files, host applications and other sources. This sort of metadata is typically created to shield users from the complexities of the underlying data source – such as its origin, referential integrity, cryptic field names, complex calculations, business rules and data types.  When stored in a centralized metadata repository, it provides a reusable and consistent approach for development and analysis of business discovery applications -  in turn reducing development time and improving overall data confidence among business users. With the introduction of QlikView Expressor, QlikView applications can now leverage its metadata, therefore managing what I call “metadata-driven” QlikView applications.  The benefits of using QlikView Expressor to manage data for QlikView become more relevant in larger QlikView deployments where there is a need for rapid collaborative development while maintaining consistency, best practices and standardization across all applications.

Over the years QlikView deployments have seen unparalleled success within our customers’ environments. With the addition of the QlikView Governance Dashboard and QlikView Expressor products, data governance practices and metadata management “the QlikView way” can be applied while still maintaining the continued speed and flexibility that are essential to any QlikView deployment.




Michael Tarallo
Senior Product Marketing Manager
QlikView Expressor



1 - W.W. Clements,  former CEO and president of the Dr Pepper/7-Up Company.

With the “Enabling the New Enterprise” theme of “QlikView.next” (the code name for the next generation of the QlikView Business Discovery platform), IT pros will be able to optimize their QlikView environments and offer self-service Business Discovery to growing numbers of users while utilizing ever-growing volumes and variety of data.

Blog Post Oct 2012 pic.png


This theme is about making security, user management, availability, and scalability easily manageable by any customer, not just the largest ones. We want to make QlikView extremely easy to administer and give administrators the same kind of gorgeous and genius experience other users get, with several product scenarios:

  • Global Deployments. With this scenario we will deliver cross-geography clustering (ensuring higher availability) and software licensing to support the new way of working. We will also provide tools and documentation to make it easier for system administrators to recover QlikView servers when a machine fails and another one needs to start up.
  • Improved IT Insight. We are re-imagining the user experience for IT professionals, focusing on making it easier for IT pros to manage users and licenses regardless of whether the deployment covers ten or tens of thousands of users, is in a single or multiple geographies, or has one app or hundreds. One way we will accomplish this is with “QlikView on QlikView”– an interface to the management console for embedding a QlikView app that will enable IT professionals to monitor the health of their environments and identify problem areas and opportunities where they can take proactive action.
  • Safe and Secure. This scenario is about making QlikView security management simple for administrators to understand and configure according to their organization’s policies and compliance requirements. This scenario has two main facets: security standardization and support for emerging technologies.
  • Streamlined Application Deployment. This scenario will make it easier to build and deploy QlikView apps. This scenario is focused on making it easier for developers, testers, and approvers to move QlikView applications through the development, test, validation, and production supply chain in a simple and straightforward way. QlikView users will be able to more easily push QlikView applications into a workflow and through the deployment process.

To learn more about “QlikView.next,” the code name for the next generation of the QlikView Business Discovery platform, download the white paper, The “QlikView.next” Product Scenarios.

This blog post was updated July 29, 2013.


Like most people, I relish a good story. And, like many people, my interest is piqued by pretty much anything that can add an element of lightness and fun to everyday activities like data analysis. Because of this, my favorite “QlikView.next” product scenario is Data Storytelling. (“QlikView.next” is the code name for the next generation of QlikView, spanning multiple releases.)


I recently talked about the Data Storytelling scenario with QlikTech product manager Ingemar Carlo, who is focused on this scenario and development tools used by QlikTech’s partners. I thought I would bring his perspective to you.

Ingemar pointed out some of the ways technology is fundamentally changing the ways we tell stories. ”This is especially true,” he said, ”when you look at advances in the computer gaming industry. With modern video games, the players are active participants in the unfolding of a story. They are not just passive recipients or listeners. There is also a great deal of interesting research going on in academic institutions, and we see lots of innovation especially in the news and entertainment media industries.”

For Ingemar, the highlights of the Data Storytelling scenario in QlikView.next are:

  • There is never just one story. The beauty of a Business Discovery application created with QlikView is that it never has a single story. ”Don't get me wrong,” Ingemar said. ” I still believe that IT departments face the need to design and configure their systems and data sources to contain a single version of the truth. But at best, a single story about the data would be incomplete.”
  • How do you uncover hidden stories? When looking at raw numbers – or even data visualizations – it may not be immediately obvious what the numbers are telling you. The implications and meaning of the data may not be clear. ”What fascinates me about stories from data,” Ingemar said, ”is when they lead you to pose new questions to try to uncover the hidden stories.”
  • Storytelling guides people toward a decision. How do you rally support for the decisions you want to make based on your discoveries? You need a convincing story. The data storytelling scenario in QlikView.next will help users emphasize a discovery they make so that it will lead to a decision. A story can also help remedy the problem of information overload by providing users with a structure or narrative that they can follow.

One of Ingemar’s favorite examples is the work done by one of our former partners, NComVA (now part of QlikTech), which developed advanced visualization techniques for multivariate statistics data.* See the related blog post, ”Bombillo Amarillo and the Importance of Data Storytelling.” For more info about Data Storytelling and the other “QlikView.next” product scenarios under the “Compulsive Collaboration” theme, see the QlikView white paper, The “QlikView.next” Product Scenarios.


* Update July 29, 2013: On May 6, 2013 QlikTech announced that we acquired NcomVA. We are in the process of integrating NcomVA's technology into QlikView.Next.

Business intelligence and collaboration are inseparable; decision making is by nature a collaborative activity. So with the Compulsive Collaboration theme of “QlikView.next,” which is the code name for the next generation of the QlikView Business Discovery platform, we are working on collaboration capabilities that are so natural and easy that people can’t resist using them.

Compulsive Collaboration product scenarios.png

QlikView.next will put QlikView at the forefront of users’ shared decision making with four product scenarios:

  • New AccessPoint. We are refining the concept of a “hub” – an entry point for users to begin their exploration, analysis, and collaboration. The new AccessPoint hub will be QlikView itself; users will no longer go to a separate portal to find apps and content that may be of value to them. The same hub will be the place users go to share, publish, subscribe to, comment on, and search for QlikView insights generated by others. The result? Higher productivity and better decisions.
  • Social Network for Discovery. It’s important for people involved in a community to be able locate others who have published content or exposed insights that may be of interest – all toward the end of increased transparency, higher productivity, and proactive decision making. This product scenario is about making it easier for QlikView users to be aware of who else is in the environment, what others are doing and discussing, and why it is relevant. This scenario draws on concepts from consumer social networking such as following, favorites, and likes.
  • Data Storytelling. People have always used anecdotes and metaphors – stories, in essence – to explain a situation or experience so others can internalize it, act on it, and pass it on. A story, in the context of QlikView.next, is a cohesive narrative that instructs or interests the recipient of the story and shows what, why, where, and when something happened. Users will be able to combine interactive data visualization techniques with descriptive text to build a comprehensive story, and then share this story with others.
  • Share the Journey of Discovery. This scenario enables QlikView users to more easily share their insights with others – even those beyond their QlikView hub. This scenario will also help our customers extend the value of a QlikView chart, graph, or other visualization, or QlikView story, by enabling people to see it in the context of other applications.

To learn more about “QlikView.next,” the code name for the next generation of the QlikView Business Discovery platform, download the white paper, The “QlikView.next” Product Scenarios.

On Tuesday, we announced a new QlikView capability, QlikView Direct Discovery. QlikView Direct Discovery will be part of the QlikView 11.2, which is targeted for availability in December. I am very excited about QlikView Direct Discovery because it will expand the potential use cases for Business Discovery and enable business users to analyze Big Data from sources that have not yet been tapped for knowledge and insights.

QlikView Direct Discovery provides QlikView’s associative experience on top of data coming directly from external big data sources and enables users to combine that Big Data with data stored in memory. What’s really special here is that with this unique hybrid approach business users get the QlikView associative experience even with data that is not stored in memory. This is amazing! With Direct Discovery, business users will be able to explore and analyze any data that is useful for analysis. 

QlikView Direct Discovery focuses on the real need of business users: finding what is relevant in Big Data and being able to explore that data in context with other enterprise data, identifying the relationships in the data – seeing what is connected and what is not – to derive insights and make decisions.

With Direct Discovery, business users will be able to:

  • Analyze in-memory data and data stored in a Big Data back end together, even on the same chart.
  • Explore Big Data freely rather than being confined to a predefined path of questions.
  • Seamlessly analyze data from multiple sources together within the same interface, including Teradata, SAP, Facebook, Google BigQuery and others.
  • Associatively make selections in any of the data sets (in-memory or Direct Discovery) and always see what is associated and not associated with the same meaningful QlikView colors: green, white, and gray.
  • Leverage QlikView’s collaborative and mobile capabilities for Big Data analysis.
  • Conduct visual analysis against massive volumes of data without a complicated ETL (extract, transform, and load) process and lengthy development effort.

We are very excited about enabling business users to tap into Big Data sources and to experience that data in context, with the QlikView associative experience. If you are also excited, stay tuned for more in December!

For more information about QlikView Direct Discovery see the data sheet and FAQ. We are expecting to make the beta version of QlikView 11.2 available on QlikCommunity in early November.

The “Mobility with Agility” theme of “QlikView.next” (the code name for the next generation of the QlikView Business Discovery platform) is about users having access to Business Discovery from any device. Mobility in QlikView.next delivers all the benefits of the overall platform. We are designing the user experience starting with a mobile and touch interface, rather than developing a desktop experience and then modifying it to work on tablets and smartphones. Therefore, all the Gorgeous and Genius, Compulsive Collaboration, and Premier Platform capabilities introduced in QlikView.next will be delivered on mobile devices in the same manner as desktops and laptops. This will create a truly beautiful and agile mobile Business Discovery experience – enabling people to ask and answer new questions while in new situations and contexts out on the road.

In addition to delivering all the new capabilities of QlikView.next on mobile, the “Mobility with Agility” theme is focused on two primary scenarios:


  • Server-Based Development. With this product scenario we are embracing server-based application development as the default. Developers will be able to do their work anywhere, on any machine – including tablets. Wherever they are working they will always get the same interface and user experience. Server-based development will also facilitate collaborative application development more naturally than client-based development.
  • Take Your Data on the Road. With this scenario, we have in mind users who need access to specific QlikView apps while they are not connected to the QlikView Server (offline). Picture a pharmaceutical sales rep preparing for customer visits in a hospital, for example. Users will be able to access QlikView apps on touch-enabled devices regardless of whether or not they are connected to a QlikView Server. They will be able to sync server-based apps and views of data with their touchscreen devices before going offline.

To learn more about "QlikView.next," the code name for the next generation of the QlikView Business Discovery platform, download the white paper, "The QlikView.next Product Scenarios."

If the role of IT in modern organizations is storekeeper rather than gatekeeper (see related blog post “From Gatekeeper to Storekeeper: The Changing Role of IT”), where does IT find the items with which to stock its shelves? If IT isn’t going to be the manufacturer of all the technology an enterprise needs, a supply chain is needed to make the IT store concept work.

IT supply chain.png 

The IT department sources “products” (apps and other technology solutions) by keeping a close eye on what’s happening outside the store – just as a merchandising manager does in apparel retail. A universe of apps develops outside the store, mimicking the supply chains that exist in the physical world between a retailer and its network of suppliers. IT observes trends, watches the growth in new apps, supports apps, and connects to them. The best of the universe is then brought inside. IT absorbs what is successful into the store for other business users in the organization to “buy” and benefit from.

In this scenario, IT’s responsibilities shift from manufacturing or gatekeeping to:

  • Making sure all the platforms connect and communicate and are integrated as needed
  • Minimizing the friction involved in passing data among platforms, apps, and other parts of the chain, particularly as users look to do more process-centric work via mobile devices
  • Making sure the platforms enable users to serve their own needs
  • Providing platforms for special functions, such as collaboration.

Want to learn more? Check out the CITO Research white paper, Putting the IT Store Ecosystem into Action.

If I started talking to people about the credit card “platform” I bet I would get a few strange looks. We take it for granted that we can pay for souvenirs with the same credit card in San Francisco as in Singapore. What makes something a “platform” is its ability to openly interconnect with other systems to accomplish much more than what it could do by itself. For example, the credit card platform ties together merchants, card issuers, banks, payment processors, and consumers into one seamless shopping experience.

credit card.png

In the same vein QlikView is a platform. The best way to imagine it is by describing the opposite: a closed system. Imagine a BI product that limits you to only the data sources for which the vendor distributes connectors. Imagine if the visuals you could create are limited to only the ones that come out of the box. Imagine if the visuals you create are stuck in your BI application and can’t be embedded in another application or web site. That would be a very limiting experience indeed. In today’s heterogeneous business environment, no vendor can possibly anticipate every customer’s data or visualization needs.

QlikView is already a vibrant BI platform with a growing ecosystem of more than 1,400 partners. We recently launched QlikMarket, an online solution exchange where QlikView customers can find QlikTech-vetted connectors, extensions, and apps. Connectors provide pre-built connectivity to business applications such as SAP, Salesforce.com, and PeopleSoft, plus social media sites such as Facebook and Twitter. And that’s not to mention the new visualization extensions and apps that are appearing every day.

With “QlikView.next” (the code name for the next generation of the QlikView Business Discovery platform) we’re taking the platform concept to the next level, under the Premier Platform theme. We are investing in QlikView as the heart of an ecosystem, facilitated by QlikMarket.


The four scenarios we are addressing within the “Premier Platform” theme are:

  • No Data, No Discoveries. The ability to access, transform, and manage data is prerequisite to enabling free data exploration and discovery of insights.  QlikView will provide developers with a modern browser-based development environment where drag-and-drop is the norm. Through a library of scriptlets and expressions, your organization can standardize definitions of KPIs and other important calculations.
  • No More Reporting. QlikView is about action- and activity-based decision making. QlikView will allow users to print exactly what they see and tell the data story via an interactive storyboard paradigm. Those who still need to create static reports for audits and record keeping will be able to export data from QlikView to third-party reporting engines.
  • Simplified Partner Deployments. This scenario is aimed at making it even easier for our OEM (original equipment manufacturer) partners to add QlikView analytic capabilities to their products. QlikView.next will include APIs (application programming interfaces) that permit access to QlikView data and visualizations by a middleware server. QlikTech OEM partners will be able to create sophisticated QlikView extensions, use QlikView to drive an associative experience, and create sophisticated mashups that use some of if not the entire QlikView user interface.
  • Unified Platform Interface. Last but not least, this scenario means that QlikView will be exposing the exact API that the native chart objects use to communicate with the QlikView engine. That means customers and partners will be able to create any visualization they can dream of and integrate them with QlikView to the same degree as native QlikView charts.

QlikView is poised to become a BI developer’s dream platform. Imagine integrating with any data source or destination, creating any visualization, and doing it all within an ultra-modern interface. I’m jazzed to see this dream take shape.

To learn more about “QlikView.next,” the code name for the next generation of the QlikView Business Discovery platform, download the white paper, The “QlikView.next” Product Scenarios.


With rapid success come many challenges. This is true whether in a sporting, professional, or personal endeavor. The Olympic athlete who became  #1  is now the guy everyone wants to beat. A successful executive who has been given greater responsibility needs to learn new skills. How a person faces these challenges will determine whether one stays successful or not.

Over the years QlikView deployments have seen unparalleled success within our customers’ environments. Customers typically start small and Business Discovery proves its value quickly. The result is that our customers quickly adopt more and more QlikView to meet their demanding business analytics needs. With this rapid success can come some challenges, particularly for IT professionals who are tasked with administering a growing QlikView deployment.

Part of QlikTech’s response to these challenges comes in the form of the newly-launched QlikView Governance Dashboard. Released alongside QlikView Expressor 3.8, the QlikView Governance Dashboard is a free QlikView app available on QlikMarket (http://market.qlik.com/qlikview-governance-dashboard.html). The QlikView Governance Dashboard delivers a 360 degree view of any QlikView  environment starting with version 10 SR2. Simply stated, it enables QlikView and IT professionals to discover how QlikView is being used.

Created using QlikView and the recently acquired QlikView Expressor technology, the QlikView Governance Dashboard focuses on helping IT pros understand and manage the QlikView environment. The information learned can help them introduce a more manageable and repeatable process when developing QlikView applications. They can also answer data lineage and impact analysis questions, thereby maximizing data governance and optimizing their QlikView investment.

Some of the capabilities offered by the QlikView Governance Dashboard include:

  • Understanding the source and target data and how it is being used
  • Discovering which applications are the most complex
  • What columns, expressions and sheet objects are used
  • Data lineage
  • Impact analysis
  • QVD (QlikView data file) change analysis
  • QlikView Server and QlikView Publisher statistics

For anyone tasked with administering a QlikView deployment, whether it supports 10 users or 10,000, the QlikView Governance Dashboard can make your job easier and give you greater confidence in understanding all the moving parts associated with your deployment. Download the QlikView Governance Dashboard now from QlikMarket (http://market.qlik.com/).

And to enable metadata-driven QlikView applications, take a look at QlikView Expressor 3.8 Desktop, a free desktop tool used to provision data for QlikView applications in a much more reusable and consistent manner.




Michael Tarallo
Senior Product Marketing Manager
QlikView Expressor


  • To learn more about the QlikView Governance Dashboard please visit: here
  • For a free copy of the newly released QlikView Expressor 3.8 Desktop please visit: here





Figure 1: Gaining insight with QlikView Governance Dashboard

We started to talk publicly about our vision for “QlikView.next,” the code name for the next generation of the QlikView Business Discovery platform, in the spring (see blog post, "The Vision for 'QlikView.next'”). QlikView.next is the code name for an entire new generation of the QlikView Business Discovery platform, spanning multiple releases. It is not the name of the next release of QlikView.

Now that we are further along in our development, we’re ready to pull back the curtain a bit more and share with you the product scenarios we are focused on within each QlikView.next theme. (See the new QlikView white paper, “The ‘QlikView.next’ Product Scenarios.’”) We’ll be posting about the scenarios in each theme here on the Business Discovery Blog, starting today with “Gorgeous and Genius.”

  Gorgeous and Genius product scenarios.png

Within the Gorgeous and Genius theme we are focused on four product scenarios:

  • Associative, Comparative, Predictive. We are making advanced analytics capabilities directly accessible to business users themselves – not just to specialists – in a visually beautiful way in the very moment when they are engaged in decision making. We will provide a base set of analytic options out of the box along with more native intelligence about data types, and will enable partners and customers to add additional capabilities to QlikView using an expanded notion of extensions.
  • Delightful Development. For people who are designing and building QlikView apps, we are focused on simplicity, reusability, and standards-based development and open APIs (application programming interfaces). We want to optimize developers’ productivity by making it easy for them to reuse components and develop solutions that extend, customize, and integrate QlikView with other software on a variety of platforms. We will provide a web-based development environment and a set of well-documented development tools and APIs.
  • One Client to Rule Them All. QlikView.next will consist of a single client that will work equally well on tablets and laptop/ desktop computers, both online and while disconnected. We are focused on new interaction paradigms that work across devices ranging from desktops to touch-based interfaces and the client will adjust automatically to the capabilities of the user’s device. We are using modern web technology (HTML5 and CSS3) and optimizing for the device.
  • Visually Beautiful. We want all interactions people have with QlikView.next to be natural, easy, and comfortable. Our world-class user experience team is focused on creating a Business Discovery environment that is a calm, comfortable, and fun place to work for all types of users. As users become more comfortable with QlikView we will offer them more options and help them along to an even richer experience. QlikView.next will introduce new metaphors for user interaction and new techniques for creating data visualizations.

To learn more about “QlikView.next,” the code name for the next generation of the QlikView Business Discovery platform, download the white paper, The “QlikView.next” Product Scenarios.

I’ve never thought of an IT organization as the storekeeper of technology before. But that’s how it’s portrayed in the CITO Research white paper “From Gatekeeper to Enabler: How the Role of IT Is Fundamentally Changing.” And I like it!

IT Changing from Gatekeeper to Storekeeper.png

In this white paper, QlikTech’s VP of Product Management Donald Farmer and Dan Woods, CTO and editor of CITO Research, put their heads together and share their thinking about how the role of IT is transforming. The gist of it:

  • IT’s role in the past: gatekeeper. In this role, IT was tasked with making sure that enterprise systems were secure, scalable, reliable, cost-effective, efficient, resilient in times of trouble, and compliant with industry and government regulations. Business users went to IT for all their needs – from hardware to software to data to networking – and IT was often put in the position of being the “no” people. “From a traditional end-user’s point of view,” the authors say, “the IT department held a virtual monopoly on corporate technology. Its domain was the back office, and its primary directive was to achieve a high level of operational efficiency.”
  • IT’s role in the future: storekeeper. In the role of storekeeper, IT becomes the “yes” people. IT becomes the proprietor of an IT store. Inside the store, IT manages mission-critical systems and master data. IT selectively exposes portions of these assets to users who need them as a foundation for solving problems. The storekeeper provides as much self-service as possible. And, importantly, instead of trying to manufacture or manage all use of technology throughout the organization, IT monitors activity taking place outside the store, staying on the lookout for new trends and business user-adopted technologies that could add value to the business in a broader way. IT then brings the most valuable of these into the store.

By supporting communities of business users and moving away from the old gatekeeper role, the IT department becomes an enabler of productivity and a more direct partner in the business. What do you think? Does this sound like a good idea? You can read more in the CITO Research white paper, “From Gatekeeper to Enabler: How the Role of IT Is Fundamentally Changing” (registration required). Let me know your thoughts.

Filter Blog

By date:
By tag: