Due to a non-disclosure agreement, information on this project and its outcome is limited.

Fiserv

A task that took 15–19 minutes now takes under 2. Unifying the credit limit management

  • SHIPPED
  • CARD & ACCOUNT LIMIT MANAGEMENT
  • B2B
  • WEB APP

TL;DR

FirstVision™ is the web interface for VisionPLUS®, the COBOL system Fiserv runs in Latin America. Limit management lived in both, and the FirstVision version was missing functions. I led the redesign from discovery to hand-off and brought 150+ fields into one feature. A task that took support teams 15–19 minutes now takes 1.5.

ROLE
UX Designer. Led the design process from discovery to hand-off.
TEAM
2 Product Managers
2 UX Designers (me + 1 who joined for deliverables)
1 Sr. Product Designer (supervising)
1 UX Researcher
1 UX Writer
2 Lead Engineers
+10 Software Engineers
TIMELINE
Sep 2023 → Nov 2023
COMPANY
Fiserv
BRAND
FirstVision™
TOOLS
Figma, FigJam, Google Workspace, Notion & Discord

Before

VisionPLUS terminal screen with authorization statistics for a card account
Limit management in VisionPLUS, the COBOL system.
FirstVision MVP account screen with credit limit management in small tables
The FirstVision MVP, missing several functions.

After

New Limit Management feature in FirstVision with credit limit and overlimit balances
One feature with all 150+ fields. Example data.

The same questions I asked got better answers when collaborating

Product and engineering worked from documents, so I started with one. It framed the problem but did not show how to group 150+ fields. The same questions, asked in a FigJam session, did. The map below shows each step and who led it.

Steps with a lock cannot be shown or shared.

  1. Discovery

    • High-level requirements

      Led by me

    • Is, isn’t, does, doesn’t Locked

      Led by me

    • Personas Locked

      Used to design the key flows
      and edge cases

  2. Definition

    • Card sorting

      Led by me, with product, dev, design & engineering.

    • User scenarios

      By me

    • User flow Locked

      By me

  3. Design

    • Internal benchmarking Locked

      Me and a colleague

    • Mid-fidelity prototype

      I led the design of the key flow and onboarded a colleague

    • Design & product Q&A Locked

      Led by me

  4. Validation & iteration

    • Usability test Locked

      UXR-led. I built the prototype and drafted the test script

    • Data analysis & report Locked

      UXR-led

    • Adjustments & final design

      By me

The doc framed the problem.
It did not group the fields.

The high-level requirements asked the team: the problem, the situations where the feature is used, what stays out of scope. The session around the doc had little energy, and it did not show how to group the fields.

High-level requirements document for credit limit, with a feature summary table
The high-level requirements doc, with names and internal IDs anonymized.

In FigJam, the group sorted
the fields into categories

So I kept the questions and moved them to a FigJam board. In one session I facilitated, product, development, design and engineering sorted the fields into categories. That grouping became the structure of the feature: account limits and card limits, with the fields in each one grouped by category.

Information is limited.

The resulting grouping, illustrated.

Four tasks guided the design,
then the test

I wrote one user scenario for each main task and used them twice: to generate design alternatives after the card sorting, and to build the usability test.

  • Check available limit

    Ensuring clarity and ease of access for locating information on available and utilized credit limits.

  • Locating and editing the temporary limit

    Identifying and understanding the temporary limit panel and its edit function is essential for effective limit management.

  • Checking and enabling international
    limit for purchases

    Identifying the credit limit details area, including the dedicated limits, and clarity in the international limit.

  • Identifying overlimit-related
    charges on the screen

    Locating and understanding the account overview block and identifying the overlimit status.

Checking a limit was easy.
Overlimit was not

The UX researcher ran the test in September 2023. Five Fiserv support agents did four tasks and answered the ASQ after each one. All five checked the available limit (4.9 out of 5). Overlimit was the hardest: two could not finish (3.3 out of 5).

The report closed with six recommendations: rework the overlimit tag, remove repeated information, rethink the edit button, revisit the temporary limit block, give access to the transaction list, and confirm every edit.

Balances first, details one click away

Limit management opens on Account Limits: two bars for the credit limit and overlimit balances, and tabs that split the details by category.

Account Limits tab with the Temporary limit button, credit limit and overlimit balance bars, and Cash, Installments, Loan and International tabs
Account Limits, with example data.
  • 1

    Add temporary limit

    Participants missed a clear way to add/edit the temporary limit. So a dedicated button was placed at the top of the page.

    Usability test recommendation

  • 2

    Edit limits

    Test participants were unsure which limit the pencil belonged to, so each block has its own edit icon, next to its last update date.

    Usability test recommendation

