top of page

MyRQ Reporting Parameters

A small, yet time gaining adjustment to the way users select their reporting parameters and simplifying repetitive tasks

ROLE 

UX / UI Designer

COMPANY

IQmetrix

TYPE

Responsive mobile first B2B SaaS

SHIPPED

Dec 2022 (2 week project)

RESPONSIBILITIES

  • User research

  • Analytics

  • Visual Design

  • Prototyping

  • Usability testing

TOOLS

Azure

DevOps

zoom-logo.png

Zoom

fullstory.png

FullStory

Figma-logo.png

Figma

maze logo.png

Maze App

myRQ.png
Project Brief

Telecom retail managers utilize myRQ to get real time data on store performance metrics, set up notifications and generate manager override codes. When they need to obtain a report for store performance, they must select certain parameters before producing a result. This user journey rework enabled the retail manager to do this in a more streamlined, time saving manner. 

​

The Problem

1. When an employee wants to see a report, they must first select a date range as the primary parameter. However, the current flow is too complex for what should be, a simple task. 

2. After an employee has completed a report, typically they will leave the reporting feature. When they return to create another report, the date they had recently used should be the default, instead it defaults to todays date.

The Solution

Provide the user the quickest and clearest way to choose the parameters of their report and to ensure the user lands on the last selected report date.

The Original Flow
My Process

  1. Understand the problem - Interviews

  2. Understand the persona

  3. Quantitative research - analytics

  4. Creating the User Journey

  5. Iteration 1

  6. Usability testing

  7. Delivery

Understanding the problem - Interviews

Internal Zoom Interview: 

Client Experience (CX)

Attendees:

Myself and three internal CX staff

Why:

I wanted to understand what the clients were saying about this problem from the CX point of view as they had several complaints from different clients about this process.

Findings:

  • The client feels this process is "incredibly frustrating".

  • They rarely use the custom date range picker (but still need it)

  • "Yesterday", "Today" and "This Month" are the more popular choices

  • The "'Today' default isn't helpful, please make it the last visited parameters" 

External Zoom & share Figma screen interview: 

Retail clients 

Attendees:

Myself and at least one MyRQ end-user from three different telecom retailers 

Why:

I wanted to go over my hypothesis with the clients and review the current flow; what they did and did not like, what worked well, what didn't. 

Findings:

  • The client feels this process is "incredibly frustrating".

  • They rarely use the custom date range picker

  • "Yesterday", "Today" and "This Month" are the more popular choices

  • They do not need fully custom dates EG:: 1st to 18th of the month. 

Screen Shot 2022-12-29 at 2.01.38 PM.png
Understanding the Persona

The Regional Manager persona is one I had personally done research for in previous months. Several interviews and a survey with 20+ relative respondents had been completed to gather this data. This personas' job is to ensure the stores within their designated region are hitting targets, and the inventory is managed as efficiently as possible. 

Understanding this persona helped me know the other tasks they have on a day to day basis. It allows me to potentially find similar parameter patterns they are used to, so that I can consider it for the flow I choose to keep consistency. 

Regional Manager - Instore.png
Quantitative Research - Analytics

To better understand the order in which we present the date range options to the user, I wanted to know what search criteria was the most popular, that way I can make the most popular options the easiest to access. 

MyRQ has its analytics captured by Full Story and I was able to track the amount of times each button is currently clicked. This is the report it returned: 

Analytics.png

Findings

"thisMonth" & "MTD", "today" & "Today", "yesterday" and "Yesterday" etc. are the same thing respectively, this was a code bug. So based on the combination of these clicks, the order of popularity is now is MTD, Today, Yesterday, Custom Day, Custom Month, Custom Week, This Week, Last Week. 

User Story

I took into consideration the old user story flow so to not create extra work in creating all new code. The persona was also used to a similar flow in another task they do on a day to day basis (not in MyRQ), so I utilized the familiarity and common design patterns from that software. 

Iteration 1

  • Began with original flow

  • Added the 3 most popular buttons in an easy to select way, (just one tap). 

  • Decided to utilize a "radio button" type component based on the fact that only one selection can be chosen at a time. 

  • Added the custom button to same radio button group (at the end).

  • Added dynamic text below button selection that displays the currently selected date range.

  • Created date range modal with three choices at the top "Day, Week, Month".

  • Followed familiar patterns to selected day/month/year choices (arrows, highlighted selections, clearly disabled dates (future dates), save button). 

Usability Test

Because it is difficult to track heat maps with mobile testing, I utilized the Maze Test App together with Zoom and met with 5 people separately (2 internal, 3 external) and had them each complete tasks while I watched them click through, taking note of any hesitation in what to do next. They then answered a qualitative question about how they felt about the flow. 

testpathMyRQ.png
testresultsMyRQ.png

Findings

Watching the participants go through the flow, there was some hesitation in the Custom Date Modal, it was explained why in the qualitative"responses. All flows were still accepted as positive experiences. This affirms 1st iteration has no need for any adjustments at this time. 

Handoff

For handoff, I created a presentation for an all-hands (PM, PO, Dev Lead, and all Developers assigned to this project) meeting in order to get a solid checkpoint on where we are all at, and to understand what to expect.   

Deliverables

  • Presentation

  • Annotated Figma file - Desktop, Tablet & Mobile size Hi-Fi mockups

  • Prototype link​

MyRQ Handoff Presentation
Pains

  • This was a rush project as the flow was causing a lot of frustration for many users. It took my time away from other important projects 

Gains

  • While this was a seemingly simple and straight forward fix, it was important for me to go through my typical full design process to ensure the user was getting the best possible 

  • Written feedback from users came back positive instantly. Some responses were "it saves a surprising amount of time", "I'm less annoyed to use it now!", and "thanks so much".  

  • The estimated time saved to complete the happy path was roughly 4 seconds

bottom of page