Why This Wasn't Just a Backend Merge

This wasn't just two systems being combined. Bank of the West's own digital banking experience had been independently benchmarked as a laggard well before the acquisition, particularly on mobile, where it ranked near the bottom of the market on things like account alerts and money movement. BMO's experience wasn't flawless, but it was meaningfully stronger. For a lot of these customers, this migration was also their first real upgrade in what their bank could do for them day to day, so it needed to feel like progress, not disruption.

The Trade-off: Keeping Bank of the West's Brand Alive

The business's first instinct was a clean break: move everyone into full BMO branding from day one. I argued against that. Nobody chose to switch banks, and stripping away every familiar visual anchor at the same moment everything else about their banking relationship was changing would have compounded an already disorienting experience. I pushed to retain Bank of the West's brand colors and logo through the transition period itself, so customers had one less thing to second-guess while they relearned everything else. The case wasn't about aesthetics, it was about reducing how many unfamiliar things happened to someone at once, and it held.

Scoping Tight, Then Building Phase Two

I scoped the migration itself tightly, around what a safe conversion actually required: one decision per screen, nothing bundled, to keep cognitive load low. Anything short of essential got deferred rather than jammed in, which created room for a second phase: Digital Banking Essentials, a feature to help newly converted customers actually use what they now had, funding their account, setting up alerts, connecting Zelle, setting up bill pay, instead of leaving it undiscovered.

For that feature, I pushed for something that added real engineering cost: rather than a standard static checklist, one that dynamically detects what a customer has already done and checks it off automatically, no manual input required, with a small trophy moment on full completion. It meant more development work than a simple list, and I had to advocate for it. But a checklist that stayed technically "incomplete" while nagging someone about things they'd already done would have undercut the entire point of the feature.

Validating the Approach

There wasn't much direct precedent for a migration at this scale, so I leaned on industry benchmarking instead of running a from-scratch competitive audit. I also ran usability testing on the core First-Time-Login flow, which backed up the approach: most participants found the multi-step process reasonable for something this important, though a few wanted more context upfront on why it mattered. That feedback shaped how I wrote the flow's early messaging.

1.8 million customers moved onto a stronger banking experience, with a lot less friction than a migration like this usually causes.