🔒 Case Study

Enter access code
to view this project

Incorrect — try again.

✈️

"You found it. This is exactly why I love design — details change everything. Let's work together."

You've got the eye for it.

Open Communication Channel ✈️
Welcome aboard, co-pilot ✈️
Selected Work 5 Case Studies
01 Fintech · Mobile Banking

CashFlow Central

Designed end-to-end landing, enrollment, and onboarding for Fiserv’s SMB cash management suite.

Fintech Banking Enrollment UX Small Business
View Case Study
CashFlow Central intro screen CashFlow Central benefits screen
02 Fintech · Mobile & Web Banking

Debit Card Perks

Led the 0→1 design of a debit card perks program, driving activation and daily engagement across 1M+ users.

Fintech Banking UX/UI Design Systems
View Case Study
Velo Perks marketing page on iMac
03 iOS App · UX/UI

Tarot Realm

Gesture-first tarot with dual visual themes and a collectibles system built to make every pull a ritual.

Mobile Consumer UX Research Interaction Design
View Case Study
Tarot Realm welcome screen Tarot Realm card spread selection
04 UX Research · Usability

NRA User Research

End-to-end user research study uncovering critical usability gaps and reshaping the product roadmap through moderated sessions.

Research Usability Testing Personas Journey Mapping
View Case Study
NRA user research artifacts: survey results, interview notes, and key insights
05 UX/UI · Video · Research

Quext.Me

Designed and launched a social discovery platform combining research, interaction design, and promotional video production.

UX/UI Video Research Prototyping
View Case Study

Design with intention.
Built for people.

Currently leading design initiatives at East West Bank (Velo Digital), crafting seamless experiences across native mobile, online banking, and web platforms.

I focus on creating minimal, elegant interactions powered by emerging technologies — with a portfolio spanning fintech, AI, and aviation UX. Beyond design, I'm a pilot in training, driven by curiosity and fresh perspective.

Tanny Liang
Based in
San Francisco Bay Area
Speciality
Product Design · Fintech · AI Native Design · B2C · B2B
Experience
7+ years
Currently
Velo Digital · East West Bank

Get in touch

Let's build something remarkable.

Whether it's a product, a system, or something no one's designed before — I'm ready to collaborate.

Say Hello
Open in Figma ↗

✦ UX / UI Case Study

Tarot Realm

An Anime-Inspired Tarot App for Every Kind of Reader

Role
Product Designer — Solo
Platform
iOS Mobile App
Timeline
10 Weeks
Tools
Figma · Claude · Replit · Midjourney

Project Overview

A mobile tarot app for every kind of reader — built around a fully committed anime art direction that merges immersive visual storytelling, structured reading flows, and a collectibles system that rewards daily practice.

"How might we design a tarot app — for all experience levels — that feels like entering another world, while building a sustainable daily reading habit?"

The Problem

Crowded market. Zero differentiation.

Most tarot apps are flat reference tools — pull a card, read a text block, close the app. No atmosphere, no habit loop, no reason to return. Visual design skews toward cold minimalism or dated clip-art, failing the digitally-native audience increasingly drawn to tarot.

No habit mechanics — no streaks, reminders, or progress rewards

Transactional sessions with no reflection or journaling layer

Card meanings as walls of text — no hierarchy or depth toggle

Cold, generic apps — no sense of world, character, or atmosphere

01 — Discovery & Research

Audit + qualitative interviews.

Competitive Analysis

Six apps assessed. No competitor had invested in retention design — streaks, reminders, and rewards were absent or afterthoughts. Visual quality was consistently low.

User Interviews

Beginners feared 'getting it wrong' — wanted guidance, not condescension

Casual readers wanted a habit but found no app made it easy or motivating

All groups responded to character-based apps — a guide or companion resonated

Key Insight

Users don't just want to pull a card — they want a ritual companion. The app's character and world need to feel as considered as the tarot content itself.

02 — User Flows

Four core journeys.

Home & Discovery

Daily draw CTA, Zodiac This Month, and Fantasy Quest — a gamified narrative layer rewarding consistent use.

Reading Flow

Intention → spread → focus → 78-card arc draw → layered card reveal. Each step builds atmosphere and anticipation.

Card Detail

Keyword tags, layered meanings (positive / negative / reversed), consistent framing across all 78 cards.

