Platform: Mobile AppIndustry: InsuranceCase Study

AMS/LMS

AMS/LMS home screen
01Quick Lead Creation

Short, fast registration

02Mobile-First Experience

Built for field agents

03All-in-One Agent Dashboard

Leads, tasks, attendance

01 • Project Overview

Project overview

AMS/LMS helps insurance Financial Advisors manage leads and daily activities.

I redesigned lead management, task tracking and attendance to make key actions faster and easier.

My roleUX/UI Designer
OrganizationPNB MetLife (Consultant)
PlatformMobile application
Primary usersFinancial Advisors (field agents)
ScopeDashboard and core agent workflows
ToolsFigma
02 • The Challenge

A long form was slowing down lead capture.

Registering one lead took about 10 minutes. At events, agents meet 10 to 15 prospects, so repeating a long form meant lost time and missed leads.

Agents also needed simple ways to find leads, track tasks and mark attendance.

~10 min

to register one lead

10-15

prospects met at one event

100+ min

of form filling for 10 leads

12345678910

10 leads x 10 minutes = 100 minutes of form filling

Goal: reduce friction in everyday work without losing essential information or verification.
03 • Research & Discovery

What was wrong with the old screen

I reviewed the existing screens and spoke with stakeholders. Here is what stood out on the old dashboard.

Existing UI and workflow reviewStakeholder discussions
Previous Summary dashboard
1
Two time tabsMTD and YTD split the view before agents see anything useful.
2
Greeting bubbleUses prime space but offers no action.
3
Tiny day plannerA cramped, cut-off timeline that is hard to scan.
4
Buried actionNew Activity hides in Quick Links, so creating a lead is not a primary action.
5
Counts onlyGreen tiles show numbers with no hierarchy or next step.
6
Repeating tilesThe same tile style keeps repeating, adding noise.
Also missing: an attendance check-in and a clear task list.

Key findings

01

Lengthy registration

About 10 minutes per lead, which adds up fast.

02

High-volume capture

10 to 15 prospects at one event multiply every extra step.

03

Workflow clutter

The dashboard and daily actions needed clearer order and easier access.

Research note. Findings come from the existing workflow review and project information. Formal user interviews, surveys and usability tests were not part of the confirmed research.
04 • User Persona

Meet the Financial Advisor

The primary user is a field-based advisor who meets prospects and runs daily operations through AMS/LMS.

FA

The Financial Advisor

Field-based agent, always on the move

Field agentEvent-heavy daysMobile first
10-15prospects at an event
~10 minto register one lead
★

Goals

  • Capture details fast
  • Verify mobile numbers
  • Manage leads and follow-ups
  • Finish tasks and attendance
!

Pain points

  • Long lead registration
  • Repeated data entry
  • Frequent actions hard to reach
✓

Needs

  • A short lead creation journey
  • Clear navigation and feedback
  • Quick access to leads, tasks and attendance
Design opportunity: help agents spend less effort on the system and more time with customers.

A provisional persona based on the known workflow and stakeholder context, not a validated research profile.

05 • Research Insight

Capture the essentials first.

How much does an agent need to enter at the very start? My answer: three fields, then verification.

Before

Everything upfront

A long form at the very first meeting.

→
After

Essentials first

Customer name
Mobile number
State
Verify mobile number→Lead created

Everything else comes later, when it is relevant.

06 • Card Sorting & Information Architecture

Pinning down the structure

Based on the interface review and stakeholder discussions, I grouped the product around what agents do.

01

Dashboard

  • Daily overview
  • Quick access to essential actions
02

Lead Management

  • Create a lead
  • View lead list
  • View lead details
  • Manage follow-ups
03

Task Management

  • View pending tasks
  • Review task details
  • Update task status
04

Attendance

  • Mark attendance
  • View attendance history
05

Profile

  • Manage account information
  • Access settings
A proposed information architecture. A formal card-sorting study with agents would be needed to confirm these categories match their mental models.
07 • User Flow

Simplifying the lead creation journey

Existing journey

  1. Open lead registration
  2. Complete extensive details
  3. Submit the form
  4. Repeat for the next prospect

The existing process took approximately 10 minutes per lead.

→

Redesigned journey

  1. Open the dashboard
  2. Select Create Lead
  3. Enter the customer's name, mobile number and state
  4. Submit the details
  5. Verify the mobile number using OTP
  6. Receive a successful lead creation confirmation
AMS/LMS lead step 1AMS/LMS lead step 2AMS/LMS lead step 3AMS/LMS lead step 4AMS/LMS lead step 5AMS/LMS lead step 6

See it in action

Tap a step to see the real screen.

  1. Basic details, no meeting yet
  2. Schedule the meeting
  3. Meeting day arrives
  4. Mark the meeting done
  5. Add customer information
  6. Choose the product plan

UX decisions

01

Reduce initial data entry

Limit the first interaction to essential details.

02

Retain verification

Use OTP to verify access to the entered mobile number.

03

Provide clear feedback

Confirm when the lead has been successfully created.

04

Support recovery

Design clear error and retry states for invalid or expired OTPs, according to the system's verification rules.

08 • Wireframes

From sketch to structure

Low-fidelity wireframes for the core screens, focused on hierarchy and flow before any visual styling.

Home
Create Lead: Meeting
Customer Info
Lead Detail
Calendar
09 • The Design Solution

The design solution

01

Quick Lead Creation

