
CHANGE Card
Connecting pay, loyalty,
and the talent experience.
Integrating CHANGE Card and loyalty rewards into Avionté’s agency and talent portals, with a shared structure for everyday account tasks.
I led UX design with 3Pillar Global to connect pay-card and loyalty experiences with Avionté’s existing agency and talent workflows.
- Role
- Lead UX Designer & project lead
- Client / delivery partner
- Avionté / 3Pillar Global
- Timeline
- Six-week project plan
- Design methods & tools
- Card sorting, workflows, wireframes, interactive prototypes · FigJam, Grafio on iPad
Desktop design · Scroll horizontally to explore
Rewards, in the everyday account experience.
The loyalty marketplace brings points, gift cards, and CHANGE Card account context into one place.
The challenge
Multiple portals. One connected experience.
Agencies already used several Avionté portals to manage talent. Talent also moved between portals to manage profiles. Adding a pay card and loyalty marketplace introduced more account tasks and external dependencies.
For agencies
Bring cardholder management, card inventory, loyalty administration, and existing staffing operations into a connected agency experience.
For talent
Keep profile, timesheet, pay history, CHANGE Card, and rewards access within a coherent talent portal.
My role and collaboration
As lead UX designer and project lead, I created workflows, wireframes, and an interactive prototype, and coordinated the design work within the project’s time frame. Massi Behbahani managed meeting coordination and JIRA records. Hitesh Acharya investigated the API dependencies for the next development phase.
- Client stakeholders
- AviontéBOLD product team · Chad Meyer, Product Manager
- Financial expertise
- Daren Jackson, RFS CEO and pay-card consultant
- Working rhythm
- Daily meetings and weekly feedback sessions with stakeholders and the internal team
People & responsibilities
Four people in this experience.
The same platform serves people managing their own money and people operating the program. Each needs a different level of context, control, and reassurance.
These scenario personas represent the talent, agency, branch, and loyalty responsibilities explored in the design. Names and motivations are illustrative, rather than interview findings.
Maya · Talent
Uses the talent portal to review pay, manage her card, send money, and redeem rewards.
- Goal
- Keep money tasks understandable and close to her work account.
- Friction to explore
- Portal switching, unclear transfer status, and an unexpected rewards shortfall.
- Needs
- Balance context, explicit review, and a clear next step.
Devon · Agency administrator
Finds cardholders and manages account-level card operations for a staffing agency.
- Goal
- Resolve a cardholder issue without losing account context.
- Friction to explore
- Selecting the wrong record or making a consequential change without confirmation.
- Needs
- Search, identity context, action review, and visible results.
Lena · Branch administrator
Handles branch-level administration and card operations within the agency experience.
- Goal
- Work inside the right branch and keep local operations moving.
- Friction to explore
- Ambiguous scope, unavailable inventory, and unclear reorder status.
- Needs
- Persistent branch context and clear inventory/reorder states.
Eli · Loyalty administrator
Coordinates enrollment, rewards configuration, point purchases, and points history.
- Goal
- Keep the rewards program understandable and reconcilable.
- Friction to explore
- Confusing points movements and disconnected purchasing or reward setup.
- Needs
- Program configuration, purchase review, and readable point history.
User journey
Access the portal. Complete the task. Understand the result.
The journey starts with one portal entry, then separates talent self-service from agency operations. Review and confirmation close the loop; recovery states help when a task cannot continue.
Talent self-service
Card management · Transfers · Bill pay · Rewards · Statements
Agency operations
Cardholders · Branches · Inventory · Loyalty administration
| Moment | Talent intent | Agency intent | Uncertainty to address | Design response |
|---|---|---|---|---|
| Enter | Reach pay and card tools | Reach the right agency or branch | Which portal or account am I in? | Shared navigation and persistent account/scope context |
| Orient | Check balance and points | Find the cardholder or inventory | Am I looking at the right data? | Visible balances, identifying details, and clear search results |
| Act | Send money, change settings, redeem | Replace a card, configure rewards, reorder | What does this action affect? | Specific task labels and focused forms |
| Review | Check amount, recipient, or shortfall | Check target record and operational scope | Can I undo a mistake? | Explicit review and correction before confirmation |
| Follow through | Know whether it succeeded | Know what changed and what comes next | Is it pending, complete, or failed? | Status, reference, history, and recovery route |
The journey map connects the platform’s tasks and responsibilities. Additional review, recovery, and confirmation states are marked as proposals.
The approach
Learn the system before drawing the screens.
The work began with knowledge transfer, stakeholder alignment, and understanding Avionté’s front-office and back-office processes. Validation and design iterations then informed the portal structure and screen flows.
- Week 1
Learn & plan
Knowledge transfer, project planning, and scheduling future sessions.
- Week 2
Validate concepts
Concept validation and brainstorming.
- Week 3
Address the structure
Card sorting, ideation, and workflow diagrams.
- Week 4
Develop screens
Low-to-medium fidelity wireframes and workflow iterations.
- Week 5
Connect the flows
Prototype features and align visuals with the AviontéBOLD style guide.
- Week 6
Iterate & deliver
Phase 1 delivery followed by a second iteration with fixes.
Design within the integration boundaries
CHANGE Card and loyalty feeds depend on external APIs.
Marketplace products and cards are supplied through RFS.
Marketplace goods are delivered through the Blackhawk system partnered with RFS.
Front-office and back-office processes shape portal workflows.
Information architecture
Start with a shared portal structure.
Card sorting combined the navigation hierarchies of three previous portals. FigJam supported the sorting work, while visual wireframes helped communicate the resulting structure with stakeholders.
My Dashboard
- Home
- Loyalty Program
- Utilities
Timesheet
- Time Entry
- Report
CHANGE Card
- Activities
- Manage Account
- Statements
- Alerts
- Pay Bill
Pay History
- Pay Check
- eDocuments
Talent
- Profile
- Settings
- Talent test
- Logout
A separate sign-on decision for agencies
The product and development teams agreed on an SSO approach for agency access. The design work included SSO diagrams connecting Avionté Classic, AviontéBOLD, the payment portal, loyalty management, and the back end.
Account management
Control the card and its alerts.
Card status, self-service actions, and alert preferences share one workspace. The account summary stays visible while the cardholder manages these settings.
Manage account
Proposed mobile adaptation of the original desktop screen.
My CHANGE Card
Self Services
Alerts
571 455 0888 Verified
Alert settings applied immediately when you switch the button
Transfers
Keep recipients and transfer history together.
A recipient list sits beside completed transfers. Account and confirmation details appear inside the selected transaction, keeping context close to the action.
Transfers
Completed transfers remain available below the recipient list.
Proposed mobile adaptation of the original desktop screen.
Transfers
Add receiver
Choose the transfer method first.
The overlay presents Card to Card, Card to Bank, and Bank to Card before collecting recipient details. Giving the methods equal visual weight makes this first decision explicit.
Add receiver
Select how this recipient will receive money.
Proposed mobile adaptation of the original desktop screen.
Transfers
Card to Card transaction has no delay. Fastest
transaction method of all tree.
Card to Card transaction has no delay. Fastest
transaction method of all tree.
Card to Card transaction has no delay. Fastest
transaction method of all tree.
Pay Bill User Profile
Set up the bill-pay profile.
A two-column form groups identity, phone, and email settings. Email format choices and the Cancel / Next footer make the setup step explicit.
Pay Bill user profile
Proposed mobile adaptation of the original desktop screen.
Bill Pay
Set up your Bill Pay
User Profile
This profile only applies to your
Bill Pay service.
We’ll send your Pay Bill Alert to this email address. To update your email,
go to update email link.
Statements
Connect statements with spending context.
Statement periods and balance details occupy the main column. The month selector, spend analyzer, and comparison chart provide adjacent context.
Statements
Spending context appears after the selected statement.
Proposed mobile adaptation of the original desktop screen.
CHANGE Card Statements
Previous Balance: $4.00
Purchases: $0.00
Credits: $0.00
Debits: $0.00
Fees: $0.00
ATM Amount: $0.00#
Transactions: 0
New Balance: $4.00
Loyalty marketplace
Keep redemption connected to the card.
The marketplace targets talent with an activated CHANGE Card and encourages card usage. At checkout, the card can cover the difference when the rewards cost exceeds the available points.
Review your basket
Use your CHANGE Card for the remaining $43.88.
Proposed mobile adaptation of the original desktop screen.
Basket
Summary
Pay difference with
Make the shortfall explicit
The checkout separates available points, the points subtotal, the shortfall, its dollar equivalent, and the remaining amount due.
Carry the account context through
The card balance and loyalty points remain in the shared sidebar, while the card payment choice appears next to the order summary.
Agency operations
The agency experience needed its own workflows.
Agency work covered cardholder search, account detail, replacement, inventory and automatic reordering, alongside loyalty enrollment, reward configuration, point purchases, and points history. Agency and branch administration wireframes made those operational tasks visible.