Collectibles

Unlockable card collection rewarding daily draws and reading streaks — the habit loop's reward layer.

03 — Visual Design & UI

A fully committed anime world.

A single recurring oracle character guides every reading. Warm tan/cream for home & discovery; deep navy for reading screens — a deliberate palette shift that signals entry into the ritual space.

Home screen

Home screen

Reading entry

Reading entry

Spread selection

Spread selection

Focus selection

Focus selection

Coffee Support — Monetisation Feature

A "Buy Me a Coffee" integration surfaced through the app's sidebar — letting users support development with bonus in-app credits. Designed across three states: intro modal (with Lottie animation), amount selection, and validation errors.

Coffee Support feature — sidebar, modal, amount entry, and error states

04 — The Card Draw Interaction

Gesture-first. 78 real choices.

A fan of 78 card backs arcs across the screen. Swipe to browse, tap to select — physically fanning a real deck, translated to mobile. Unlike the standard 'tap one face-down card', the arc makes all 78 choices visible, reinforcing that the selection is real.

Pre-selection

Pre-selection

Card placeholder visible above the arc, awaiting a draw

Post-selection

Post-selection

Chosen card rises from the arc into the reading position

05 — Card Detail & Reading Results

Layered meaning without overwhelm.

Card detail EN

EN — keyword tags & meanings

Card detail ZH

ZH — localised card content

Amber keyword tags — fast, scannable signposting before body text

Short prose under each keyword — approachable for beginners, detailed for practitioners

Light background signals 'reading mode' and reduces fatigue during longer sessions

Fully localised — card names, keywords, and meanings available in English and Chinese

06 — Three-Card Reading Flow

Past / Present / Future.

Three sequential draws, one position unlocked at a time. Results shown individually per card — not a three-up layout — so each card's meaning gets full attention.

0 drawn

0 drawn

Past drawn

Past drawn

Past + Present

Past + Present

All 3 drawn

All 3 drawn

07 — Testing

Maze testing. 6 participants.

Key Findings

5/6 completed the full flow without error on first attempt

Card arc was the standout moment — all 6 called it 'satisfying', 'tactile', 'like a real deck'

Oracle character felt like a trust signal — users felt 'guided', not alone with information

Iterations

Added 'Swipe & Tap' affordance label — first-time users were unsure of the gesture

Increased keyword tag spacing — users losing their place mid-scroll

Replaced spread selection text labels with card icon visuals

Outcomes & Reflection

Anime art as strategic differentiator.

The character, world, and visual consistency create a product genuinely distinct from every existing tarot app. The multi-step reading flow and collectibles system lay the groundwork for a habit product with real retention potential.

Proud of

Card draw arc — translating the physicality of real tarot into a gesture-first mobile mechanic

Dual palette theme — ritual transition without any user action required

Oracle character throughline across every reading screen

Next steps

Reading Log — saving past readings with date, focus, and notes (most requested in testing)

Deeper Collectibles — new card back designs or oracle outfits as practice rewards

Onboarding path — first-run reading calibrated to self-reported experience level

View the full prototype.

Full prototype and design system on Figma

Open in Figma ↗
Velo by East West Bank

✦ Product Design Case Study

Debit Card Perks

Enhancing Card Value Experience for International Students

Role
Lead Product Designer
Timeline
March – August 2022
Platform
Mobile & Online Banking
Teams
PM · Design · Dev · QA · Compliance

Overview

Velo by East West Bank had no debit card rewards experience. I led the design of a new Debit Card Perks program — giving international students and debit card customers a way to discover offers, earn cash back, and track rewards directly inside MB and OLB.

01 — Context

Why this project.

Velo by East West Bank had no debit card rewards experience. Debit card holders — especially the international student segment — had no native way to discover merchant offers, earn cash back, or track rewards inside the banking app. A competitor audit confirmed this was a gap the market had already solved; East West Bank hadn't. The ask was to design it from zero.

Current situation

No East West Bank-owned surface for offers.

Customers who wanted debit rewards had to leave the app entirely and find offers through third-party services. No cash-back tracking, no map of nearby deals, no reason to stay engaged between transactions.

Ecosystem

MB + OLB, no feature gap.

