← All work
03 / Fleet payments onboarding

Making the first
steps clearer.

Evaluating how fleet managers discover help, interpret instructions and complete first-time setup.

My contributionUX Researcher · B2B payments
ScopeOnboarding web experience
ApproachModerated prototype evaluation
Fleet dashboard and onboarding checklist; edited to remove branding
The dashboard and first-use guidance evaluated with fleet managers.Project screenshot edited to remove branding; some interface details may differ from the source.View full size ↗
Research in numbers

Five sessions exposed a discoverability gap.

5Fleet managers
60 minPer session
5 hrsScheduled session time

Checklist discovery before prompting

Found independently0
Did not find independently5
0Participant count5
0 / 5

Found the checklist on their own.

Participants valued the guidance once introduced. The priority was to make it visible at the point of need.

Source: onboarding usability report, five moderated sessions. Five hours is calculated from five scheduled 60-minute sessions. This small study does not estimate population-wide behaviour.

01 / Study

Useful guidance must
first be discovered.

Five experienced fleet managers took part in 60-minute, face-to-face prototype sessions.

Before prompting

Checklist missed

Participants noticed cards and balance information, but did not find the checklist on their own.

After introduction

Guidance valued

Participants understood the checklist and wanted it available for future use and staff handovers.

Key insight

Availability is not discoverability.

Place help where users expect it and keep it accessible after first-time onboarding.

02 / Journey

The sequence conflicted
with existing expectations.

Fleet managers brought habits from physical-card workflows to a new digital service.

Tested sequence · friction observed
  1. 01Top up

    Fund the account first.

  2. 02Create card

    Set up the card afterwards.

Recommended sequence · not yet validated
  1. 01Create card

    Establish the card.

  2. 02Set restrictions

    Configure its intended use.

  3. 03Top up

    Add funds.

The proposed ordering required further usability testing. It is not presented as a shipped or validated replacement.

03 / Recommendations

Clarify the action,
the state and the meaning.

My research contribution focused on evaluating the prototype and translating observed behaviour into recommendations.

What we observedDesign response

Completed steps looked unfinished

Users thought they needed to create another account.

Recommendation

Make completion unmistakable

Differentiate finished steps from actions still required.

Images looked interactive

Users tried clicking controls inside guidance images.

Recommendation

Distinguish guidance from controls

Show where the real action begins.

Wallet linking went unnoticed

Verification felt familiar; the linked wallet later caused confusion.

Recommendation

Explain the service connection

Clarify what is being linked before reaching payment.

Fields left room for assumptions

Users were unsure whose phone number to provide.

Recommendation

Use role-specific labels

Specify driver details and identify optional fields.

04 / Outcome

A clearer path to
independent onboarding.

The study connected support-team observations with real first-use behaviour.

What the work established

Focused changes to test

Improve checklist placement, preserve access to help, clarify labels and re-evaluate the task sequence.

Evidence boundary

No measured activation uplift

The study identifies usability issues. It does not quantify increased top-ups, card creation or reduced support demand.

Edited project screenshots accompany generalised diagrams of the research and design reasoning. Visuals do not imply measured production outcomes. Work was delivered collaboratively.

Continue the conversation

Let’s talk about the thinking
behind the work.

Get in touch ↗