← All work
Charles Schwab2019–2023Sr. Team Manager, UX Design

Building the Schwab Assistant, from labs to launch

A conversational AI that helps clients reach their financial goals, and the research, patterns and design system that made its answers usable.

Executive summary

7 min read
What I did
Built the Schwab Assistant, Charles Schwab's conversational AI, from concept to launch in the mobile app as its UX lead and then manager. Led the research, the conversational design system and the patterns behind its most-used answers.
Who with
A team that started at 12 people and was 90 when I rolled off: designers, a researcher, content strategists, product owners and PMs, plus mobile, web, middleware, live chat, NLP, architecture and data teams.
Intent & reasoning
Three business problems: off-load chat and call volume, ease navigation and search issues, and respond to current events faster.
Outcomes
27%average reduction in calls and chats
96%Schwab Assistant accuracy
400k+monthly users
1290people on the team when I rolled off

Assistant metrics as of March 2023; monthly users from LinkedIn.

The hook
A test participant compared our early answers to Alexa rambling off a wiki page. Fixing that made rich answers our most-used intents. Read the story ↓
Charles Schwab project cover
01Context

A financial assistant for people who'd rather do it themselves

Simply put, the Schwab Assistant is a conversational AI designed to support clients in achieving their financial goals. Our users were self-directed investors.

Our user

DIY segmentHigh income, average savingsMore confident in their abilities than a professional'sHighly drivenTrusts algorithms over humans for financeUses modern digital information sources

The assistant, as of March 2023

27%average call and chat reduction
14%adoption rate
81%NLU accuracy
96%Schwab Assistant accuracy
3average turns per conversation
4daysto ship an intent for a current event
02The problem

A paragraph of numbers is technically an answer

Early testing showed a pattern: the more data an answer held, the less useful it became as text. So the study focused on rich responses.

“Have you ever asked Alexa what something means and she starts rambling off a wiki page and you just want to scream STOP? Reading this paragraph on a daily basis would be like that.”
User testing participant

The questions

01

How much data do we show so it's easy to digest, while leaving a path to dig further?

02

How do we validate this and apply it in a scalable way, including on the backend?

03

How do we show partners the value of visual answers in a conversational agent?

03The process

From sketches to a system

  1. 01DiscoveryFrom user testing
  2. 02ResearchIndustry & competitive
  3. 03Study 1Partitioning information
  4. 04Iterate
  5. 05Study 2The accounts flow
  6. 06ShareFindings and scaling approaches, with partners
↳ Added to our Conversational Design System↳ Applied to our navigational strategy
Card sorting intents during research
Prioritizing intents with clients
Competitor assistants: TD Ameritrade, USAA, Bank of America Erica, Robinhood
Competitive review: TDA's Ask Ted, USAA, BoA's Erica, Robinhood
04Study 1

Break it up, and five of six succeed

We tested the same account answer two ways in a moderated study.

Before1 of 6 succeeded
Schwab Assistant

What are my balances?

As of 11:16 AM ET, 07/01/2019, your Designated Beneficiary account ending in 634 has a value of $16,748.34 and has a day change gain of 0.3%, up $23.13. Your Retirement Savings Investment account ending in 136 has a value of $77,658.24 and has a day change gain of 0.01%, up $13.16.

Sketch: one long paragraph listing two accounts
After5 of 6 succeeded
Schwab Assistant

What are my balances?

Here are your accounts as of 11:16 AM ET, 07/01/2019.

…634 Designated Beneficiary

Value
$16,748.34
Day change
+0.3% $23.13

…136 Retirement Savings Investment

Value
$77,658.24
Day change
+0.01% $13.16
Sketch: a short intro and one bubble per account
05Study 2

People recognize accounts by name and balance

“I know which account is which by the amount.”
“It's that one because it's my only brokerage account.”
“Yes, the one named ‘Jan and Pete’, that's how I know it's our joint account.”
Schwab Assistant accounts view with account name, type and balance
06What we shared

Five principles for rich responses

We took the findings to product and development partners, along with what the platform needed to support them: a pipe symbol in the CMS to split bubbles, clean APIs for every channel, data viz on screens, and voice-only versions for screen readers.

1

Partition responses when appropriate.

2

If more than 3 data points are presented, it needs a visual component.

3

There is an intuition to engage with the response to dig deeper.

4

Done right, rich intents can be reused in multiple task flows.

5

When a client selects an account, include the name, type and balance.

07Patterns from testing

No dead ends. Clean the screen.

We ran 4 moderated studies in 2019, my first year, and 10 in 2020, testing the principles and turn logic, not just features. Nearly all of the turn logic came from things we saw again and again in testing.

Inline actions
Transfer status answer with inline links
  1. Tied to the turn: trigger another intent, deep link in the app, open a CMS asset, place a call, start an email, or automate slot-filling.
Smart prompts
Limit order definition with smart prompts below
  1. No dead ends: every turn of the conversation leaves next steps. Prompts can be contextually analogous, relevant to the intent, or a default set.
“I don't know why I keep hitting the ‘X’… I guess maybe I thought it would refresh it or just clear all of this out.”
The participant who ignited Clean the Screen
Clean the Screen: a new answer replaces the stacked conversation
Participants kept closing and reopening the assistant. It wasn't a refresh button they needed: the more visual complexity, the harder it was to focus on what to do next.
Usual response
Positions answer for a client with no investment account
Turn logic
Answer that offers to open an account or view the watchlist
08The system

In a voice interface, the logic is the design

With replicating language at scale comes organization through systemization. We built the Conversational Design System so the team could onboard faster, communicate out, and stay aligned as we grew. Every feature shipped with a designer package covering voice, mobile, web, watch and car.

Conversational Design System

FoundationsConversational guideDesign guideTurn logicComponents & patternsResources
Feature flow across voice, mobile, web, watch and car
Designer package: one flow, every channel
VoiceOver labels, traits and hints for smart prompts
Accessibility: what VoiceOver speaks, and how
“In a voice interface the underlying logic and documentation IS the design.”
Managing UX Director of Mobile, Charles Schwab
09What changed

Rich answers carried the most-used intents

Voice is the most efficient input. A screen is still the most efficient output.

#1
Positions answer in the Schwab Assistant
Positions
#2
Quotes answer in the Schwab Assistant
Quotes
#5
Market update answer in the Schwab Assistant
Market update
#9
Market indices answer in the Schwab Assistant
Market indices
#54
Equity ratings answer in the Schwab Assistant
Equity ratings

Intent traffic rankings since July 2020, out of 758 intents

How it helps the client

01

Consistency across channels means less friction and cognitive load, whatever channel they're on.

02

A formal way to turn client needs into principles.

03

Components in one place, so a fix like an accessibility pattern reaches clients quickly.

04

An established way of working makes it easier to onboard and scale.

10Beyond the assistant

Advisors got their answer on the first call

I also co-led a multi-team project on digital recommendations that streamlined advisor workflows. It was recognized with an Excellence in Equity Award.

50%90%first-call success rate, exceeding targets
~30 minsaved per rep, per week
Next case studyKnocki63% improvement in device provisioning: drop-off fell from 51.2% to 18.9%.