The program needed to live in both Mobile Banking and Online Banking with consistent capability. Entry on mobile via a Perks diamond quicklink. Student Perks ran as a subset of the same offer engine, tailored for enrolled students.

User journey map

Awareness (Perks quicklink on home) → discovery (category browse or map view) → merchant detail (offer terms and activation) → cash-back summary (pending vs. settled, lifetime totals). The highest-friction point was discoverability — users didn't know the feature existed until we surfaced it as a primary entry point.

02 — Problem-Solving

User research.

Competitive analysis covered U.S. and international markets — Wells Fargo, Chime, and Rakuten for the domestic frame; JD.com, Meituan, Dianping, and Ctrip for the super-app paradigms familiar to East West Bank's bilingual international student base. Target users: NRA students and SSN/NRA debit card customers — price-sensitive, bilingual, actively seeking deals. Internal data confirmed this segment was the highest-churn risk with the lowest in-app engagement.

Competitors analysed: Wells Fargo, Chime, Rakuten, JD.com, Meituan, Dianping, Ctrip

Painpoints

No offer discovery layer. Customers had no native way to find merchant offers. Without a browsing surface — category-indexed, searchable, map-enabled — there was nothing to engage with. Offers that existed through partner programs were invisible inside the product.

No cash-back visibility. Pending cash-back, settled amounts, and lifetime totals existed at the program level but were completely absent from the customer-facing product. Users had no feedback loop to confirm their card was working for them.

No geographic context. Debit card spending is local. Without geo-targeted discovery, the offers list felt abstract — a grid of merchants with no relevance to where the customer actually was.

Solutions

Solution 1

Category browsing with search

Eight categories — Grocery, Gas & Auto, Restaurants, Shopping, Travel, Health & Beauty, Home Goods, Entertainment — with icon-led navigation drawn from JD.com and Meituan, adapted for banking. Search indexed across merchant name, category, and descriptive keywords.

Solution 2

Real-time cash-back tracking

A dedicated summary view surfacing current balance, pending rewards, and lifetime totals. Pending vs. settled framing drawn from Chime and Rakuten — clear enough that customers understood when cash-back would settle without contacting support.

Solution 3

Geo-targeted map integration

Location permission requested with a trust-first design — explaining value before requesting access. Offers surfaced as pins within a configurable radius, making Perks contextually relevant at the moment of spending.

03 — Process

Brainstorming & user flow.

A cross-functional kickoff with PM, engineering, QA, compliance, and the East West Bank digital banking team set the early questions: What categories matter most to this user segment? How do we surface the entry point without disrupting the home screen hierarchy? How does Student Perks inherit from Debit Card Perks without requiring a separate design system?

Design process from PM ticket through to dev hand-off and future updates
Four primary flows

Offer discovery via category browse · Offer discovery via map · Cash-back summary and history · Offer activation and detail. Entry point unified through the Perks diamond quicklink, with branching for enrolled students vs. standard debit holders.

Hi-Fi · Visual System

Typography, icons, entry point.

Type built on Nunito Sans for legibility across Latin and extended character sets. A bespoke category icon set and a colour system designed to hold a wide range of merchant brand colours without visual conflict.

Colour system

Colour palette

Category icon set

Category icons

Quicklinks entry point

Quicklinks: Perks, Zelle, Check Deposit, Bill Pay, Statements

The Perks diamond quicklink (highlighted) is the primary entry point from the MB home screen.

Hi-Fi · Mobile

End-to-end mobile experience.

Home screen entry point → My Perks (featured offers) → category browse → map with geo-targeted pins → offer detail → cash-back summary. Walking through each flow below.

Landing flow — entry from home screen

Flow 01 — Landing

Entry from the home screen.

A single tap on the Perks diamond quicklink takes the customer from the MB home screen straight into the program. No menu drilling, no modal interstitial — discoverability was the biggest barrier in earlier rounds, so the entry point sits in the primary quicklink row alongside Zelle and Bill Pay.

Flow 02 — Offer Details

Terms and cash-back rate, made obvious.

The offer detail page surfaces the cash-back rate, eligibility window, and merchant terms above the fold. Activation is a single CTA. Everything a customer needs to decide whether the offer is worth using lives on this one screen — no hidden fine print, no follow-up taps for the rate.

Offer details flow
Account Summary — cash-back balance flow

Flow 03 — Account Summary

