As the pandemic continues to upend life around the world, data, big and small, takes a central role in mobilizing the right efforts to prevent a much greater calamity. And as people and organizations face unprecedented hardships, business analysts, data scientists, and data analysts are going to be integral to the solution. We have the skills that the world is counting on to arm our leaders with the best possible information as they are tasked with making immediate choices, allocating resources, and anticipating the next obstacles to overcome.

Visual analysis models provide a powerful set of tools that let business analysts depict system information at various levels of abstraction. These models serve as an aid to understanding, as well as an aid to communicating. Alas, I fear that modeling is somewhat of a neglected practice. I believe modeling is an essential skill every BA should master. Here’s why.

Knowing how your users behave and how they rate user experience is important, but it is very hard to learn that without various UX metrics and tools. The quality of user experience is a complex matter; you cannot use one tool to measure the whole experience, as it is built from several smaller components.

Understanding your users’ attitudes and behaviors on your site is key for providing a better user experience. There are many tools and metrics out there and most of them are data-driven. That means that collecting and analyzing data from your site has never been more important than it is today.

In this article, we will take a look at how you can measure user experience on your site, and why is it so important. Also, we will share some of the tools that you can use to measure it, and what you can measure.

First of all, any operating system or solution contains two types of requirements: functional and non-functional. The solution works as a clock, which requires each gear within the solution to be properly functioning. Based on the theory of constraints, any process throughput can only be improved when the constraint or bottleneck is resolved.

Therefore, no matter how fast the train can run and how many passengers it can carry in one trip (the functional requirements), as long as the NFRs are not met, the performance of the solution (subway system) can only be as good as the non-functional requirements.

Second, if NFRs are not considered during the business analysis process, it is very likely they were not part of the criteria for solution evaluation. Without consideration of NFRs, the proposed solution may not be evaluated accurately. What was thought to be the best solution may not be a suitable solution at all.