Align how teams contribute
I helped shape a repeatable framework for the pilot through reviews across disciplines and iterations on the proposed process.
USAA · Design systems · Accessibility · Design QA
I helped lead a Bank Library pilot for native banking experiences and served as my team’s QA Advocate. I connected shared patterns, accessibility and defect analysis to improve how we designed and reviewed member experiences.
My team, within six months of the new QA strategy, compared with the previous reporting.
The challenge and my role
Fragmented components across Bank Digital made it harder for teams to deliver cohesive member experiences. USAA’s Reveille Design System provided the enterprise foundation, but banking teams also needed patterns that addressed their native product workflows.
I helped lead the Bank Library pilot, a focused incubator forked from the Enterprise Design System. My contribution combined pilot activation, governance across disciplines and reusable design patterns. Alongside that work, I served as my team’s appointed QA Advocate, investigating recurring component and accessibility issues in Foundation Reviews.
These were connected responsibilities: help designers start from stronger shared patterns, communicate intended behavior clearly and use review evidence to improve the next design.
01 · Shared foundations
The Bank Library extended the enterprise foundation for native banking needs. I supported the pilot rollout and helped establish its governance and operating path, working through process proposals with design and product partners across business areas.
I helped shape a repeatable framework for the pilot through reviews across disciplines and iterations on the proposed process.
I embedded accessibility, component reusability and early QA checkpoints into design workflows, so teams considered quality from the beginning.
I facilitated workshops for rapid prototyping to help teams iterate and strengthen feedback on Bank Library components.
The pilot launched a reusable account summary layout called the Super Component template. It combined shared regions for the header, balance, messaging and service actions, giving designers a flexible starting point for account views at the highest level.
Account identity and context.
A shared region for balance information.
A place for account messages.
A consistent region for available account actions.
Conceptual anatomy of the template’s four core regions; reconstructed for this case study.
I partnered with product managers to connect design decisions to adoption, satisfaction and operational efficiency measures. Structured reviews with Product and Engineering helped clarify expected behavior and resolve implementation questions.
02 · Interaction patterns for reuse
I worked regularly with the Design System team to understand the core concepts behind Reveille, improve my team’s QA and contribute when our feature work exposed a missing pattern or component. Research, testing and consultation with other designers helped establish whether a solution could serve multiple experiences.
Pattern alignment
My first contribution examined confirmation screens across responsive web experiences. Teams differed in how they communicated success, task completion and what happened next. I researched and contributed to the shared patterns and component blocks.
Component delivery
A badge was already in the system backlog, but my feature needed it during the sprint. I consulted teams with similar needs, designed the initial concept and worked with Design System designers and developers to implement the badge for production use.
Reusable guidance
Before members entered the disputes flow, I built a reusable component explaining the tasks ahead. It set expectations for the next screens and the path to confirmation.

The exploration compared the existing messaging colors, stronger fills and a border with a light fill across five statuses. It made the options concrete for discussion with the Design System team, while retaining a written label for each status.
The pilot added an Action Menu to reduce page clutter while keeping account actions available, Spending Over Time and Balance Over Time visualization patterns, an enhanced Service Action Bar and empty state treatments. These additions addressed gaps in the patterns teams could use across account experiences.
My other contributions included data table enhancements, messaging, data visualization and member task flows. I considered the immediate feature need alongside whether the pattern could support other teams.
03 · Accessibility in the design handoff
In disputes, I used accessibility markup to communicate how members should understand and navigate the experience. QA and development had access to screen readers and other testing tools, and we consulted with the Enterprise Accessibility Office (EAO).
Document reading sequence, headings and meaningful content relationships.
Distinguish keyboard focus order from reading order; describe behavior as the flow changes.
Make labels, instructions, status and error messages understandable beyond their visual treatment.
I led initiatives to share knowledge on inclusive design, accessibility and QA practices. Better documentation and early reviews helped bring defect prevention into the design workflow.
I bring accessibility into early design decisions, carry it through the handoff and help teams understand the rationale. My aim is to design beyond minimum requirements and to include people with disabilities in research and evaluation wherever possible.
04 · Evidence and prevention

QA Advocates met one to two times per month to discuss Foundation Review defects, including component usage and accessibility markup. During one reporting cycle, I questioned whether the totals accurately represented what designers had handed off.
I started with my team’s defect data. Using data analytics, AI and Excel, I investigated reporting inconsistencies and performed analysis of root causes. That work helped me propose a clearer definition of a defect within the scope of the design handoff.
Use the team’s reported defects to identify inconsistencies and root causes.
Define defects against the intended design handoff and apply accessibility expertise.
Test the QA strategy and track Foundation Review results over six months.
Present findings to QA and Design System directors and other stakeholders.
The pilot and my accessibility work helped my team reduce Foundation Review defects by 50% within six months. My presentation secured support for implementation across the design organization. The wider organization also saw a substantial decrease in reported defects.
What changed
The lesson: a quality metric is only useful when teams understand what it measures. Challenging the reporting model constructively, testing a change within my team and communicating the evidence gave the organization a stronger basis for action.
Explore the disputes experience →Future direction · Planned work
My next objectives focused on aligning Account Summary, the Financial Feed and the Financial Wellness Zone. I wanted related visualizations to complement one another and give teams clearer guidance on where each belonged.
The planned work included a reusable “View Chart as Table” option, interactive bar and line chart exploration, competitive research and a workshop across disciplines on shared visualization standards. The table view was intended to make equivalent financial information available beyond the chart’s visual presentation.