Pending, settled, and lifetime totals.

A dedicated summary view that closes the feedback loop: how much has been earned, how much is still pending settlement, and a lifetime running total. The pending vs. settled split — borrowed from Chime and Rakuten — is the single change that reduced support tickets about "where's my cash back" the most in internal review.

Map integration & local offers

Map permission

Location permission — trust-first design before requesting access

Map offers

Geo-targeted pins — offers surfaced within a configurable radius

Hi-Fi · Online Banking

Full desktop parity.

The desktop experience mirrors mobile — same offer detail pages, same cash-back flows, same enrolment path. Customers switching between mobile and web encounter no capability gap.

OLB on iMac

Design Detail · Marketing Page

Driving enrolment from outside the app.

A companion page outside the logged-in banking environment introducing Debit Card Perks to prospective customers — communicating value, surfacing key categories, and driving enrolment. Designed to work for both existing East West Bank customers and acquisition traffic.

Marketing page on iMac

04 — Impact

A new lever for customer engagement.

The Debit Card Perks program gave East West Bank a new lever for customer engagement — offering meaningful discounts to debit card holders across both mobile and web, while directly addressing an underserved, high-churn segment.

1M+

East West Bank customers with access

8

Merchant categories at launch

2

Platforms — MB & OLB

Knock-on effects

Student Perks, built on the same infrastructure, became a key selling point of the Student Product — reducing the differentiation gap against competitor student checking accounts. The program also established a geo-targeted offer layer as a first for East West Bank's digital banking product, and a reusable design pattern for future merchant partnership integrations.

05 — Takeaways

What I learned.

What I learned

Designing for a bilingual, price-sensitive segment sharpened my instinct for information hierarchy. Every label, every empty state, every cash-back summary had to communicate clearly on the first read — no idioms, no assumed familiarity with U.S. banking patterns.

The cross-market competitive analysis was one of the most valuable inputs — it prevented the team from optimising against a domestic baseline when the actual benchmark was significantly higher. Super-app users expect frictionless geo-discovery and real-time reward visibility as table stakes; most U.S. banking apps were nowhere close.

Working zero-to-one across PM, engineering, QA, and compliance reinforced how early decisions — like the category taxonomy and entry point hierarchy — compound downstream. Getting those right in the first week saved weeks later.

What I'd do differently

I'd push for moderated usability testing with actual students earlier — specifically on the offer detail page and cash-back summary. Both passed internal review but I believe there was room to reduce the cognitive load of the rewards breakdown for a first-time user.

I'd also advocate for a geo-permission A/B test: requesting access at first launch vs. deferring until the user explicitly navigates to the map. The deferred request likely converts better, and the data would have been worth having.

Finally, I'd build the category icon system as a shared component in the design system from day one — not as a project-specific set. The icons were extensible in theory, but adding a new category mid-project was slower than it should have been without a system-level owner.

Enhancing Card Value Experience.

Velo by East West Bank · 2022

Velo by East West Bank

✦ UX Research Case Study

NRA User Research

Optimizing the Velo banking experience for overseas customers

Role
Product Designer · UX Researcher
Timeline
June – August 2021
Methods
Moderated Remote Usability · Interviews
Deliverables
Personas · Journey Map · Prototype Updates

The Problem

A product that didn't fit the customer.

Velo's product set lacked the depth to serve its non-resident alien (NRA) customer base — limiting growth and weakening the experience for overseas users with distinct financial behaviours.

The Solution

Research-led product refinement.

Expand offerings with additional NRA checking products and refine onboarding and money-movement flows — synthesised from moderated sessions with overseas customers across three distinct segments.

Target Audience

Three distinct NRA segments.

Interview questions covered basic context and pain points across onboarding, transfers, and service expectations. Findings were synthesised into personas for each segment.

Persona — Investor

Investor

Persona — Family/Immigration

Family / Immigration

Persona — High Spender

High Spender

Research Process

Cross-border interview coordination.

Research spanned three time zones — the U.S. team, the Beijing product team, and APAC interviewees. This flowchart shows how preparation, interviews, and post-session logistics were divided.

Interview process flowchart

Journey Map

From awareness to loyalty.

Five stages — Awareness, Considerations, Enrollment, Funding, Loyalty — capturing feelings, thoughts, and pain points. Drop-off risk was highest at Funding, where fee opacity and transfer complexity drove churn.

