Storefront for Staff
Improving an internal tool for Staff members to assist customers
Introduction
Boeing Employee Credit Union (BECU) is a member focused financial institution that operates primarily in the Washington State area. The project is called Storefront for Staff, an internal tool for staff members to search applicants, create new applications, and screen them.
Company
BECU
Teammates
UX Designer, Software Developers, Stakeholders
My role
UI Designer
Objectives
Due to BECU wanting to sunset a 3rd party tool, me and a UX designer were brought in to help design an internal tool designed to help staff members search applicants, create new applications, and screen them more effectively.
Process
I was a Product Designer working with a UX Designer (Liz) in a more UI capacity, gathering requirements, conducting research, and iterating through the designs, involving stakeholders and developers in a very short sprint.
Challenges
The sprint was quite short.
Monday: Stakeholder meeting to define requirements
Tuesday: Develop mockups and wireframes
Wednesday: Design review with devs
Thursday: User test designs
Friday: Compile User test findings
Then the following Monday would tell the stakeholder any findings and adjustments to be made to the previous design while moving forward with the requirements for new features. Thus our iterations had to be fast and accurate to keep up with requirements.
Search Results
One particular feature I refined was the search results. The stakeholders wanted to see all possible search results that a user could work on, so they could choose which one to proceed with.
Testing
During testing, we found that users were still confused about which result to proceed with. They expected to see some recommendation, screening results, and dates to inform them of the best decision to make. There were a couple of comments on wanting to know if the result was a primary account holder or joint on the account.
Iteration on search results
Based on those findings, I decided to have a visual way to show a recommended search result based on the screening result and date programmatically pushing a result to the top, along with a bar at the top indicating our recommendation. A small icon next to the name indicated if the person was a primary or joint was also added.
The following week, the testing went much better. Users understood what the colours meant, could see the screening result and date to make an informed decision on the application to move forward with. Final designs were put into Zeplin.
Outcomes
I left before the project could be completed, but testing showed that users were very pleased with the new system and that it would “save [them] a lot of clicks”
Check out some of my other projects
Storefront for Staff
Improving an internal tool for Staff members to assist customers
Introduction
Boeing Employee Credit Union (BECU) is a member focused financial institution that operates primarily in the Washington State area. The project is called Storefront for Staff, an internal tool for staff members to search applicants, create new applications, and screen them.
Company
BECU
Teammates
UX Designer, Software Developers, Stakeholders
My role
UI Designer
Objectives
Due to BECU wanting to sunset a 3rd party tool, me and a UX designer were brought in to help design an internal tool designed to help staff members search applicants, create new applications, and screen them more effectively.
Process
I was a Product Designer working with a UX Designer (Liz) in a more UI capacity, gathering requirements, conducting research, and iterating through the designs, involving stakeholders and developers in a very short sprint.
Challenges
The sprint was quite short.
Monday: Stakeholder meeting to define requirements
Tuesday: Develop mockups and wireframes
Wednesday: Design review with devs
Thursday: User test designs
Friday: Compile User test findings
Then the following Monday would tell the stakeholder any findings and adjustments to be made to the previous design while moving forward with the requirements for new features. Thus our iterations had to be fast and accurate to keep up with requirements.
Search Results
One particular feature I refined was the search results. The stakeholders wanted to see all possible search results that a user could work on, so they could choose which one to proceed with.
Testing
During testing, we found that users were still confused about which result to proceed with. They expected to see some recommendation, screening results, and dates to inform them of the best decision to make. There were a couple of comments on wanting to know if the result was a primary account holder or joint on the account.
Iteration on search results
Based on those findings, I decided to have a visual way to show a recommended search result based on the screening result and date programmatically pushing a result to the top, along with a bar at the top indicating our recommendation. A small icon next to the name indicated if the person was a primary or joint was also added.
The following week, the testing went much better. Users understood what the colours meant, could see the screening result and date to make an informed decision on the application to move forward with. Final designs were put into Zeplin.
Outcomes
I left before the project could be completed, but testing showed that users were very pleased with the new system and that it would “save [them] a lot of clicks”
Check out some of my other projects
Storefront for Staff
Improving an internal tool for Staff members to assist customers
Introduction
Boeing Employee Credit Union (BECU) is a member focused financial institution that operates primarily in the Washington State area. The project is called Storefront for Staff, an internal tool for staff members to search applicants, create new applications, and screen them.
Company
BECU
Teammates
UX Designer, Software Developers, Stakeholders
My role
UI Designer
Objectives
Due to BECU wanting to sunset a 3rd party tool, me and a UX designer were brought in to help design an internal tool designed to help staff members search applicants, create new applications, and screen them more effectively.
Process
I was a Product Designer working with a UX Designer (Liz) in a more UI capacity, gathering requirements, conducting research, and iterating through the designs, involving stakeholders and developers in a very short sprint.
Challenges
The sprint was quite short.
Monday: Stakeholder meeting to define requirements
Tuesday: Develop mockups and wireframes
Wednesday: Design review with devs
Thursday: User test designs
Friday: Compile User test findings
Then the following Monday would tell the stakeholder any findings and adjustments to be made to the previous design while moving forward with the requirements for new features. Thus our iterations had to be fast and accurate to keep up with requirements.
Search Results
One particular feature I refined was the search results. The stakeholders wanted to see all possible search results that a user could work on, so they could choose which one to proceed with.
Testing
During testing, we found that users were still confused about which result to proceed with. They expected to see some recommendation, screening results, and dates to inform them of the best decision to make. There were a couple of comments on wanting to know if the result was a primary account holder or joint on the account.
Iteration on search results
Based on those findings, I decided to have a visual way to show a recommended search result based on the screening result and date programmatically pushing a result to the top, along with a bar at the top indicating our recommendation. A small icon next to the name indicated if the person was a primary or joint was also added.
The following week, the testing went much better. Users understood what the colours meant, could see the screening result and date to make an informed decision on the application to move forward with. Final designs were put into Zeplin.
Outcomes
I left before the project could be completed, but testing showed that users were very pleased with the new system and that it would “save [them] a lot of clicks”