Valley Bank

Stakeholder Interviews

I partnered with UX Researchers and Product Managers to collect and synthesize analytical data and customer feedback that later informed design decisions.

Platform Analysis

As an out-of-the-box solution, the platform required a deep understanding of its component library.

Listening

Post-launch listening programs through exit-intent surveys and diary studies with the customer care team generate actionable feedback to iterate designs on an ongoing basis.

User Stories

To understand user tasks, I generated user stories through a series of workshops for all three account openings — two for retail and one for small businesses. The product, QA, and engineering teams used the user stories to define requirements and testing scripts.

I held bi-weekly UX workshops with product managers to define requirements and gather feedback on design concepts. These workshops involved some whiteboard and rapid prototyping.

An agency initially started the visual design process, which I took over and established a design system and improved the look and feel. I designed Over 70 new screens (including mobile designs) with a cleaner interface and created prototypes for user testing.

I partnered with UX Researchers to test page flows for clarity, intuitiveness, and understanding of tasks. Testing mainly was successful, with some feedback suggesting clarity around language or labeling of instructions, buttons, and other UI components. I iterated on the designs based on user feedback.

Valley AO - Add Beneficiaries

Objective: Gauge how well users understand the process of adding beneficiaries to CDs. ‍

Method: Unmoderated‍

Summary: Users find adding beneficiaries an intuitive and straightforward process with little friction, but it was not immediately apparent that the system added their beneficiaries to the CD. They prefer to actively save their designations or receive a confirmation that their input was successful.

• ‍"Clicking the drop down and adding the beneficiaries couldn't be any easier. It was seamless; it was quick; and it was really well organized."
• "I do wish there was a save screen for the first beneficiary... something like a 'save' and 'add new.'"
• "I'm looking for a save button. I'd rather have a save button than a continue button."
  

Design Strategy

• Shorten the "Add beneficiaries" text below the headline to aid cognition.
• Prevent errors by adding an "Add a beneficiary" CTA after the user opens the accordion.
• Change the primary CTA label from "Add beneficiary" to "Add a beneficiary" to reinforce the singular action.
• Change the secondary CTA label from "Add beneficiary" to "Add another beneficiary" to clarify the act of saving versus adding a new beneficiary.

‍

Valley AO - Funding Debit Limit

Objective: Gauge how well users can identify and understand why they cannot fund their accounts with a debit card once the user exceeds the $500 debit limit.  ‍

Method: Unmoderated‍

Summary: There's a high probability that users will reach the debit card limit, which prevents them from moving forward. Our mission was to determine how to best handle error reporting.

• ‍"I like being able to click on these different funding options and see why I cannot move forward."
• "Option 2 would be the better choice. The color really makes it so that I notice the debt limit." 
• "I actually like Option 2 better because someone could easily overlook the explanation of the debit limit." 
  

Design Strategy

• Tell customers about the $500 debit card limit upfront (under the subheading).
• Alert customers when they exceed the $500 debit limit.
• Tell users what to do when they exceed the debit limit in the error message.

‍

• Valley Direct received $1.2 million in deposits post-launch.
• Valley Direct account opening received a 150% increase in new customers to Valley, realizing a 20% conversion rate goal.
• Valley.com retail account opening conversion rate increased from 2% to 11%, with an average deposit of $5,845.
• Valley Direct/Valley.com retail online account opening process reduced from 12 to four steps.
• Small business account opening successfully launched.

Lessons Learned

• Despite initial opposition, creating user stories was highly valuable for the broader team to collaborate, practice user-centered design, and define functionality.
• Documentation is essential for ensuring all players are communicating.
• Quality control is complicated with outsourced dev and QA resources.
• Users don’t typically read content — especially during testing. Therefore, it’s essential to keep UX writing as concise as possible.
• User testing only captures happy paths, not all scenarios that generate friction.