NRA Journey Map

Top Insights

What the research revealed.

01
Guided onboarding is essential — NRA users needed a clear, step-by-step registration path with visible progress, especially for ITIN and SSN requirements.
02
Money movement must be effortless — High fees without clear rationale eroded trust at the critical funding stage. International transfers needed to feel simpler.
03
High earners expect VIP treatment — High-income customers looked for concierge-level service. A feature set no richer than a standard checking account was a blocker.

Competitive Context

Benchmarked against Chinese banking institutions.

NRA customers frequently held accounts at major Chinese state banks alongside Velo. Understanding their onboarding and transfer benchmarks set the bar Velo needed to meet — or exceed.

Competitor banks

Design Response

Two flows redesigned.

Research findings drove two high-priority prototype updates: a progress-bar onboarding flow and a simplified domestic wire transfer experience.

01 — Onboarding: progress bar added

A progress bar introduced a clear sense of where users were in registration — addressing anxiety from an opaque ITIN and SSN process.

Redesigned onboarding screens

02 — Domestic wire: friction reduced

Key information — amount, method, fees, confirmation — surfaces progressively, reducing cognitive load and improving trust.

Before

Wire transfer before redesign

After

Wire transfer after redesign

Listening as a product strategy.

By listening closely to overseas customers, the team turned qualitative insight into two shipped flows: a clearer onboarding experience and a less friction-heavy wire transfer journey.

The BBG Corp

✦ UX/UI · Creator Economy · Case Study

Quext.Me

A messaging app that helps creators monetize follower outreach and support charitable causes

Role
UX/UI Designer · Video Editor
Timeline
3 months · Launched Feb 2021
Methods
Moderated & Unmoderated Remote Studies
Deliverables
Research · Personas · Wireframes · Prototype

The Problem

Creators can't keep up with their inbox.

Experts and creators receive far more DMs than they can handle, with no incentive to respond. Followers seeking advice rarely get a reply — leaving value on the table for everyone.

The Solution

Turn outreach into revenue.

A mobile app that lets creators set a price for responding, accept or reject requests, schedule paid meetings, and route a percentage of earnings to charity.

Product Walkthrough

See the full experience.

Covers onboarding, the inbox, fee-setting, payment, the public Q&A library, and creator controls.

Research

Two audiences. Four findings.

Interviews across creators and nonprofit representatives. Creators consistently saw product-market fit; charities responded openly — "all money is good money."

Personal-brand reviewersStrongest fit. Creators with product-recommendation followings receive constant DMs and benefit immediately.
JournalistsLess direct value. Fewer one-to-one requests, but still hold knowledge worth sharing over time.
YouTube creatorsNeed comment triage. Most reach-outs arrive through public comments, so streamlining replies at scale is essential.
CharitiesWant reputation first, then scale. Smaller nonprofits saw value in building trust before partnering with larger organisations.

User Persona

User persona — Mike Pan

Design Process

Kick-off to prototype.

Aligned CEO, graphic design, and content strategy on goals and scope. Wireframes covered onboarding, conversations, payments, Q&A, and profile — refined before moving to high-fidelity.

User flowchart

Quext.Me user flowchart

Key Features

What creators can do.

01Set a fee before responding to a message
02Request payment in-chat for one-off services
03Donate a chosen percentage of earnings to charity
04Receive an assigned public phone number
05Accept or reject incoming requests
06Timed chats with an end-chat control for the creator
07Public Q&A library with paid access to past answers

High-Fidelity Prototypes

Three complete user journeys.

Full prototype coverage across onboarding, messaging and payment, and the broader feature set including Q&A, contacts, settings, and payments.

01 — Onboarding flow

Onboarding flow

02 — Messaging, pricing & donations

Messaging flow

03 — Features, Q&A, contacts & payments

Features flow

A two-sided value exchange.

Creators are compensated for their time. Followers get reliable access. Charities gain a new funding channel. Grounding the design in direct user interviews ensured the final product addressed real pain points across every group.

Velo by East West Bank

✦ Product Design Case Study

CashFlow Central

A new way for small businesses to manage cash, pay vendors, and track bills — built inside East West Bank's app.

