USAA CFO Treasury Applications

Redesigning internal treasury management tools across 7 agile squads

Role

Senior UX Designer

Timeline

June 2022 - August 2023

Team

7 squads (35+ people)

Tools

Figma, Axure, Miro, Azure DevOps

Project Overview

The Challenge: USAA's CFO organization relied on outdated internal treasury management systems that had evolved organically over 15+ years. Treasury analysts spent excessive time navigating between disconnected tools, manually reconciling data, and working around system limitations. The organization needed to modernize these critical financial operations tools while maintaining business continuity.

My Role: As Senior UX Designer embedded across 7 agile squads, I was responsible for creating wireframes, interactive prototypes, and design specifications for treasury applications including wire transfers, cash management, investment tracking, and RPA workflow tools. I worked in two-week sprints, collaborating directly with product owners, treasury analysts, and development teams to rapidly iterate on designs.

Key Responsibilities:

  • Conducted 25+ contextual inquiry sessions with treasury analysts to understand daily workflows and pain points
  • Created wireframes and interactive prototypes for 12 different treasury management applications
  • Designed RPA (Robotic Process Automation) monitoring dashboards to track automated financial processes
  • Established consistent interaction patterns across squad deliverables to create cohesive user experience
  • Facilitated design critique sessions with stakeholders to validate designs before development handoff
  • Collaborated with developers during implementation to ensure design fidelity and address technical constraints

Application Overview

💼 Treasury Dashboard Interface

Replace with treasury management dashboard showing key metrics and workflows

Design Process & Methodology

1

User Research

Shadowed treasury analysts during their daily work to understand workflows, pain points, and workarounds. Documented 8 core user journeys and identified 15+ high-priority usability issues. Created detailed user personas for different treasury roles including cash managers, wire transfer operators, and financial controllers.

2

Information Architecture

Reorganized fragmented tools into coherent task-based workflows. Conducted card sorting exercises with 12 users to validate navigation structures. Developed site maps for each application showing relationships between features and data flows across systems.

3

Wireframing & Prototyping

Created low-fidelity wireframes for rapid concept validation, then progressed to high-fidelity interactive prototypes in Figma. Built clickable prototypes for usability testing with 5-8 users per sprint. Iterated based on feedback before handoff to development teams.

4

Agile Integration

Worked in two-week sprints alongside development teams. Participated in daily standups, sprint planning, and retrospectives. Created design specifications and annotation documents for developers. Conducted design QA during implementation to ensure design intent was preserved.

Research & Key Insights

👥 User Personas & Journey Maps

Replace with user research artifacts showing personas and workflow documentation

User Pain Points

  • Treasury analysts toggled between 6-8 different systems to complete single wire transfer, increasing error risk
  • No centralized view of pending approvals created bottlenecks and missed deadlines
  • Manual data entry required copying information between systems, consuming 30% of daily work time
  • Inconsistent terminology across applications caused confusion and required tribal knowledge
  • Limited visibility into RPA automation status meant analysts couldn't troubleshoot failures independently
  • Outdated interfaces didn't support keyboard shortcuts, slowing down expert users

Design Opportunities

  • Create unified dashboard consolidating information from multiple systems into single view
  • Design bulk action capabilities to process multiple transactions simultaneously
  • Implement smart defaults and auto-population to reduce manual data entry
  • Establish consistent terminology and interaction patterns across all applications
  • Build transparent RPA monitoring with clear error states and remediation paths
  • Add keyboard shortcuts and power user features for efficiency gains

Key Design Decisions

Working across multiple agile squads required strategic design decisions to maintain consistency while delivering value quickly:

1. Task-Oriented Information Architecture: Reorganized applications around user tasks rather than system structure. For wire transfers, we moved from a system-centric flow (accounts → beneficiaries → templates → submit) to a task-centric flow (initiate transfer → verify details → approve). This reduced steps by 40% for common scenarios.

2. Progressive Enhancement for Power Users: Designed dual-mode interfaces that supported both novice and expert users. Basic mode provided guided workflows with helpful hints, while advanced mode offered keyboard shortcuts, bulk operations, and minimal UI chrome. Users could toggle between modes based on their comfort level.

3. Transparent Automation Status: Created comprehensive RPA monitoring dashboards that showed real-time status of automated processes, historical success rates, and clear error diagnostics. Enabled treasury analysts to identify and resolve automation failures without IT involvement, reducing resolution time from hours to minutes.

4. Flexible Approval Workflows: Designed configurable approval chains that adapted to different transaction types, amounts, and organizational hierarchies. Visual representation of approval status helped users understand where transactions were in the pipeline and who needed to take action next.

🎨 Wire Transfer Workflow Redesign

Replace with before/after comparison showing workflow improvements

Wireframes & Prototypes

📐 Low-Fidelity Wireframes

Replace with early sketches and wireframes exploring different layout options

🖥️ Interactive Prototype Screens

Replace with high-fidelity prototype screens showing key interactions

📊 RPA Monitoring Dashboard

Replace with dashboard design showing automation status and analytics

Key Learnings

Designing for Expert Users: Treasury analysts were domain experts who performed complex financial operations daily. Unlike consumer applications where simplicity is paramount, these users valued efficiency and precision over hand-holding. We learned to respect their expertise by providing power user features, keyboard shortcuts, and information-dense interfaces that reduced cognitive switching costs.

Working Across Multiple Agile Teams: Coordinating design across 7 squads required strong communication and documentation practices. We established weekly cross-squad design syncs, maintained a shared Figma library, and created design decision logs that helped teams understand rationale behind patterns. This prevented divergence while allowing squads to work autonomously.

Balancing Speed with Quality in Agile: Two-week sprints demanded rapid design iteration. We learned to timebox research and design activities, focusing on highest-risk areas first. Quick sketches and low-fidelity prototypes for concept validation, followed by higher-fidelity designs only after direction was confirmed, helped maintain quality without slowing velocity.

Internal Tools Deserve Good Design: Initially, some stakeholders questioned investing design effort in internal tools. However, user research revealed that poor tool design cost USAA thousands of hours annually in lost productivity. Demonstrating ROI through time-on-task measurements and error reduction helped build organizational support for UX investment in internal applications.

Legacy System Constraints as Design Drivers: Many treasury applications relied on mainframe backends with strict data formats and processing windows. Rather than fighting these constraints, we designed interfaces that made system limitations transparent to users, helping them plan work accordingly and reducing frustration from mysterious errors.