The registration journey was simplified to three fields followed by OTP verification. This reduces the amount of information requested upfront and creates a more focused interaction for agents capturing leads in the field.

UX value: less initial data entry, clearer progression and a more focused registration experience.

02

Mobile-First Experience

The interface prioritizes readability, clear actions and easy navigation for field-based users.

UX value: supports quick interactions and access to essential workflows in a mobile environment.

03

Unified Agent Dashboard

The dashboard brings together the key areas of the agent experience: leads, tasks, attendance and daily activities.

UX value: provides a clearer starting point for navigating the platform and accessing frequent actions.

Create Lead in three steps

The final screens split lead creation into a short stepper.

Create Lead, step 1
Step 1: MeetingBasic details (first name, last name, mobile number) and whether a meeting is scheduled.
Create Lead, step 2
Step 2: Customer InfoGender, occupation, date of birth, income range and closure date.
Create Lead, step 3
Step 3: Product PlanProduct type, sum assured, premium amount, payment frequency and lead source.

Progressive disclosure in action

The form reveals more only when it is relevant.

Meeting not scheduled
No meeting yetA short prompt reminds the agent to schedule a meeting at the earliest to drive closure.
Meeting scheduled
Meeting scheduledThe agent picks the meeting date. Additional details become visible only on the meeting day, once the meeting is completed.
Meeting done toggle
Meeting dayA Meeting Done toggle appears next to the scheduled date.
Meeting marked done
Meeting doneThe meeting is marked as done.

Lead detail

Everything about a lead, organized into three tabs.

Lead detail, info tab
InfoName, lead ID, created date and time and contact number, with a call shortcut and a Process Lead button.
Lead detail, appointment tab
AppointmentFollow-up and notes: meeting date and time, follow-up type and a note field.
Lead detail, history tab
HistoryA timeline of the lead from Lead Created to Lead Closed.
10 • Task Tracking & Attendance

Supporting the complete daily workflow

Lead creation was the primary focus, but the redesign also considered how agents interact with other essential workflows.

Task tracking

Organize pending activities and task details so agents can understand what needs attention and access the next available action.

Attendance management

Make attendance status and relevant actions easier to locate and understand.

Dashboard navigation

Establish clearer destinations and a more consistent hierarchy for daily agent activities.

Home, calendar and notifications

The daily workflow screens.

AMS/LMS home
HomeCheck-in, search, headline numbers, Today's Tasks and the Create button in the bottom bar.
AMS/LMS calendar
CalendarA date strip with Today, Upcoming and History tabs. Each entry shows the customer, time, status and meeting type.
AMS/LMS notifications
NotificationsAll and Unread filters, with reminders for demos, huddles and activities.
11 • Design Principles

The redesign followed four core principles.

01

Simplicity

Remove unnecessary complexity from frequent workflows.

02

Progressive disclosure

Request essential information first and introduce subsequent steps when needed.

03

Clarity

Use understandable labels, a clear action hierarchy and useful feedback.

04

Consistency

Create a predictable experience across lead management, task tracking, attendance and dashboard navigation.

12 • Validation & Success Metrics

Measuring whether the redesign works

The existing workflow provided a baseline of approximately 10 minutes per lead. The redesigned journey should be evaluated through usability testing and product data before claiming a specific improvement.

01

Lead creation time

Compare the time required to create and verify a lead before and after the redesign.

02

Task completion rate

Measure how many agents successfully complete each workflow.

03

Error rate

Track invalid entries, OTP errors and incomplete registrations.

04

Navigation usability

Evaluate how easily agents find leads, tasks and attendance actions.

05

Data quality

Check whether the simplified registration process maintains reliable records.

No post-redesign performance figures are claimed here because measured results were not provided.
13 • Reflection

Better UX starts by removing unnecessary effort.

This project highlighted the importance of designing around the user's real working context. A registration process that seems manageable when completing a single form can become cumbersome when an agent needs to repeat it for multiple prospects during an event.

By focusing on essential information, simplifying the lead creation journey and organizing daily workflows more clearly, the redesign established a more focused approach to the agent experience.

The goal was not simply to redesign the screens. It was to make the everyday experience of using AMS/LMS simpler, clearer and more efficient.
14 • UX Laws

UX laws applied

The laws of UX that shaped the decisions in this redesign.

01

Hick's Law

More choices take longer to decide.

In AMS/LMS: Only three essential fields first, with details revealed when relevant.

02

Jakob's Law

People prefer patterns they already know.

In AMS/LMS: Familiar steppers, tabs, cards and a bottom navigation bar.

03

Fitts's Law

Big, close targets are faster to hit.

In AMS/LMS: A large central Create button and full-width Submit buttons within thumb reach.

04

Miller's Law

People hold only a few items in mind at once.

In AMS/LMS: A long registration chunked into three steps: Meeting, Customer Info, Product Plan.

05

Goal-Gradient Effect

Motivation rises as the goal gets closer.

In AMS/LMS: The stepper shows completed and remaining steps, so agents want to finish.

06

Law of Proximity

Nearby items feel related.

In AMS/LMS: The meeting date sits right under the scheduled toggle; related details stay together.

07

Law of Common Region

Items in a shared area feel grouped.

In AMS/LMS: Cards and tabs group tasks, calendar entries and lead history.

08

Von Restorff Effect

The item that differs is remembered.

In AMS/LMS: The Create button, status tags and primary actions stand out from their surroundings.

Thanks for scrolling

Back to portfolio
Built on Hatchable