Role
Lead Product Designer
Platform
Mobile & Online Banking
Timeline
Jan - Mar 2026
Teams
PM · Design · Dev · QA · Compliance
CashFlow Central intro screen
CashFlow Central benefits screen

01 — Context

Why this project.

East West Bank's app (Velo) had a growing base of small business customers. None of them had a built-in way to manage cash, pay vendors, or track bills. CashFlow Central — a Fiserv product — filled the gap. I designed the full customer experience from first marketing email to post-enrollment.

Many East West Bank customers are international business owners and first-generation entrepreneurs. Clarity and trust matter to them. Getting this right meant balancing Fiserv's technical limits with East West Bank's customer expectations.

Where CFC lives in the app.

CFC sits inside the Transfer & Pay area and shows a promo card on the home dashboard. Users never leave the bank — CFC loads inside a secure frame using single sign-on.

East West Bank Velo dashboard with CashFlow Central promo card

01 · Dashboard promo card

Transfer & Pay screen showing the CashFlow Central entry tile

02 · Transfer & Pay entry tile

How do you add a powerful new product to a trusted banking app — without breaking that trust or overwhelming people at sign-up?

Ecosystem

Designing inside someone else's system.

CFC lives inside East West Bank's app but is built by Fiserv. That meant working within a tight set of rules.

Single sign-on. Users log in through East West Bank once. No second login.

Account changes happen on East West Bank's side. Adding or removing bank accounts runs through East West Bank's system, not Fiserv's.

East West Bank's own terms. East West Bank used its own Terms & Conditions instead of Fiserv's default — which meant extra compliance work.

Two bill-pay tools at once. Existing customers had to keep their old tool or switch — without confusion.

Business accounts first. The first account used to pay must be a business one. Personal accounts can come later.

User Journey Map

From the first email to post sign-up.

I mapped the full journey in two passes — a first version, then a refined one based on what we learned. Seven key moments.

01
First campaign email

Introduces CFC to current and new customers.

02
In-app messages

Gentle awareness — no interruptions to banking tasks.

03
Landing page

Teaches first. No sign-up button until people understand what they're getting.

04
Re-engagement email

A nudge for people who didn't open the first email.

05
Sign-up · Pick a business

Users pick which business to enroll — one or many.

06
Drop-off email

Brings back users who started but didn't finish.

07
Welcome + milestone emails

Helps people get comfortable in the first 90 days.

02 — Problem-Solving

Three users. One product.

I looked at competitors, talked to internal teams, and reviewed how customers used the existing tool. Three user types stood out — and the design had to serve all three without becoming a mess.

Level 1 · Owner

The boss.

Makes the money decisions. Signs up the business, accepts the terms, approves staff. One per business.

Level 2 · Manager

The office manager.

Handles payments day to day. Can approve staff actions, set up autopay, and pay bills on their own.

Level 3 · Staff

The junior staffer.

Limited access. Small payments go through. Bigger ones need approval from the boss or office manager.

A key customer insight

Many East West Bank customers compare their banking to apps like WeChat and Alipay. They expect things to feel effortless — a bar most U.S. banks don't meet.

Painpoints

Where the experience was breaking.

01

Sign-up felt sudden.

New users hit the sign-up screen with no explanation of what CFC was or what it cost. Many dropped off right away. Hidden fees caused frustration later, after charges appeared.

02

Owners with several businesses got stuck.

People expected to sign up once and cover all their businesses. But sign-up worked per business. Without a clear pick-your-business step, many enrolled only one and called support.

03

Staff hit dead ends while waiting for approval.

Staff who tried to use CFC before their boss approved them saw nothing — no message, no next step. They kept trying to log in, then called support.

Solutions

Designing the way out.

Solution 01

A landing page that teaches first.

Added a landing page — "Every payment. Perfectly tracked." — that everyone sees before sign-up. It covers three benefits (Convenient, Powerful, Flexible), shows fees clearly, and ends with one simple call to action.

Prototype: landing screen with benefit cards, fee callout, and button states.

Animated walkthrough of the CFC education-first landing page
Animated walkthrough of the business selection screen

Solution 02

Pick a business, with a smart button.

A new screen shows all the user's businesses before sign-up — built on a pattern they already know from Zelle. The button changes from "Enroll →" to "Continue →" for businesses already signed up, so no one signs up twice by mistake.

