BTG Pactual · Banking · 2020

Modular card insurance in a banking app

Modular card insurance in the BTG+ banking app: customers choose their cover instead of buying a fixed bundle. I designed it and tested where to sell it; in the card request it put sign-ups at risk, so it sits in the card's settings.

Role
Senior Product Designer
For
BTG+ card customers
What I did
  • Survey
  • Benchmark
  • Flows
  • Prototyping
  • Usability testing
The case as one flow: cover level and assistances, the module, bundle or modules, modules and a fixed bundle
  1. Cover level and assistances
  2. Module
  3. Bundle or modules
  4. Modules and fixed bundle

01

What customers wanted

BTG Pactual was entering retail banking. I surveyed 30 customers: 90% had card insurance, 65% disliked at least one assistance in their package (a service such as home repairs), and 80% wanted to choose the parts.

In a fixed bundle, the limits are buried in policy clauses. Customers can't compare the parts or drop the ones they don't want.

Survey of 30 customers: 90% already had card insurance, 65% were unhappy with at least one assistance, 80% wanted to choose the benefits. Below, modules compared with a fixed bundle

02

The limits

The insurer, Too Seguros, set the cover, prices and claim rules, and regulated terms can't be reworded. So clarity had to come from layout: each limit next to the price. And card conversion was the retail business's key metric, so anything added to the card request put it at risk.

03

The design

With the PM, tech lead and developers, I agreed three principles first: simplicity, personalisation, transparency. Later disagreements were settled against them.

I reviewed seven insurers; three shaped the structure: Cuvva (the price updates as cover changes), Wrisk (a policy built one question at a time) and Lemonade (plain language). The customer picks one of three plans, then one free assistance: pet, repairs, home, emergency services or bike.

  1. Pick one free assistance
  2. Confirm the details
  3. Done

I designed all three flows: buying, claiming and cancelling. The claim is when customers learn if the insurance works.

Three flows: buying, claim and cancelling, step by step

04

The test

I tested both placements, in the card request and in the card's settings, with 10 customers. In the request, insurance made a crowded sign-up longer and mixed free and paid products in one checkout.

Two placements tested: inside the card request, and after the card is approved

So we moved it. Once the card is approved, insurance appears as a pending task, with a permanent place in the card's settings.

  1. Open the card menu
  2. Tap Seguro do cartão
  3. The insurance page opens

Customers were slow to notice the price change between plans, so the price and limits now update in place.

  1. Switch to Pleno
  2. Switch to Superior

05

What I learned

Test where a feature sits, not only its screens

The screens worked in both places; the placement was the decision.

In regulated products, clarity comes from layout

The wording can't change, so what sits beside the price has to explain it.

Agree principles early

They let me argue for the move with rules engineering had already signed.

06

What this case doesn't cover

  • Results after launch. I left before they were measurable.
  • Prices. They were set by the insurer; the ones in the figures are placeholders.
  • Accessibility. No review was run.

Next case

06 / 07