As part of my work as User Experience Researcher, people tell me about their journeys of learning QlikView. This includes developers creating their first applications for other people, administrators setting up large scale environments and users of business discovery applications. These journeys describe both what people struggle with and what they find easy when using QlikView. Each journey is unique and extremely valuable for us in understanding how people use QlikView and how we can support their working process in the best way possible.
A particularly interesting trend I’ve seen is that people working within business, e.g., controllers, accountants and sales managers, can also have roles as QlikView developers at their organizations. Compared to the “conventional” developer who has specific IT or software developer skills, people with a background in business face quite different challenges when learning QlikView. For example, they are often not familiar with scripting or visualization techniques and worry a lot about best practices when designing apps. On the other hand, this specific kind of developers has an in-depth understanding of their business and the needs of their company and colleagues. They might struggle with implementing technical solutions but the applications they create are often immediately valuable to the business.
By understanding our different types of users we can create solutions that help people quickly learn and effectively use QlikView regardless of how they approach it. People’s journeys with QlikView are the basis for one of our most valuable design tools for QlikView.next: personas. A persona is a fictional character that represents core characteristics of real users based on research. Our personas at QlikTech describe behaviors and attitudes that we gather from engagements with large number of existing as well as potential users. When creating these personas, we do not only ask what people want but also observe and interview them to understand how we can support their needs efficiently and effectively.
Our personas give our different kinds of users names, faces and feelings rather than merely being a “type” or a categorization. They provide presence and influence from our users at all stages of the design and development process. The personas cover novice, intermediate and expert users and our aim is to provide solutions that can support them all when learning and working with QlikView.next.
Do you have your own journey to share or seen any similar trends when working with QlikView? Let us know in the comments below!