Prototype: covers one business, many businesses, already-enrolled, and not-eligible.

Solution 03

A calm waiting screen for staff.

Staff waiting for approval now see "Contact Your Administrator" — a friendly warning icon, plain words, and one clear button to go back. No dead ends, no jargon.

Prototype: the full staff path from waiting → approved → access granted.

Animated walkthrough of the Contact Your Administrator state

03 — Process

Mapping every branch.

We kicked off with PM, engineering, QA, compliance, and Fiserv. Early talks focused on the branching logic — user type, number of businesses, sign-up status, and error states.

An early idea — one flow for everyone — fell apart fast. Bosses and staff needed very different paths. So we built two.

Decision map

A visual map of every yes/no point in the journey — One business or many? Boss or staff? Have the terms been signed? Are the accounts eligible? — became the single source of truth for design and engineering.

Final designs for mobile and web.

Built in Figma for iOS and desktop. Every screen, every error, every loading state. Here are the four main ones.

East West Bank Velo home dashboard with the CashFlow Central promo card

Dashboard · CFC promo on home

Transfer & Pay grid with the new CashFlow Central tile

Entry · Transfer & Pay tile

CashFlow Central splash and feature highlights

Splash · Introducing CFC

CashFlow Central benefits landing — Convenient, Powerful, Flexible

Benefits · Every payment, perfectly tracked

Design details that mattered.

Smart button label

Enroll → Continue. A tiny change that stopped people from signing up twice for the same business.

Equal-weight terms buttons

"Yes, I agree" and "No, I do not agree" look the same. No dark patterns. Compliance signed off.

Fees shown up front

The landing page shows fees before sign-up. No surprises later.

Easy to translate

Short sentences. No idioms. Ready for East West Bank's Mandarin-speaking customers.

Error State Design

Designing for every outcome.

Three error screens needed careful wording — calm, not alarming, with a clear next step. A fourth handles staff waiting for the boss to sign the terms.

Contact Your Administrator screen

Pending · Contact Your Administrator

No Eligible Business Accounts screen

Ineligible · No qualifying accounts

Waiting for approval

Staff are signed up but the boss hasn't approved yet. Calm tone, warning icon — not an error.

Not eligible

Shown when there's no business account, or when staff try to sign up. Points them to support.

Account paused

A clear stop with a button back to the dashboard. No technical jargon.

Terms not signed

Staff can't access until the boss accepts the terms. Says so without exposing internal roles.

Email Touchpoints

Bringing people back, beyond the app.

A series of emails — launch, reminder, drop-off, welcome, and milestone — keeps people moving forward outside the app. All compliance-approved and written for East West Bank's bilingual customers.

East West Bank CashFlow Central campaign email

Campaign email · "Now business payments are faster and easier"

04 — Impact

From zero to a finished product.

CashFlow Central gave East West Bank's small business customers a tool they never had inside Velo. The full sign-up experience went from blank page to compliance-approved, build-ready design in one cycle.

1M+
East West Bank customers with access
3
User types with their own flows
7
Touchpoints in the journey

The project also built a reusable pattern for adding outside products to East West Bank's app — making future integrations faster. And the two-phase rollout set a model for shipping in stages and learning as we go, instead of one big launch.

05 — Takeaways

What I learned.

In banking, the most important decisions aren't about how something looks. They're about how it's structured and the exact words on a button. Every dead-end screen chips away at trust in the bank.

Holding the design and the technical model in my head at the same time was hard. The API shaped what was possible — and knowing it well let me push for the right experience without asking for the impossible.

Compliance is a design partner, not a gatekeeper. Equal-weight terms buttons, up-front fees, plain-language errors — all got stronger because of compliance, not weaker.

Mapping decisions before drawing screens saved weeks. Every new edge case had a clear place on the map.

What I'd do differently.

I'd test with real small business owners earlier — especially the pick-your-business step. It worked in review, but I think we could have made it lighter for people juggling several businesses.

I'd build a shared error-screen library with engineering from day one. We ended up designing errors as they came up, instead of mapping them all at the start.

And I'd push for A/B testing the landing page button. "Start using CFC" won, but "Get started" and "See how it works" were close. Even small wins compound over a quarter.

Explore the Work

View in Figma

Open Figma File ↗
🤝 Captain's Handshake