This situation Desi described, he said, is very typical. The users, in theory, get exactly what they asked for, but not what they expected. It ends up being a bunch of pretty charts that happen to be on an HTML page, accessible from a mobile device, but not intuitive nor user friendly.
When they engage Desi to do a user experience workshop, a company’s first assumption is they need to re-design their analytics. But Desi focuses on different questions, like “who would use the app?”, “how will they use it?”, “where will they be using it?” and “what will they be using to access it?” He assumes they already identified the analytics that were needed, so focuses instead on ensuring the users have an exceptional experience. He helps identify flaws from their first attempt, but more importantly, he helps define a development roadmap they could easily deploy going forward.
Which brings me to the conclusion of this first installment on user experience. In my next post, we’ll learn from Desi how to go about developing and deploying a great user experience while building your first analytics application, including knowing when you should invest in a web application and when it just doesn’t make sense for your situation.
To learn more on how Qlik Consulting can help you design a great user experience for your Qlik apps, visit qlik.com/consulting.