top of page

GAC - Application Management Tool

Grow Admin Console is an application management tool built for bank agents to manage financial products applications customers apply. The main functionality of the product is to surface highlighted information for bank agents to examine and assess when going through the approval process. 

Grow technologies , acquired by ATB Financial, is a Vancouver Fintech startup that focuses on delivering self-serve and omni-channel banking experiences, solutions including retail and business account opening and lending.


ATB Financial


Product designer

Prior to the acquisition, GAC was served to other financial institutions based on specific needs. With new partnership with ATB Financial, we recognize that the tool has to cater to their banking system and processes. We began by exploring and talking with numbers of stakeholders in different areas within the organization to understand their current internal process. 

After we had a better overview on the organizational structure, we wanted to narrow down our focus on our target user - the Client Care team, to understand how our product currently intervenes within their working process. With this clear goal in mind, I began to scope out a research plan by first defining the objectives, hypothesis, potential participants and methods that are applicable for the goal of this study. Working closely with my product manager, we interviewed and shadowed six participants. 


Participant and direct observation at the Client Care department

Multiple tools and screens opened

Collaborating with the team including developers and product managers, we ran a HMW brainstorming session to prioritize the findings and define the appropriate areas to tackle on. We recognized that changing the core banking system would be a huge project that ties into other stakeholders. To keep the scope contained, we decide to focus on improving usability by adapting users’ working process to the workflow and integrate relevant information from other banking tools to extend our product.


Main takeaways:

1   Users spend a long time on navigating to find key information 

2  During examination, ID verification is the major step that slows down decision-making 

Core banking system is slow and rigid, requiring a lot of manual process between tools 

Currently has no way to track team performance and application flow 


Currently, the application page is displayed and organized in a pipeline format in one single page without a clear indication of when an application is ready to be reviewed. GAC users have to constantly scroll through applications that are not relevant and reply on using filters to surface the most updated applications. 


Application page - As a user, I cannot keep track on my own claimed application

Restructure navigation flow

To understand how the current information is being structured, the first task I did was to define the current architecture and rearrange the navigation flow.  

GAC info architecture .png

Redefine application and step logic

To prevent users from constantly spending time on searching open applications to review, a way to solve this is to divide applications in different categories based on step progress to provide a clear threshold of when an application can be reviewed.

Step logic.png

Improve header section and microinteractions

1  Having predefined application type on side navigation

2  Surfacing filters to prevent cognitive overhead

3  Clean up irrelevant feature - bulk download documents

4  Better search capabilities

View full ux documentation

Screen Shot 2020-05-03 at 2.58.53 PM.png
Screen Shot 2020-05-03 at 2.53.42 PM.png
Screen Shot 2020-05-03 at 2.59.17 PM.png


According to FinTrac compliances, it is required for bank agents to use required methods to verify the applicant identity and authenticity of provided documents. Through shadowing our users, we recognized users spent a long time matching personal information between applicant ID, agreements and credit bureau. To narrow down the problem, we began on improving the ID document page.

Screen Shot 2020-03-18 at 3.21.46 PM.png

Currently ID document page is not displaying relevant information from the ID. As a user, I have to preview the image to review ID information.

Redefine storing documents logic and interaction

1  Grouping documents as a set for fraud verification purposes

2  Surfacing ID information from OCR results

3  Better microinteraction for viewing and re-uploading documents

Screen Shot 2020-05-03 at 3.47.50 PM.png

Photo documents in card format | OCR information is displayed along with fraud detection mapping to the verification checklist


Managing documents: Modal interaction

To make sure we have a close relationship with our users, we set up bi-weekly feedback session to make sure we are listening to our users. Not only does this help us to validate our design decision, but also gives us clear guidance in the areas we should focus on as we continue to make improvements.

bottom of page