08 / Selected workMobility · Onboarding and growth

Flexar

Onboarding looked healthy. Activation did not.

Seventy-three per cent of people completed onboarding, but only 10% reached a first rental. I reframed the problem around activation and redesigned onboarding as three independent blocks that can be moved, combined and tested without rebuilding the flow.

Product DesignUX ResearchProduct Strategy
My role
Lead Product Designer — funnel analysis, problem framing, onboarding architecture, interaction design and experiment planning
Scope
In build · experiment-led
Focus
Onboarding · Growth · Experimentation
Evidence status
The redesign is in build, so no conversion uplift is claimed. Funnel data covers 15 April–12 May; the partly overlapping KYC session data covers 29 April–22 May. The two systems disagree on the exact verification loss, which remains a measurement issue to resolve.
Before-and-after Flexar onboarding model showing one sequential gate replaced by sign-up, reservation verification and rental payment blocks
Baseline and experiment plan
10%accounts reached a first rental
3 → 2gates before first value
3independent onboarding blocks
01 · Project overview

My role, the team and how success was defined

A short project brief before the detailed story: the setting, my responsibility, the people involved and the outcome we were working towards.

01Product context
A mobility onboarding flow with 73% completion appeared healthy until the funnel was extended to first rental, where conversion fell to 10%.
02My ownership
I analysed the account-to-rental funnel, reframed the success measure, defined the block architecture, designed the proposed flow and set the experiment and guardrail metrics.
03Core collaborators
The source presents the work as a product-and-engineering replatforming in build; it does not name individual contributors or assign them specific ownership.
04Success definition
Increase account-to-first-rental conversion above the 10% baseline without reducing the verified-account rate or simply moving the drop-off to a later stage.
02 · Problem

What was happening—and why it mattered

Flexar collected account details, payment and Singpass verification before customers had received any value. The visible onboarding funnel looked healthy, but extending it to first rental showed that 90% of created accounts never drove. The design needed to protect the 73% completion baseline while moving costly steps closer to the value they unlocked.

  • 17,974 people created an account, but only 1,840 reached a first rental.
  • Payment before any product value accounted for a 22% drop, and 98% of those exits recorded no failure event.
  • Singpass represented a smaller 6% loss, with many cases linked to existing accounts or incomplete sessions rather than true rejection.
  • The largest gap came after verification: 11,240 people completed every gate and still did not book.

Onboarding should not be the toll gate. It should be the on-ramp.

03 · Discovery evidence

Evidence that changed how I understood the problem

Behavioural, operational and qualitative evidence did different jobs. Together, they helped define what the team needed to solve before choosing a direction.

01Account-to-rental funnel

17,974 accounts became 14,042 payment methods, 13,080 Singpass validations and 1,840 first rentals. The largest opportunity sat after onboarding, not inside it.

Design implication

First rental—not onboarding completion—needed to become the primary success measure.

02Payment behaviour and usability

Payment before value produced a 22% loss; 98% of those exits had no recorded failure. In the cited usability study, all four participants objected to payment during onboarding and chose the freemium route.

Design implication

Payment should be requested when the customer is ready to rent, not when they are only trying to enter the product.

03KYC rejection and session data

The most common rejection reasons included existing identity or verified-account collisions. The KYC log counted 480 affected sessions while analytics reported 962 dropped users.

Design implication

Account recovery and instrumentation needed attention before treating the entire 6% as a verification-design problem.

04 · Service system

What customers saw depended on what happened behind it

The blueprint connects the customer journey, product behaviour and operational responsibilities across the same sequence.

StageCustomerFrontstageBackstage
1 · Sign up

Creates an account with minimal information and enters the product.

Sign-up is the only unconditional onboarding block.

The account is created without collecting payment or completing KYC.

2 · Explore

Browses vehicles and understands the service before making a commitment.

The home and vehicle views provide value immediately after sign-up.

Incomplete setup remains visible as resumable tasks rather than a locked funnel.

3 · Reserve

Chooses a vehicle and signals clear intent to use the service.

Singpass verification appears as the short step that unlocks reservation.

Identity and licence checks remain mandatory, but their placement is configurable.

4 · Prepare to rent

Returns to the active reservation and prepares to start the rental.

Progress shows what is complete and what remains before driving.

The system preserves reservation and setup state if the customer pauses.

5 · Rent

Adds payment at the moment of highest intent and starts driving.

Payment is explained as the requirement that unlocks the rental.

Payment and verification completion remain guardrails for starting the vehicle.

Scroll horizontally on smaller screens to follow the complete service.

05 · Decision trail

The choices that shaped the work

The artefacts mattered when they helped the team choose. These are the questions, evidence and decisions behind the final direction.

01
Question

What should the funnel optimise?

Evidence

Onboarding completion was 73%, but account-to-first-rental conversion was only 10%.

Decision

Use first rental as the primary outcome and treat onboarding completion as a supporting measure.

02
Question

When should payment and Singpass appear?

Evidence

Payment created a 22% pre-value loss, while verification and payment were still mandatory before reservation and rental could be completed.

Decision

Place Singpass at Reserve and payment at Rent so each requirement sits beside the value it unlocks.

03
Question

Reorder the existing screens or change the architecture?

Evidence

A fixed sequence would make each new variant another redesign and risk a baseline that already worked for 73% of users.

