Modernizing Valley's account opening to grow deposits beyond the branch footprint

Valley's legacy account opening platform was aging, inflexible, and unable to support the business's growth ambitions. To digitally acquire consumer deposits outside its branch footprint, Valley launched Valley Direct — a digital-only sub-brand — while simultaneously replacing the legacy platform with a modern, scalable solution designed to later expand across branch, commercial, and specialty banking.

Role UX Lead

Role Jr. UX Designer

Partners  Product · Engineering · Marketing · Compliance · Retail Operations

Deliverables User Stories · Design System · High-fidelity Prototypes

Tools Figma · Sketch · Miro · Maze · User Testing

The Problem

Valley's retail account opening relied on a legacy platform that couldn't scale and a customer experience that wasn't converting. Valley Direct and Valley's core banking products on its website were the first two streams selected to test the new platform and validate the market.

I executed the design end-to-end — partnering closely with product and engineering, pulling in direct reports at key moments, and using that collaboration as an opportunity to develop their skills.

Learn more about how we solved account opening friction for existing customers >


A screenshot of the old experience.
"How might we design a digital account opening experience that earns customer trust, meets compliance requirements, and scales across Valley's growing lines of business?"
Pain Points

No self-service

Customers couldn't add beneficiaries, joint applicants, or debit cards online. Adding beneficiaries required a notarized letter, joint applicants and debit cards required a branch visit.

Funding drop-off

The legacy platform used microdeposits to fund accounts, requiring customers to return and verify their deposit before it was accepted. Most never returned.

Lengthy application process

Opening an account took up to 3 days — a form-heavy, multi-step process that pushed customers to abandon before completing.

Opportunities

Grow application volume and deposits

Optimize the funnel to increase application starts, cut time to open, and eliminate moments where customers exit without completing.

Improve end-to-end conversion

Redesign the application flow to reduce steps, shorten completion time, and remove the friction driving abandonment.

Scale online account opening

Give customers the ability to open any core product online and fully onboard all branches to use the new digital platform.

Step One

Establishing Ways of Working

The first challenge wasn't design — it was ambiguity. Requirements were unclear, and stakeholder alignment was inconsistent. How did I solve this challenge?

Workshops

I facilitated (or jointly-facilitated) workshops to engage business stakeholders, understand business challenges, and establish shared success criteria before any design work began.

Requirements-gathering sessions gave the team a shared understanding of what the experience needed to do — and why.



Design Thinking

I coached the cross-functional team on maintaining a human-centered approach and on using data and user insights to inform our decisions through research and usability testing.

Journey Mapping

Mapped various user journeys to uncover pain pain and how back-office processes contributed to the customer experience.

No items found.
Step Two

Building the Design System

Valley's account opening lacked a shared design language and was disjointed from the parent brand's identity. Engineering output reflected that gap — inconsistencies, bugs, and unintuitive UI components were common, compounded by the limitations of the vendor's component library.

With all digital touchpoints along the customer journey in mind, I built a primary design system (pre-Figma) — components, interaction patterns, and content standards — grounded in Valley's brand guidelines and adapted for the vendor platform.



Mentorship

I created a design system roadmap and mentored my junior direct reports through the roll-out, using the work to develop their skills in component thinking, design documentation, and working within technical constraints. As the system matured, they took on increasing ownership of component maintenance.

Engineering Partnership

I built an ongoing working relationship with the vendor’s engineering team — sharing specifications in a format their engineers could act on and collaborating to find solutions that preserved design intent within platform limitations. The partnership reduced bugs, increased time-to-market, and enabled a more accurate, efficient build process.

No items found.
Step Three

Funding

Funding on the legacy platform was completed via microdeposits — a process in which small test amounts are deposited into a customer's external bank account, which they must return to verify before funding is confirmed. Requiring a return visit caused a significant drop-off, as most customers did not complete the process.

To remove the return-visit requirement, we switched to real-time bank verification with Plaid. This created a new issue: users didn’t trust Plaid and hesitated to link external accounts.

I partnered with UX Research to understand user concerns. Testing confirmed the trust gap. Users needed explicit reassurance that their information was secure and the service was legitimate before they would proceed.

Design Response
  • Reduce cognitive load: Added numbered steps within the funding process.
  • Improved error recovery: Made error messages actionable with clear next steps.
  • Build trust at the linking step: Added tooltips, Valley branding within the Plaid interface, and  security messaging at the point of account linking.
No items found.
Step Four

Adding Beneficiaries

To reduce reliance on branches, decrease customer care call volume, and eliminate manual data entry, I designed a self-service beneficiary flow.

Previously, customers were required to mail a notarized letter to add beneficiaries — a significant barrier for anyone without easy access to a branch.

Testing showed users could navigate the process intuitively; however, a confirmation feedback gap created doubt at a trust-sensitive moment—users weren't sure their designations were saved.

"I'm looking for a save button. I'd rather have a save button than a continue button."
Design Response
  • Reduce cognitive load: Shortened instructions under the headline.
  • Prevent errors: Placed an explicit 'Add a beneficiary' CTA after the accordion opens.
  • Clarify actions: Renamed CTAs to distinguish between saving and adding beneficiaries.
No items found.
Step Five

Debit Card Limits

During testing, we saw users who chose to fund their accounts with a debit card frequently hit the $500 limit and were blocked from proceeding, with no clear explanation. As a result, they abandoned the account-opening experience altogether.

I partnered with UX research to validate two error treatments — a passive inline message versus a high-visibility alert — and the user response was decisive.

"Option B would be the better choice. The color really makes it so that I notice the debit limit."
Design Response
  • Set expectations upfront: Added a $500 debit card limit disclosure under the funding subheading, before users selected their method — removing the element of surprise.
  • Alert at the threshold: Triggered a clear alert when users exceeded the limit, rather than silently disabling the “Continue” button.
  • Tell users what to do next: Rewrote the error message to include a recovery path, not just an explanation of the issue.
No items found.

Impact

In the end, my team and I delivered a scalable design system during Valley's corporate rebrand and a simultaneous migration to Figma. Our engineering partners received a single source of truth that reduced bugs, eliminated design inconsistencies, and sped up handoffs to engineering.

The result was a faster, more consistent build process and a customer experience that reflected it: application completion time dropped from three days to minutes, online account openings quadrupled, and customers could finally fund their account, add beneficiaries, and get a debit card without ever visiting a branch.

This multi-year initiative established Valley’s digital account-opening capabilities across multiple lines of business, including retirement, specialty banking, business, trusts, and estates — laying the foundation for future expansion into credit cards, mortgages, and additional offerings.

Outcomes

$88.2 K

Estimated annual cost savings from reduced reliance on customer care calls.

10%

Valley’s conversion rate using Plaid, a percentage above the vendor’s industry benchmark, following trust-focused content and design updates.

20 mins

50% reduction in application completion time and from 12 steps to 4, cutting time to open from days to minutes.

Growth in online account openings. From 5% to 20% total retail accounts with an average of $5,845 deposits. 25% Valley Direct conversion rate.

Learnings & Reflections

Vendor relationships are a design tool

Treating the platform vendor as a partner (not a constraint) produced higher-fidelity builds and faster resolution of spec gaps.

Design systems build team capability

Building the system alongside the engineers created shared ownership that sped up speed to market.

Structure unlocks speed

Workshops and requirements sessions upfront reduced rework and kept the team moving with clarity rather than chasing alignment.