Case Studies >
Card Sort Study

Saved 6.2 Million Dollars

For a Top US Bank


Impact

Reduced Call Time
2 Minute Reduction
Learn How
5 Unique Groups Discovered
R and Optimal Workshop
See Research
Actionable Insights
UI Overhaul
View Results
Reduce call-handling by 2 minutes per agent. This change saved $6.2 million in costs for the quarter. Improved efficiency and usability for customer service agents via a natural categorization structure. These insights created the new IA.This change made the customer service team more efficient.


Overview and Abstract

  • Context: Customer service agents use Fare Rules, a feature within a larger banking application, to determine travel costs.
  • Problem: The text interface made it tough to find information. It slowed down agents and led to more human errors since agents had to type commands manually. This cost the bank millions in operational costs annually.
  • Role: As the Principal UX Researcher, I chose methods, gathered data, and analyzed it. I worked with product managers, help desk agents, and the design team.
Client PresentationResearch Plan


Project Runway
‍‍


User Persona: Anonymized Bank Customer Service Agent


We established the following persona through three studies, consisting of user interviews with junior and senior customer service agents.

Key Insight

"It normally takes me 15 minutes to navigate from one application to another. It also typically takes me thirty minutes to one hour to look up an entry in the fare rules. During that time, I am on the phone with our customers."
- Senior Escalation Desk Customer Service Agent


Goals

  • Resolve customer issues quickly without escalation
  • Minimize time spent navigating between applications


Agent Behaviors Insights

  • Relies on memorized workflows and shortcuts to avoid UI inadequacies.
  • Develops personal “workarounds” for inefficient systems, such as for the inability to search.
  • Prioritizes speed
An image of a generic customer service agent at their computer with two monitors looking at a generic customer service management tool (not this tool)


Pain Points


Agent Needs


Methods and Process

A flowchart of my research process starting two months before the study and a day by day breakdown during the study
My research process flowchart shows what I did two months before the study. It also includes a day-by-day breakdown during the study.
  • Method:
  • I talked to stakeholders to decide which cards participants would sort. Fare Rules is a complex feature. I also confirmed a research plan before starting the research.
  • The customer service manager scheduled agents with me. I used Optimal Workshop to gather data.
  • I clustered to see how participants grouped cards. This helped identify pages and sections for the new UI.
  • Schedule:
  • This was Tallwave and the client's first card sort, so I provided two months for education which occurred during group and 1-on-1 client meetings.
  • Other methods, like usability tests, can be done faster.
  • This approach ensured thorough data collection and analysis. I finished data gathering and presentation creation in 10 days.
  • I shared the findings with the client and the UX design team. We discussed them over the following months.

Optimal Workshop analysis cut 51 fragmented categories down to 21, defining four major groups. This suggested the new design should have four pages or sections.


Further Analysis in R

After looking at the Optimal Workshop findings, I saw I needed a deeper R analysis.  This analysis took place after the report was released because:
I wrote a program in R to analyze the data.

I anonymized the data here to protect my client and the users.

This diagram helps to decide how to group the cards:
The dendrogram for the card sort (with R visualizations)
I used the heatmap to determine the degree of agreement between users on whether or not a data field should be on a page:
A heatmap of the amount of participant agreement about two cards in the Fare Rules Card Sort

The blue text image shows part of the program that created the dendrogram and heat map.
This shows a loop that I used to create a similarity matrix .


Outcomes

The heatmap and dendrogram provided insights not visible in the Optimal Workshop analysis:
The analysis showed that there could be either four or five groups. The final decision was to use five groups, which was arrived at after speaking to stakeholders (UX designers and the Senior Product Manager).
We split ticket types from routing info. This fixed the confusion that slowed down searches.
We placed fare calculators with pricing rules where agents expected to see them. This cuts down on wasted search time.
We organized commands by how often people use them. The most important tools are right at the front.
In conclusion, we created categories matching how agents think about fare information, making the process more intuitive.


Other Case Studies