Decision

Build three independent blocks whose order and placement can be changed through configuration and tested separately.

06 · Two connected lenses

One problem, viewed through service and product

The operating service and the interface formed one system. Each lens addressed a different part of the same problem.

Service Design

Shaping the ecosystem, hand-offs and operating model.

  • Extended the journey from account creation to first rental instead of stopping at onboarding completion
  • Placed Singpass at reservation and payment at rental, where each requirement has an understandable purpose
  • Made deferred tasks resumable so customers can explore before completing every requirement
  • Separated registration from account recovery after identity-collision data exposed a service gap

Product Design

Turning service decisions into clear, usable product behaviour.

  • Replaced one fixed funnel with independent Sign up, Singpass and Payment blocks
  • Kept sign-up as the only unconditional entry cost
  • Used visible progress and clear next actions to make unfinished setup recoverable
  • Made block order and placement configurable for controlled experiments
07 · Process

How the work moved from uncertainty to a decision

01

Extend the funnel to the outcome that mattered

The analysis followed customers from account creation through payment and Singpass to first rental. That extra step changed the problem: the 73% onboarding rate hid a 10% activation rate.

02

Separate refusal, rejection and the unknown

Payment exits were mostly voluntary, Singpass losses included identity collisions and incomplete sessions, and the 61-point post-verification gap had no confirmed explanation. I kept those causes separate instead of treating every exit as onboarding friction.

03

Attach each requirement to a value moment

Sign-up became the entry block, Singpass the requirement to reserve and payment the requirement to rent. The sequence preserved compliance while giving each ask a clearer reason.

04

Design for deferral and return

Progress, resumable tasks and product-led re-entry points allowed customers to pause without being stranded mid-funnel.

05

Define the experiment before claiming success

The plan measures account-to-first-rental conversion, recovery of the 22% payment loss and return-to-complete behaviour, with verified-account rate as the guardrail.

08 · Constraints and trade-offs

The constraints that shaped the work

These constraints affected the direction, the order of work and the compromises made with the wider team.

01

Deferral did not remove mandatory steps

The tension

Customers still need identity verification and a payment method before driving.

My response

The design moved each requirement to the point where it unlocked a clear action rather than presenting deferral as removal.

02

Friction moved into higher-intent moments

The tension

Some customers will now encounter verification during reservation rather than before entering the product.

My response

I accepted that cost because the customer has clearer intent and a concrete reason to finish, while keeping the block short and resumable.

03

The measurement systems disagreed

The tension

The KYC log counted 480 affected sessions while product analytics reported 962 dropped users over partly overlapping periods.

My response

The 6% remains directional, and instrumentation repair is part of the work before optimising against a more precise number.

04

The largest loss remained unexplained

The tension

The funnel showed that 11,240 verified accounts did not book, but it did not explain why.

My response

I kept this as the next research question instead of implying that an onboarding redesign would solve the full activation problem.

09 · Evidence

What the evidence shows

17,974accounts created
14,042payment methods added
13,080Singpass validations
1,840accounts reached first rental
22%loss at payment before value
61 ptsverified accounts lost before rental

The main funnel covers 15 April–12 May. The KYC session data covers 29 April–22 May and reports 480 affected sessions where analytics reports 962 dropped users, so the verification loss is useful directionally but not precise. The redesign is in build and no uplift is claimed.

10 · Selected UI deliverables

A product journey that earns each commitment

The proposed experience lets customers enter with minimal input, see the service and complete the remaining requirements when they are trying to reserve or rent. These screens show the shift from one compulsory funnel to visible, resumable progress.

Flexar welcome screen introducing the car-sharing service with options to log in, sign up or continue later
01 · Sign up

Let people enter before asking for commitment

The entry screen explains the service and keeps sign-up lightweight. Payment and identity checks no longer sit between account creation and the first look at the product.

View full-size UI
Flexar map showing an active reservation and the action to start the rental
02 · Reserve

Attach verification to a clear intent

Reservation is the first value moment. Singpass is positioned as the short requirement that unlocks it, while the active reservation keeps the customer oriented in the product.

View full-size UI
Flexar setup progress screen showing mobile, identity and payment steps completed before driving
03 · Rent

Make deferred setup visible and finishable

The checklist shows completed identity and payment requirements and gives the customer one clear route into driving. A paused task remains recoverable rather than becoming a dead end.

View full-size UI
11 · Outcome

What changed

01

Reframed the primary measure from onboarding completion to account-to-first-rental conversion.

02

Designed a block model that reduces gates before first value from three to two and removes payment from that early sequence.

03

Made Sign up, Singpass and Payment independently placeable and testable.

04

Defined conversion, recovery and verification guardrails for the build and experiment.

12 · Reflection

What I learned and would do next

Strongest contribution

The key contribution was changing both the success measure and the product architecture: from completing a fixed funnel to helping more created accounts reach a first rental through testable blocks.

What I learned

A healthy completion rate can hide the wrong boundary. The 73% looked strong only because the funnel ended before the behaviour the business and customer actually cared about.

What I would do next

I would investigate why the 61% of verified accounts never book, repair the KYC measurement gap and run the block-placement experiment with verified-account rate as the guardrail.

Next case study · BlueSG

Charger-less parking and clearer availability