Product Design Lead with 8 years designing high-trust financial experiences, from first-of-kind fraud flows to card servicing systems used by millions.
I work at the intersection of compliance, behavioral design, and systems thinking, shipping complex fintech products that reduce friction and build customer trust. Currently leading design across 8 agile teams at U.S. Bank and open to senior and lead roles at fintech startups and B2B SaaS companies.
Millions of U.S. Bank credit card customers had no way to upgrade their card without calling a call center. I led the design of the bank’s first fully digital upgrade experience, taking it from zero to a launched product that exceeded conversion expectations and opened the door to three…
U.S. Bank’s card management features were scattered across multiple entry points, and usability testing confirmed what customers had been experiencing: finding what they needed took too long and caused measurable drop-off. I led the design of a centralized servicing hub that consolidated the bank’s most-used card features into a…
A new credit card arrives in the mail, but the customer has no idea when, and no way to know if it was lost or delayed. This gap drove a measurable spike in “where is my card” calls to U.S. Bank’s support centers. I led the end-to-end design of…
Losing a card is stressful. Having to navigate three separate digital flows to report a lost debit card, ATM card, and credit card made it worse. I co-led the design of U.S. Bank’s first unified multi-card reporting experience, bringing all three card types into a single guided journey that…
Before this project, every U.S. Bank credit card fraud claim required a phone call, even at 2am when a customer’s card was just compromised. As design lead on a small cross-functional team, I directed the design of the bank’s first fully digital fraud claims experience, working alongside a product…
I’m a Product Design Lead with over 8 years of experience designing financial products that people actually trust. Most of that time has been spent inside U.S. Bank, working on the kinds of flows that don’t get much glory but matter enormously: fraud claims, card replacements, upgrade journeys, and servicing hubs used by millions of consumer and business customers. I care about getting those details right.
My path to design wasn’t straight. Before this, I worked as an auctioneer, which taught me to read a room, communicate under pressure, and make complex decisions fast. I studied fine art, film, and computer science, none of which I finished, all of which shaped how I think. I approach design the way I approach most things: with curiosity, a lot of iteration, and a genuine interest in the people I’m designing for.
Right now I’m especially drawn to what’s happening at the edges of fintech, including web3, AI, and decentralized infrastructure, where the design problems are hard and the stakes for getting them right are high. I’m looking for senior and lead roles where design has a real seat at the table.
Good product design in regulated environments is less about inspiration and more about rigor: understanding constraints deeply, asking the right questions early, and building trust with the people you’re designing alongside. Here’s how I approach it.
I start with the problem, not the solution. Before sketching anything, I want to understand why this problem exists, who it affects, and what success actually looks like for the business and the customer. I use problem statements and design hypotheses to align teams early, so we’re solving the right thing before we debate the right design.
Constraints are part of the design. I’ve spent years designing inside compliance, legal, and accessibility requirements that don’t move. I’ve learned to treat those constraints as design inputs rather than obstacles, finding the space for great UX within them rather than fighting them. The best work I’ve done has come from understanding a constraint well enough to work creatively inside it.
Research informs direction, not just validation. I partner closely with researchers and use usability testing to challenge assumptions, not just confirm them. Some of my most important design decisions have come from watching a user struggle with something I was confident about. I build in time to be wrong.
Design is a team sport. I work best when I’m deeply embedded with product, engineering, content strategy, and compliance. I’ve learned that the earlier you bring engineering into design decisions, the fewer surprises you get in build. I write clear JIRA stories, give detailed redlines, and stay close through QA to make sure what ships matches what was designed.
I think in systems, not screens. A single screen is a decision. A product is a system of decisions made consistently over time. I try to design with the system in mind: how does this pattern scale, how does it work across platforms, how does it connect to what already exists. That’s especially true when contributing to a design system, where a single component decision affects hundreds of surfaces.
If any of this sounds like the kind of designer your team needs, I’d love to talk.