Making insurance renewal
actually happen.

Renewal existed in the app. Almost no one used it. We built a flow that actually worked.

48% 95% In-app renewals
<12% 40% Early renewals
Role
Product Designer · End-to-end
Team
1 PM · 3 Engineers · Ops
Timeline
~8 weeks
Scope
Renewal experience — start to finish
Constraints
No existing flow · Ops was the default · Low user trust · Tight engineering scope
Outcome
Built from zero. Ops became the backup.
The Situation

There was no renewal flow.
We built one.

Renewal existed in the app — but not really. Users who needed to renew called support. An agent walked them through it over the phone. No in-app flow, no deadline visibility, no clear path forward.

48% App renewals — mostly ops-assisted
<12% Used any in-app flow at all
85% Waited until the last month (R11)
What users actually needed

"The job wasn't 'renew policy'.
It was: help me avoid lapse
without making a mistake."

Research

What we learned
from users.

20 interviews, ops shadowing, funnel analysis. The problem wasn't behaviour — it was the product.

User Interviews 20 participants · phone + Zoom
Ops Shadowing Observed real renewal calls
Journey Audit End-to-end flow mapping
Funnel Analysis Drop-off points identified
Stakeholder Sessions PM · Engineering · Ops
  • Trust Gap

    Users called ops because the app never gave them a reason to trust it. Ops felt safer than a UI they'd never needed to rely on.

  • Buried Entry

    The renewal entry point required 3 taps to find. Most users only discovered it when ops told them where to look.

  • No Urgency

    85% waited until R11. The system created no deadline visibility and no cost to waiting. So users waited.

  • Broken Flow

    Ops had become the default renewal channel. The app wasn't competing with ops — it had already lost.

Exploration

Four directions.
One worked.

Variant 1 — information-first design direction
Variant 01

Information-first

Tried showing more details upfront.
Users ignored them and still didn't renew.

Variant 2 — progressive disclosure design direction
Variant 02

Step-by-step reveal

Tried revealing information progressively to reduce anxiety.
More screens meant more drop-off. Didn't build trust.

Variant 3 — nudge-forward design direction
Variant 03

Nudge-first

Tried pushing users to renew earlier.
You can't nudge people into a flow that doesn't work.

Selected ✓ Variant 4 — clarity-first selected direction
Variant 04

Clarity-first

One screen. Clear status. Minimal steps.
Fastest to complete. Easiest to build. Clearest for users.

Reviewed with PM and engineering. V4 was the only direction all three could commit to.

Solution

What we built.

Visible

Surfaces 45 days before expiry

Understandable

Clear policy details upfront

Complete

End-to-end inside the app

Supported

Comms that guide users in

Shipped flow — recorded from the live Navi app.

Before
  • No renewal flow in the app
  • Users called ops to renew
  • No deadline visibility
After
  • Renewal visible 45 days before expiry
  • Complete in under 2 minutes
  • No call needed
Final shipped design — the Navi health insurance renewal experience

Final shipped design — the renewal entry point inside the Navi app.

The simplified flow was also the easiest to build. Engineering sign-off came fast.

Key Decisions

What we chose.
And why.

Impact

The numbers
moved.

Before

48%

After

95%

+47pp In-app renewals
Before

<12%

After

40%

~3× growth Early renewals
  • Renewal became predictable — users knew what to expect
  • Users completed it alone, without calling anyone
  • Ops became the backup. Not the default.
What I Learned

Three things this
project taught me.

  • Insight 01

    In financial products, the interface has to feel safe before users will act in it.

  • Insight 02

    Progressive disclosure slows people down when they just want to get something done.

  • Insight 03

    Skipping the nudge layer at launch was the right call. Real data beats assumptions every time.

"When the app works, users don't call.
They just renew."

Let's connect

Open to what
comes next.

Genuinely curious about your story too.

Start a conversation  →