Selected work
05

USAA · MESSAGING SYSTEMS

Making thousands of emails feel like one system

Members experienced every email as USAA. The organization produced them through many businesses, templates, and legacy conventions.

ROLELead design producer · Experience strategist
SCOPEEmail taxonomy · Heuristic review · Template strategy · Accessibility
CONTEXTInventory → evaluation → patterns → modular direction
5message families
7shared evaluation lenses
Mobile firstlayout direction
One systemmember experience goal

The emails shared a sender, but not a predictable experience.

USAA emails had accumulated across products and business areas. Members encountered inconsistent hierarchy, imagery, terminology, calls to action, support patterns, footers, and mobile behavior. Some messages carried too much detail; others made the required action difficult to find.

The challenge was not to redesign one email. It was to create a reusable system that could support required communications, member-requested alerts, security updates, personalized advice, onboarding, and marketing without making every message look or behave unrelated.

Create evidence and structure before proposing templates.

I helped organize the work around message intent, then used a shared heuristic framework to evaluate representative emails. This separated universal quality standards from the needs of each message family and made recurring problems visible across the portfolio.

Message taxonomyRequired communications, requested alerts, security and profile updates, personalized advice, engagement and onboarding
Evaluation lensesInformation visibility, language, imagery, security cues, mobile simplicity, clear actions, unsubscribe and support

WHAT THE AUDIT REVEALED

Different messages. Recurring experience failures.

Organizing the evidence by message job made the system-level opportunities easier to see.

Message familyMember needRecurring breakdown
Required communicationsUnderstand the obligation and locate the essential detail.Dense copy, buried actions, attachments competing with heavy footers.
Member-requested alertsRecognize what happened and whether action is needed.Inconsistent hierarchy, terminology, and levels of detail.
Security and profile updatesVerify legitimacy and act safely with confidence.Uneven security cues, dated instructions, and unclear support paths.
Personalized adviceUnderstand why this matters now and what to do next.Promotional titles, excess content, and inconsistent personalization.
Engagement and onboardingOrient quickly and continue the relationship.Competing messages, inconsistent imagery, and unclear primary actions.
01 · AUDITCompare representative messages

Evaluate examples against one member-centered framework.

02 · STANDARDSSeparate universal quality from message-specific needs

Define what should remain consistent and where emphasis must change.

03 · MODULESSolve recurring problems once

Reuse resilient structures for hierarchy, actions, support, and disclosures.

The system direction followed the way people scan email.

01

Lead with the message job. Make the subject, summary, and first heading clarify why the member received the email.

02

Make action unmistakable. Use one clear primary action when action is required—and state plainly when no action is needed.

03

Design mobile first. Use responsive structure, meaningful hierarchy, sufficient spacing, resilient text sizing, and dark-mode-aware assets.

04

Build modularly. Reuse headers, summaries, content blocks, support, disclosures, and footers while allowing the message family to control emphasis.

05

Reduce cognitive load. Move durable detail to appropriate destinations and keep the email focused on understanding and the next decision.

The audit turned subjective inconsistency into an actionable system agenda.

The work created a common vocabulary for design, product, content, accessibility, security, and business partners. Instead of debating individual preferences, teams could evaluate messages against the same member-centered criteria and identify patterns worth solving once.

The resulting direction was a modular email system with clearer hierarchy, responsive behavior, consistent language and imagery, accessible reading order and contrast, purposeful alt text, robust links and controls, and predictable support and preference patterns.

What this case demonstrates

This is systems and strategy work in progress: creating the inventory, evaluation model, and reusable direction required to improve a large communication ecosystem responsibly.

A template library should reduce decisions without flattening meaning.

The goal is not visual sameness. It is predictable quality: members should immediately understand why a message matters, what they need to do, and whether they can trust it—regardless of which part of the organization sent it.

NEXT CASE STUDY

How I Lead