Quality starts before the review.

The problem

Shared standards still need shared understanding.

USAA’s Reveille Design System provided a common foundation. Applying it consistently across responsive web experiences required more than selecting a component: teams needed to agree on its intended use, accessibility behavior and the member journey around it.

As my team’s appointed QA Advocate, I met with other advocates one to two times per month to discuss Foundation Review defects, including incorrect component usage and accessibility markup. One reporting cycle raised a question: did the defect totals accurately describe the quality of what designers handed off?

01 · Investigate, pilot, influence

I questioned the reporting model, then tested an alternative.

I started with my team’s defect data. Using data analytics, AI and Excel, I investigated reporting inconsistencies and performed root-cause analysis. That work helped me propose a clearer definition of a defect within the scope of the design handoff.

1. 01

   Examine the evidence

   Use the team’s reported defects to identify inconsistencies and root causes.

2. 02

   Clarify the review

   Define defects against the intended design handoff and apply accessibility expertise.

3. 03

   Pilot with my team

   Test the QA strategy and track Foundation Review results over six months.

4. 04

   Build broader support

   Present findings to QA and Design System directors and other stakeholders.

Explanatory reconstruction of the process, based on my account. This is not a reproduction of an internal reporting dashboard.

From team evidence to organizational change

The pilot and my accessibility work helped my team reduce Foundation Review defects by 50% within six months. My presentation secured buy-in for implementation across the design organization. The wider organization also saw a substantial decrease in reported defects.

02 · Accessibility in the design handoff

Specify the experience beyond what is visible.

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 EOA team.

Illustrative handoff categories. An annotated disputes screen will provide the next supporting artifact.

Accessibility is part of design quality.

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.

03 · Contribute for reuse

Solve the immediate need without creating a one-off.

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.

The contribution extended beyond a single component.

Other work included data-table enhancements, messaging, data visualization and member task flows. Across these contributions, I balanced an immediate delivery need with the system’s value to other teams.

What changed

Better design quality, with a clearer basis for review.

• Team impact: 50% fewer Foundation Review defects within six months of the revised QA strategy and accessibility work.
• Organizational influence: director and stakeholder buy-in led to adoption across the design organization.
• System contribution: production badge implementation, confirmation-pattern work and reusable process guidance.
• Design leadership: recurring advocacy connected component use, accessibility handoff and evidence from reviews.

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.