3

Overlimit, on demand

Shows a red tag and a red balance bar. Details stay behind an arrow, so the screen only grows when needed. A participant suggested this.

Usability test recommendation

Credit Limit Overview with a red Overlimit tag, red balance bars and a collapsed details arrow
Overlimit status, collapsed.
4

Overlimit details, with links

Shows the fee status and start date, with links to Statements and Fee Details. In the overlimit task, four of five participants asked for the transaction list.

Usability test recommendation

Overlimit details expanded, with the fee status, start date and links to Statements and Fee Details
Overlimit status, expanded.

Guided fields, confirmed changes

Editing opens in a modal over the same screen, one limit at a time.
Each field states what is allowed before the agent submits.

Edit Cash Limit modal with a Cash Availability dropdown, a Cash Limit field with its allowed range, and a Notes field
Edit Cash Limit, with example data.
  • N - No limit available
  • T - Total account limit
  • Y - Fixed amount
5

Availability options

A dropdown sets the type, and the amount field sits beside it, with the allowed range below. In the test, a participant editing the international limit found the options confusing and wanted to type a value.

Usability test recommendation

The form adapts to the option chosen

Fields that do not apply are disabled and fill themselves in. The ones that do apply open for input and show the allowed range.

Not editable

No limit available: Cash Limit is disabled and shows R$ 0,00.

Not editable

Total account limit: Cash Limit is disabled and shows the account limit.

Editable

Fixed amount: Cash Limit opens for the amount, with the allowed range below.

A confirmation names the limit being changed

Each modal names the limit about to change, to prevent mistakes.

Usability test recommendation

  • Confirmation for the account credit limit.

  • Confirmation for the cash limit.

Its own block, its own status

A customer is traveling and needs extra limit for a set period. For that, the temporary limit has its own block on Account Limits.

Temporary Limit Balance block with an Active tag and expiration date, above a faded Credit Limit Overview tagged Temporary Limit in Effect
A temporary limit in effect, with example data.
  • 6

    Temporary limit indicator

    Participants read the old panel as a limit to activate, not one already set. So I decided to create a new block, with a status tag, the expiration date, and edit and remove actions.

    Usability test recommendation

  • 7

    Temporary limit in effect

    A blue tag next to the Credit Limit Overview title shows when a temporary limit is active.

    Usability test recommendation

  • 8

    Credit limit overview

    While a temporary limit is active, the Credit Limit Overview fades, so the agent always knows which limit is in force.

    Usability test recommendation

Pick a card, then read or edit its limits

Card Limits is the second tab. Specific limits per card start switched off. Once a toggle turns them on, the agent picks a card and sees its limits by transaction type.

Card Limits tab switched on, with a carousel of cards and a table of limits by transaction type
Card Limits, switched on, with example data.
  • 9

    Navigation by cards

    A carousel holds the account's virtual, physical and additional cards. Picking one keeps the agent on the same screen, and the table below shows that card's limits.

  • 10

    Limits by transaction type

    The table lists each limit by transaction type. Frequency sets the period it covers.

The new design process
after the project

Limit management was the test for a new design process: working sessions instead of documents to read. It became part of Fiserv's design process in Latin America, for feature development and large redesigns. The team's estimates, before and after:

These are estimates, not measurements.

  • Kickoff meetings: 2 hours → 1 hour
  • Design: 6–8 weeks → 3–4 weeks
  • Ready for dev: 4 sprints → 2 sprints
  • A document frames the problem.
    A shared activity answers it

    One named the problem, the other grouped the fields. When the goal is to decide something together, I now choose a shared activity over a document to read.

  • Test with the people
    who live the task

    The participants were Fiserv support staff. The report notes they lacked the day-to-day context of end users, which may explain the wish for a transaction list and the doubts about the international limit.

  • Card limits and the
    final screens still need a test

    Card limits were not tested, and the final design was not tested again. The next step is the one the report recommends: a retest with end users.

Owning the seller experience of a delivery platform across LATAM & South Africa

2 SaaS tools became 1 platform where store managers receive orders and run daily operations, now live in 13 countries.

Read case

Delivering by suburb, not postcode: 20K+ new orders in Australia

One question after the postcode let customers in reach finally order, and almost ended boxes that could never arrive.

Read case