Debit Card Hub Dashboard

I was the Lead Designer on this project for TD Bank in 2025. I worked with a product owner, a business analyst, and a team of developers.

We simplified a complex system, aligned procedures to other areas of the bank, and improved stakeholder relationships.

Context

TD Bank is one of the top 10 largest banks in North America. In 2024 they were featured heavily in the news for receiving a large fine in the US for failures in their anti-money laundering (AML) program. The news stories led to a decrease in customer’s overall trust in the bank.

The call centre had previously been excluded from funding for research and design efforts but there was now renewed business interest in improving their fragmented systems to reduce customer call times, review and improve existing AML features and strengthen trust in the brand.

This project started as an effort to reduce the number of different apps agents needed to navigate and centralize important customer information when performing high risk actions.

Discover

We conducted user interviews within the call centre.

I observed call centre agents taking customer calls while they shared their screen. This allowed me to quickly learn different work flows in the call centre and gave me a starting point for more precise questions. I later recruited agents for interviews to ask them questions around debit cards in more detail and gain insight into where they felt the biggest pain points were happening.

We referenced similar dashboards in other areas of the bank.

I reached out to other departments that had previously benefitted from research efforts and compared similar actions, such as how debit card information was handled, to see if we could leverage existing patterns.

We met with stakeholders and developers to align on the longer term roadmap.

I asked where the debit card hub design project fit into their overall plans for the contact centre so that I could be sure my design addressed both current user needs as well as needs for the near future.

Define

Discovery surfaced a lot of problems within contact centre but we focused on the ones most relevant to handling debit card actions.

Users were frustrated with the overwhelming existing process.

For agents to complete standard debit card action requests for customers they needed to navigate several different apps and flip back and forth to verify customer information. The friction from this constant switching meant that the system was more likely to freeze or crash, agents sometimes struggled to locate information quickly, and to customers there was no indication for why an agent would be pausing before giving answers to their questions, leading to increased tension.

The existing debit card solutions across the bank, wouldn’t fully work for call centre agents.

Existing patterns for transaction views, debit card actions, and customer information on the public site and retail branches were generally treated as separate pages, not one large app. Research into retail systems had shown that tellers benefitted from debit card actions being executed in steps with only 1 step in the process being shown at a time. Limiting the information on screen helped them focus on completing the current step accurately before proceeding to the next. We didn’t have research to support if this conclusion was true for call centre agents as well.

Stakeholders had never worked with the design team before.

Funding for research and design in the call centre was not common and teams typically operated amongst themselves resulting in each app, feature, and update lacking any consistency. Teams were unsure where design should be brought in during the project timeline and some project teams assumed that the design role would only be providing input on the final visuals of the project. This uncertainty of the role design played in the success of the project would prove to be a problem.

Develop

Ideate

I created an initial wireframe that leveraged existing retail debit card patterns and tucked information in tabs to improve cognitive load for agents. I had intended for the existing debit card patterns to aid in the longer term goal of aligning contact centre with retail, while reducing the overwhelm of information described by agents.

Feedback

I presented this design to stakeholders and developers and got a lot of feedback. Developers had already created the container and microapp structure for the dashboard and the design of one view with tabbed microapps would not work with what they had already built. Stakeholders insisted that information not be hidden in tabs because it would add a click to the process. There was also worry among stakeholders that we were relying too heavily on retail’s patterns when their users were different than contact centre’s users.

Ideate again

I realized at this point we needed to take a step back. I couldn’t fight for reduced cognitive load for users without gaining some trust from stakeholders. First, I met with the lead developer to walk me through in more detail the workings of their existing container and the parent-child relationships of the microapps. Then, I hosted a mini design workshop with stakeholders using unbranded lo-fi sketch component stickers to have them build their own dashboards and discuss the pros and cons to their ideas. Using the lo-fi stickers helped non designers feel more confident building with them while also distancing the components from their hi-fi counterparts used across the bank. Armed with more context and some good will, I was ready to create a new design.

Iterations

The new dashboard design focused on creating clear ‘buckets’ for information and actions while allowing some visual breathing room to reduce cognitive load. I had learned from my developer chat that microapps were capable of tabbed views as long as they only tabbed information from within that specific microapp. This allowed me to keep sections organized while surfacing the most important information by default.

Feedback again

I presented the new dashboard design to stakeholders and developers again. Developers confirmed the new design would function within their technical constraints and stakeholders felt their concerns had been heard and addressed. I wanted to test the new design with contact centre users to be sure it met their needs and not just the teams. User feedback was that the new dashboard was easier to use, easier to locate specific information, and took less or the same amount of clicks to perform actions. Some feedback pointed to a preference for some actions to be grouped under different titles to align with written procedure guides and some fields were updated to address insider risk issues.

Deliver

Our final solution addressed the three problems we had uncovered:

We reduced cognitive load for agents.

The design’s focus on grouping information, tucking edge case details out of sight and introducing a bit of white space made the dashboard easier to skim, and reduced agents clicking through tabs and opening separate apps to search for information.

We aligned the card actions microapp to retail.

After pivoting from aligning the overall dashboard to retail, we focused on matching the card actions themselves to retail. Matching the language and flow of the card actions makes it easier for cross training and allows for better communication between agents, retail tellers, and customers.

We gained stakeholder and developer trust.

Taking a little extra time to step back and make everyone’s concerns feel heard, while still keeping design delivery on time, resulted in a confident approval of final design from both stakeholders and developers and led to design being invited to the table earlier in the project process the next time.

Outcomes

We reduced cognitive load and clicks for debit card actions leading to improved call times, saving the bank time and money.

We aligned process to other areas of the bank.
Allowing for reduced training time, and improved communication between customers, call centre, and retail branches.

We gained stakeholder trust, allowing for more opportunities in the future to improve call centre systems for agents.