ARC Settlement / Section 03 of 05
Process
Due to NDA constraints, I'm describing the approach and decisions in general terms rather than showing screens. The interactive demo on this page is fictional and illustrative.
Mapping the system before the screens
I mapped the full life cycle of a ticket as service blueprints: cash sales, credit sales, early credit billing, a change of payment method, and sales edited by the agency before the cycle closed. Each blueprint traced what the customer, agency, airline and ARC teams see at every step, which systems are involved, and when the data changes from initial (as the agency submitted it) to settled (final for the cycle).
That timing turned out to explain most of the confusion. Users weren't missing data so much as looking in the wrong place for the stage a ticket was in.
Document lookup
I designed a new tool for finding any ticket by its document number, built from task models for every document type: straight sales, refunds, voids, and one-to-one and one-to-many exchanges.
- One search by document number, refined by airline or agency depending on the user's permissions.
- Results default to settled data, with an option to see the initial data as the agency submitted it.
- A transaction history that follows the exchange chain, so one search shows the original ticket, the exchange and any refund together.
- Document details shaped to the transaction type, with the summary users need to verify or explain a transaction first and the full record one step away.
- Sign-in and session flows designed alongside the customer portal: bookmarked links, many open tabs, timeouts and logging out across apps.
RUN DEMO: Look up a ticket and follow its exchange chain
Editing refunds and exchanges
In the modernized reporting tool, agents choose which flight segments a refund or exchange covers, and that choice makes it full or partial. I defined what happens to their numbers when they go back and change segments after entering figures, so no one loses edits without being told:
- Full to partial: the figures stay as they are. If the agent never edited them, the confirmation step flags that a partial refund still matches the full amount.
- Partial to full: the full-document figures are filled in. If the agent had entered figures of their own, they are asked first, so nothing they typed is replaced without warning.
RUN DEMO: Change segments on a refund
I also mapped dependencies for a later release of the tool, sequencing sales reports, transaction edits, memos, payment features, configuration and permissions so each release stood on the one before it.
Discovery for transaction file intake
I facilitated discovery with the teams who receive the daily transaction files. The workshop reframed a broad request ("we have problems with errors") into a problem statement, questioned its assumptions with the five whys, and planned the research to follow.
An ecosystem map and current-state journey maps traced the work across booking systems, data center operations, production support, card operations and the settlement team. They surfaced the opportunities: notify partners automatically when files arrive late or fail, move invalid transactions to a holding area for review instead of dropping them, and replace hard-to-read legacy text reports with reporting partners can actually use.
Design principles
Clarity over completeness
PrincipleSurface the information users most frequently need to verify or explain transactions, not the full depth of the system by default. Progressive disclosure over information overload.
Why it matteredAgents under time pressure made more errors when confronted with dense, unfiltered data. Reducing cognitive load at the decision point directly reduced error rates.
Terminology alignment
PrincipleAudit, flag, and redesign ambiguous labels that caused misinterpretation across tools and teams. Language is part of the UX.
Why it matteredA single misunderstood status label could trigger incorrect downstream actions in a compliance-sensitive workflow. Getting terminology right was a risk-reduction strategy.
Shareable states
PrincipleDesign streamlined, readable views optimized for communication with end customers, reflecting how agents already worked in practice.
Why it matteredAgents were already creating screenshots and workarounds to share transaction status with customers. Designing for that reality eliminated shadow workflows.
Research & Validation
One of the most significant contributions of this project was introducing a new testing model to ARC. I designed an asynchronous usability testing approach that allowed participants to explore interactive prototypes on their own schedule, reducing scheduling friction and producing more natural behavioral signals than traditional moderated sessions.
Async Usability Approach
- Lightweight interactive prototypes
- Behavioral observation without scheduling
- Structured feedback collection
- Later adopted org-wide
Research Toolkit
- Stakeholder and discovery workshops
- Ecosystem maps and current-state journeys
- Service blueprints of the ticket life cycle
- Task models for every document type
- Terminology audits across systems
The testing model proved effective enough that it was adopted more broadly within the organization, shifting how ARC teams approached discovery going forward.