Complete the workflows
From the first step to the next clear state.
Six workflow branches connect portal entry, card management, transfers, bill-pay setup, rewards, and agency operations. Mobile and desktop views explore the same decisions across devices; additional states are marked as proposals.
Financial-provider rules, fees, settlement, permissions, and fulfilment behavior need confirmation against the production integrations. The screens illustrate the design questions without simulating real transactions.
Enter the right workspace
A connected entry experience helps people reach the correct talent or agency workspace. These proposed entry and recovery states make account context and access explicit.
Explore the main task and its alternative or recovery states. These screens are not all sequential steps.
Portal entry
Sign in to reach your talent or agency workspace.
Recognize the account and preserve the intended destination.
Choose workspace
Separate personal account tasks from operational permissions.
Talent overview
Establish shared balance and navigation context before starting a task.
Agency overview
The agency overview exposes operational tasks separately from talent self-service.
Sign-in needs attention
We could not sign you in. Check your details or recover access to your account.
Keep error handling specific enough to recover and appropriate to the authentication system.
Access needs attention
Your session has expired. Sign in again to return to this workspace.
Restore access without presenting financial data before authentication.
Portal entry
Sign in to reach your talent or agency workspace.
Recognize the account and preserve the intended destination.
Choose workspace
Separate personal account tasks from operational permissions.
Talent overview
Establish shared balance and navigation context before starting a task.
Agency overview
The agency overview exposes operational tasks separately from talent self-service.
Sign-in needs attention
We could not sign you in. Check your details or recover access to your account.
Keep error handling specific enough to recover and appropriate to the authentication system.
Access needs attention
Your session has expired. Sign in again to return to this workspace.
Restore access without presenting financial data before authentication.
Manage card security and alerts
Card status, lost/stolen reporting, PIN, disputes, and alerts belong together. Proposed review and result states make consequential changes understandable.
Explore the main task and its alternative or recovery states. These screens are not all sequential steps.
Card controls
Keep status, card identity, and related actions visible together.
Deactivate this card?
Review the card below before changing its status. Choose Keep active to return without making a change.
A consequential status change deserves confirmation; exact provider behavior needs verification.
Card state updated
Your card status is now inactive. Return to card controls to manage the card or report it lost or stolen.
Close the loop and show how the user can manage the state next.
Report lost or stolen
Tell us what happened to this card. Review the report and replacement details before confirming.
The original lost/stolen action needs a clear reporting and protection path.
Report request received
Your report has been received. Review the card status and follow the replacement request for the next update.
Separate reporting, status changes, and replacement fulfilment.
Choose alert preferences
Alert changes apply immediately. Check each preference before leaving this screen.
Distinguish immediate preference changes from a reviewed card-status action.
Card controls
Keep status, card identity, and related actions visible together.
Deactivate this card?
Review the card below before changing its status. Choose Keep active to return without making a change.
A consequential status change deserves confirmation; exact provider behavior needs verification.
Card state updated
Your card status is now inactive. Return to card controls to manage the card or report it lost or stolen.
Close the loop and show how the user can manage the state next.
Report lost or stolen
Tell us what happened to this card. Review the report and replacement details before confirming.
The original lost/stolen action needs a clear reporting and protection path.
Report request received
Your report has been received. Review the card status and follow the replacement request for the next update.
Separate reporting, status changes, and replacement fulfilment.
Choose alert preferences
Alert changes apply immediately. Check each preference before leaving this screen.
Distinguish immediate preference changes from a reviewed card-status action.
Add a recipient and send money
Sending money connects recipient selection, transfer details, review, and history. The proposed flow distinguishes submission, completion, and recovery.
Explore the main task and its alternative or recovery states. These screens are not all sequential steps.
Choose a recipient
Keep existing recipients reachable before asking for new details.
Recipient and amount
Show a focused entry step; account validation rules remain provider-dependent.
Review transfer
Verify the recipient and amount before sending.
Do not imply a zero fee or immediate settlement without provider confirmation.
Transfer submitted
Your transfer has been submitted and is waiting for confirmation. You can follow its status in transfer history.
A pending state avoids showing a payment as complete before settlement.
Transfer completed
Your transfer to Pam Ruprecht is complete. Open the transfer details to review the confirmation.
The completed result links back to the history pattern in the original screen.
Transfer details need attention
We could not accept these transfer details. Check the recipient and amount before continuing.
Recover before submission without losing the selected recipient.
Choose a recipient
Keep existing recipients reachable before asking for new details.
Recipient and amount
Show a focused entry step; account validation rules remain provider-dependent.
Review transfer
Verify the recipient and amount before sending.
Do not imply a zero fee or immediate settlement without provider confirmation.
Transfer submitted
Your transfer has been submitted and is waiting for confirmation. You can follow its status in transfer history.
A pending state avoids showing a payment as complete before settlement.
Transfer completed
Your transfer to Pam Ruprecht is complete. Open the transfer details to review the confirmation.
The completed result links back to the history pattern in the original screen.
Transfer details need attention
We could not accept these transfer details. Check the recipient and amount before continuing.
Recover before submission without losing the selected recipient.
Set up a bill-pay profile
Bill-pay setup groups identity, contact details, email updates, and alert preferences. Proposed review and validation states help people finish setup with confidence.
Explore the main task and its alternative or recovery states. These screens are not all sequential steps.
Profile details
Collect identity and contact information inside a focused setup task.
Email and notifications
Keep an email update distinct from choosing the message format.
Review profile
Review the contact details before continuing into bill pay.
Let the user check the information that future bill-pay communication relies on.
Profile setup complete
Your profile is ready. Continue to Bill Pay or review your contact information.
Close profile setup without implying that a bill has been paid.
Correct a required field
Use the required format. Keep the other profile values in place.
Recover locally instead of clearing a partly completed setup form.
Profile details
Collect identity and contact information inside a focused setup task.
Email and notifications
Keep an email update distinct from choosing the message format.
Review profile
Review the contact details before continuing into bill pay.
Let the user check the information that future bill-pay communication relies on.
Profile setup complete
Your profile is ready. Continue to Bill Pay or review your contact information.
Close profile setup without implying that a bill has been paid.
Correct a required field
Use the required format. Keep the other profile values in place.
Recover locally instead of clearing a partly completed setup form.
Redeem points and understand the shortfall
Rewards browsing leads to a checkout that shows the points shortfall and its card-payment equivalent. Proposed order states connect that decision to confirmation and history.
Explore the main task and its alternative or recovery states. These screens are not all sequential steps.
Browse rewards
Keep points visible while exploring the reward catalogue.
Choose a reward
Make the quantity’s effect on the redemption cost visible.
Review the difference
Explain the shortfall and payment choice next to the order summary.
Order confirmed
Your order is confirmed. Open purchase history to review the payment and follow its delivery status.
Link confirmation to history and distinguish order placement from fulfilment.
Review purchase history
Open an order to review its points, card payment, and latest status.
Make redemption traceable without assuming when either balance updates.
Order needs attention
Your basket is still here. Review your payment details before trying again.
Do not silently consume points or imply success when the provider has not confirmed the order.
Browse rewards
Keep points visible while exploring the reward catalogue.
Choose a reward
Make the quantity’s effect on the redemption cost visible.
Review the difference
Explain the shortfall and payment choice next to the order summary.
Order confirmed
Your order is confirmed. Open purchase history to review the payment and follow its delivery status.
Link confirmation to history and distinguish order placement from fulfilment.
Review purchase history
Open an order to review its points, card payment, and latest status.
Make redemption traceable without assuming when either balance updates.
Order needs attention
Your basket is still here. Review your payment details before trying again.
Do not silently consume points or imply success when the provider has not confirmed the order.
Operate within the right agency and branch
Agency operations connect cardholder search, account details, transactions, replacement, inventory, and loyalty management. Proposed states keep the selected person and branch visible through each action.
Explore the main task and its alternative or recovery states. These screens are not all sequential steps.
Choose operational scope
Make operational scope explicit before revealing or changing cardholder data.
Find the cardholder
Provide enough identifying context to distinguish similar results.
Review a card action
Check the cardholder, branch, and requested replacement before confirming.
A staff action must stay tied to the selected person and branch.
Request status
The request is recorded for this cardholder. Review its status in account details.
Distinguish a recorded request from completion and keep related operational tasks accessible.
Inventory and reorder
Inventory and reorder decisions need clear branch context, thresholds, and request status.
Loyalty administration
Keep enrollment, rewards, point purchases, and history reachable from the loyalty workspace.
Choose operational scope
Make operational scope explicit before revealing or changing cardholder data.
Find the cardholder
Provide enough identifying context to distinguish similar results.
Review a card action
Check the cardholder, branch, and requested replacement before confirming.
A staff action must stay tied to the selected person and branch.
Request status
The request is recorded for this cardholder. Review its status in account details.
Distinguish a recorded request from completion and keep related operational tasks accessible.
Inventory and reorder
Inventory and reorder decisions need clear branch context, thresholds, and request status.
Loyalty administration
Keep enrollment, rewards, point purchases, and history reachable from the loyalty workspace.
Questions to resolve before validating these flows
- Which identity and access states apply to talent, agency, and branch accounts?
- What changes when a card is inactive, and how are replacement and disputes handled?
- Which transfer methods, fees, timing, and failure responses do the providers support?
- How are points reserved, payment shortfalls authorized, and orders confirmed?
- Which branch permissions, inventory rules, and request states need to be exposed?
Delivery & evidence
Two delivery phases, with an iteration between them.
The design work was delivered in two phases. Phase 1 met the client’s expectations; a second iteration incorporated fixes before Phase 2 delivery.
Design outputs
Portal structure, SSO diagrams, workflow diagrams, low-to-medium fidelity wireframes, screen flows, and interactive prototypes aligned with the AviontéBOLD style guide.
Delivery scope
The six-week engagement connected stakeholder feedback with portal structure, workflows, wireframes, and prototypes. Two delivery phases provided room to refine the design and address fixes.
Design development
Explore the planning, card sorting, workflows, wireframes, marketplace, and agency prototype that supported the connected experience.












