Zoro Bank Project Cover

PROJECT SCALE

39M+ retail banking customers
Mobile + Web

MY ROLE

Design Consultant
Led UX Research &
Design for Pod 1

MY OWNERSHIP

Login & Registration · Debit & Credit Card Management
Co-designed Dashboard · Supported Admin

RESEARCH

Mixed-method research across the banking journey
100+ survey responses · 50+ customer interviews · Branch research · Task-based usability testing
Survey design · Moderated interviews · Heuristic evaluation · Competitive benchmarking · Synthesis · Insight prioritization · Research-to-product strategy

THE TEAM

18-person design team across
5 pods · 3 design managers
5 business analysts
Engineering · Deloitte & bank stakeholders

TIMELINE

11 months

Redesigning Digital Banking for 39M+ Users

A research-led transformation of authentication, card management, dashboard, and the everyday banking experience.

As a Design Consultant at Deloitte Digital, I led UX research and design for Pod 1, owning login and registration
and debit and credit card management, while co-designing the dashboard.

I also contributed to research across the broader banking platform, using evidence to frame problems, guide
product direction, and inform design decisions.

The client has been anonymized as Zoro Bank. Some details have been altered or omitted for confidentiality.

01 The Challenge

One bank, Multiple disconnected experiences.

Customers moved between separate experiences for everyday banking, cards, loans, investments, and insurance, each with different navigation patterns and points of friction. What appeared to be one bank from the outside often behaved like several separate digital products on the inside.

Customer struggling with fragmented banking journey Customer speech bubble: I just want to check my balance... why is this so confusing? Customer confused doodle cloud
Everyday Banking
Everyday Banking app screen
Cards
Cards app screen
Loans
Loans app screen
Investments
Investments app screen
Insurance
Insurance app screen
10,000+
CUSTOMER COMPLAINTS

Customers were struggling
before they could even reach
the rest of the banking experience.

IT WASN'T JUST A

DESIGN PROBLEM

Every simplification had to work within multiple constraints, making the problem more complex than just the interface.

Security
SECURITY

Protecting customer data and preventing fraud.

Regulation
REGULATION

Meeting strict banking and compliance requirements.

Technical Constraints
TECHNICAL CONSTRAINTS

Working within existing systems and infrastructure.

Established Behavior
ESTABLISHED BEHAVIOR

Respecting mental models and usage patterns.

Business Priorities
BUSINESS PRIORITIES

Supporting product growth and commercial goals.

THE DESIGN QUESTION

How might we make digital banking easier to use without compromising the trust and control customers expect from a bank?

02 Research & Strategy

Research that changed product direction

Research ran throughout the engagement. We combined multiple methods
to understand behavior, friction, and decision-making across the banking journey.

UX Research Deep Dive
Mapping journeys and friction points on whiteboard
Understanding real customer pain points on sticky note wall
User research notebook notes and diagrams
Banking Login Experience Survey and affinity clustering
Research synthesis and journey mapping on digital canvas
Banking Login Experience Survey questionnaire forms

Research Program

A mix of qualitative and quantitative methods helped us build a complete picture
of customer needs, friction points and opportunities.

Customer complaint analysis 10,000+ complaints analyzed
Surveys 100+ survey responses
Moderated interviews 50+ interviews (15+ conducted by me)
Branch research In-branch observations for offline context
Task-based usability Across key journeys (login, dashboard)
Heuristic evaluation Best practices review & gap analysis
Competitive
benchmarking
Leading Indian & global banks
Customer-review analysis App store & sentiment analysis

Study samples

We recruited customers across key journeys to validate behavior and test core flows.

Registration n=22
Login n=22
Password Reset n=18
Dashboard n=39

Four findings became four design principles

We synthesised research insights into clear design principles that guided the product
strategy and experience design across the banking journey.

01 FINDING

53% forgot their
User ID, password, or both

DESIGN PRINCIPLE Reduce memory burden
02 FINDING

47% preferred debit-card
verification for recovery

DESIGN PRINCIPLE Make trust visible
03 FINDING

72% did not want promotional
banners dominating the dashboard

DESIGN PRINCIPLE Protect the primary task
04 FINDING

Digital friction could move
into the physical service

DESIGN PRINCIPLE Design beyond the screen

03 Authentication

Reducing memory burden without forcing behavior change.

Login and registration were the biggest source of friction, with 52% of customer complaints related to authentication. Customers struggled with remembering multiple credentials, receiving OTPs, and recovering access.

Our goal was to design a simpler, more intuitive authentication experience while maintaining the security, regulatory, and business requirements of a bank.

Customer struggling with remembering credentials, receiving OTPs, and recovery flows
3.1 KEY INSIGHTS FROM RESEARCH

Key insights from research

Authentication was a major pain point.

Insights from 100+ survey responses, 50+ customer interviews, branch research and usability testing.

53%

forgot their User ID, password or both.

The problem wasn't just the number of steps, but the amount of information customers had to remember.

14%

didn't receive an OTP.

OTP delivery issues created significant drop-offs during login and registration.

61%

still used User ID and Password.

Most customers were familiar with this method and were not ready to fully switch.

42%

preferred using Mobile number + mPIN for login.

Customers preferred options that were easier to remember and always available.

Zoro Bank Onboarding & Welcome Screens
3.2 EXPLORING SOLUTIONS

We explored multiple authentication approaches.

We considered different ways to simplify login and registration, evaluated their feasibility, and tested them with customers.

01
Keep User ID + Password as default

Familiar to most users and requires no behaviour change.

Keep User ID + Password as default screen
Benefits
  • Familiar and widely used
  • Lower support burden
Limitations
  • High memory burden
  • Continued login errors
02
Require Mobile Number + mPIN

Simpler and easier to remember.

Require Mobile Number + mPIN screen
Benefits
  • Reduces credential recall
  • Quicker login experience
Limitations
  • Forces behavior change
  • Some users don't receive OTPs
3.3 THE CHOSEN APPROACH

A flexible and familiar login experience.

We designed a unified experience that supports multiple login options, reduces memory burden, and keeps the experience simple and consistent.

Zoro Bank Chosen Login Approach Screens
1. Choose login method

Start with a single, simple input.

2. Enter mPIN

Simple and quick verification.

3. Logged in

A seamless transition to home.

Why this approach?
Flexibility

Gives customers flexibility to use the method they prefer.

Reduces memory burden

Reduces the amount of information they have to remember.

Simple and consistent

Keeps the experience simple and consistent across web and mobile.

Security requirements

Works within security and regulatory requirements.

3.4 WHAT TESTING CHANGED

Observing what customers did, not only what they said.

01
The meaning of mPIN was unclear.

Some participants confused their banking-app mPIN with their ATM PIN. I introduced clarifying copy to make the distinction understandable.

02
Biometric login was expected.

Some returning customers instinctively searched for biometric authentication, reinforcing the importance of supporting a familiar, low-effort return journey.

3.5 VALIDATION WITH USERS
LOGIN JOURNEY · 22 PARTICIPANTS

The login experience was easy to use in testing.

79%

rated the task easy.

4.3/5

average ease rating.

90%

encountered no difficulty.

The flow felt simple and easy to follow. I like that I can use my mobile number.
— Research participant

04 Card Management

Giving customers control without creating anxiety.

Card controls ranged from everyday settings to actions with permanent financial consequences. Making every action equally prominent could increase visibility, but also the risk of costly mistakes.

The question: How do we make routine card management effortless while keeping consequential actions deliberate?

One card. Different levels of risk.
DEBIT CARD •••• •••• 4512 ZORO BANK
CARD CONTROLS
Freeze card
Transaction limits
Where should friction live?
4.1 THE DESIGN LENS

Not every card action deserves the same treatment.

Instead of organizing controls only by feature type, I assessed them through
frequency, reversibility, and potential consequences.

94%

Have a savings account, credit card and loans as their primary product.

Many customers use cards alongside multiple banking products.

40%

Use net banking as either a primary or secondary method.

Card management needed to work well for both mobile and web users.

59%

Considered dashboard customization important.

Customers wanted the ability to quickly access and manage their cards from the home screen.

47%

Preferred debit card verification for password recovery.

Tangible and familiar verification methods were easier to trust.

Customer holding banking app card controls with friction points and questions
4.2 DESIGN APPROACH

Clear, accessible controls for everyday card management.

We redesigned the card-management section to bring the most important actions upfront, use familiar language, and guide customers with clear feedback and safeguards.

Card overview screen
01 Card overview

Quick access to the most important controls.

Card settings screen
02 Card settings

Control how and where the card can be used.

Manage PIN screen
03 Manage PIN

Simple and secure PIN management.

Success feedback screen
04 Success feedback

Clear confirmation to build trust.

4.3 BALANCING CONTROL AND SECURITY

Empowering customers while keeping them safe.

We introduced protective patterns and clear guidance to help customers understand the impact of their actions.

Temporarily Block Card modal screen
Design principles
Give control, not confusion
Give control, not confusion Make important actions easy to find and understand.
Explain the impact
Explain the impact Use clear language for limits, blocks and replacements.
Guide secure behaviour
Guide secure behaviour Add contextual information where needed.
Key considerations
Security
Security Prevent fraud and unauthorized use.
Regulatory requirements
Regulatory requirements Comply with RBI and card network rules.
Customer behaviour
Customer behaviour Respect existing mental models.
Business priorities
Business priorities Support usage, activation and growth.
4.4 WHAT TESTING REVEALED

Customers could complete key tasks with confidence.

Task-based usability testing with 22 participants highlighted a clear and intuitive experience, with only minor points of confusion.

Checkmark icon
82% completed card management tasks successfully.
Star icon
4.4/5 average ease rating.
Users icon
90% found it easy to locate important actions like block, limits and PIN.
It's easy to find the option I need. I feel in control and know what each action does.
— Research participant
4.5 THE RESULT

A card management experience that feels simple, safe and in your control.

Key actions upfront
Key actions upfront Quick access to settings, PIN, limits and block.
Clearer security guidance
Clearer security guidance Helpful information at decision points.
Consistent experience
Consistent experience Aligned patterns for debit and credit cards.

05 Dashboard

A clearer, more personalised dashboard for everyday banking.

The dashboard is where everything comes together. It needed to give customers a clear overview of their money, quick access to everyday actions, and a personalised experience across multiple banking products — without feeling cluttered or overwhelming.

Designing the dashboard experience
5.1 KEY INSIGHTS FROM RESEARCH

Customers wanted a simpler and more relevant dashboard.

Insights from 100+ survey responses, 50+ customer interviews, branch research and usability testing.

59% considered dashboard customization important.

Customers wanted the ability to see and manage the information that matters most to them.

Many users felt overwhelmed

The existing dashboard contained too much information and made it difficult to find key actions.

Customers expected quick access

to everyday tasks such as transfers, bill payments and card management.

Enable personalisation and control

Customers wanted personalized dashboards to see what matters most. Give users the ability to customize their experience and manage their information.

5.2 THE PROCESS

A research-led and iterative design process.

We combined customer research, competitive analysis, ideation and multiple design iterations to define and validate the new dashboard experience.

01
Research & Insights

Competitor analysis, customer research, branch research, customer needs and pain points.

02
Ideation & Concepting

Explored different ways to organize information, prioritize actions and support personalisation.

03
Design Iterations

Created and refined multiple low and high fidelity designs based on research insights.

04
Usability Testing

Tested key journeys with customers to validate the design and identify areas for improvement.

05
Final Design

Delivered a clean, intuitive and personalised dashboard experience for web and mobile.

5.3 FROM INSIGHTS TO DESIGN

A personalised, easy-to-navigate dashboard.

Quick access
to key actions
Your accounts
at a glance
Zoro Bank Dashboard Responsive Mockups
Clear overview
of finances
Personalised
recommendations
Easy access to
everyday tasks
Zoro Bank Dashboard Screen Variations and States
5.4 VALIDATION WITH USERS

A clearer and more intuitive dashboard experience.

Usability testing with 22 participants showed that the new dashboard was easy to navigate, helped customers find important information quickly, and felt more relevant to their needs.

86%

completed key dashboard tasks successfully.

4.4/5

average ease rating.

91%

found it easy to locate important information and actions.

The new dashboard feels a lot cleaner and easier to use. I can see what I need and access things quickly.
— Research participant
5.5 THE RESULT

A dashboard that gives customers control and confidence.

Clearer overview

A simplified layout that highlights what matters most.

Personalised experience

Flexible components to show relevant products and actions.

Faster access

Quick and easy access to everyday tasks like transfers, bill payments and card management.

Greater confidence

A cleaner, more intuitive experience that helps customers feel in control of their money.

06 System & Delivery

Designing for the platform, not just individual screens.

Authentication, card management, and the dashboard could not operate as isolated experiences. The work had to connect into a broader banking system, communicate clearly in high-anxiety moments, and hold up through implementation.

6.1 INFORMATION ARCHITECTURE

Connecting the wider banking ecosystem.

I created a unified information architecture to ensure a consistent and scalable experience across all key product areas, with clear relationships, shared patterns, and room for future growth.

Zoro Bank
Payments
  • Transfers
  • UPI Payments
  • Bill Payments
  • Transaction History
Savings
  • Savings Account
  • Goals
  • Auto-save
  • Recurring Deposits
Cards
  • Debit Cards
  • Credit Cards
  • Card Controls
  • Rewards & Offers
Loans
  • Personal Loans
  • Loan Offers
  • Repayments
  • Eligibility & Status
Investments
  • Mutual Funds
  • Digital Gold
  • Bonds
  • Portfolio
Deposits
  • Fixed Deposits
  • Recurring Deposits
  • Manage & Renew
  • Interest & Maturity
Insurance
  • Health Insurance
  • Life Insurance
  • Motor Insurance
  • Travel Insurance
More Services
  • Authentication
  • Profile & Settings
  • Help & Support
  • Notifications
MY KEY CONTRIBUTIONS
Authentication entry points and recovery paths.

Designed sign in, verification and account recovery across the platform.

Debit and credit-card hierarchy.

Structured how different card types are presented and organised.

Navigation between card types.

Defined clear pathways between debit, credit and additional card products.

Placement and depth of different card controls.

Determined what controls are surfaced, and how deep settings are organised.

6.2 TONE OF VOICE & ERROR STATES

Designing how the product speaks when something goes wrong.

Error states are high-anxiety moments. The goal was to make communication more contextual and actionable, helping users quickly understand what happened and how to move forward.

Before Generic and unclear.
Before: Generic and unclear error dialog
After Clear, contextual and actionable.
After: Clear, contextual and actionable error dialog
A CLEARER ERROR MESSAGE ANSWERS THREE KEY QUESTIONS:
  • 01
    What happened?

    A clear and specific explanation in simple language.

  • 02
    What does it mean?

    Helps users understand the impact on their request or account.

  • 03
    What should I do next?

    Provides a clear next step, with help options where needed.

6.3 ACCESSIBILITY, QA & LAUNCH

Making high-stakes interactions understandable and deliberate.

I remained involved through QA, refinement, and launch to help maintain design integrity, resolve edge cases, and ensure a consistent experience across devices and platforms.

Legibility
Legibility

Clear type hierarchy and readable content at all screen sizes.

Contrast
Contrast

Meets accessibility standards for text, icons and components.

Touch targets
Touch targets

Comfortable sizing for key actions across mobile.

Interaction states
Interaction states

Clear feedback for press, loading, empty and disabled states.

Error clarity
Error clarity

Consistent and helpful error patterns across the platform.

Sensitive information
Sensitive information

Careful treatment of personal and financial data.

DELIVERY PROCESS
01
Design QA

UI review, accessibility checks and edge cases.

02
Implementation refinement

Work with engineering to resolve issues.

03
Cross-team alignment

Partner with product, engineering and compliance.

04
Launch

Support release and monitor post-launch.

07 Validation & Reflection

Evidence first. Reflection after.

The redesign was evaluated through usability research. Where analytics were not available, I deliberately distinguish measured usability evidence from what I would validate in production.

7.1 USABILITY RESULTS
ALL FINDINGS ARE FROM A MODERATED USABILITY STUDY WITH n = NUMBER OF PARTICIPANTS.

What the research demonstrated.

Login icon LOGIN n = 22
Login screen mockup
79%

Rated the task easy.

4.3 / 5

Average ease rating.

90%

Encountered no difficulty.

Registration icon REGISTRATION n = 22
Registration screen mockup
81%

Rated the journey easy.

71%

Described it as user-friendly with fewer clicks.

Password reset icon PASSWORD RESET n = 18
Password reset screen mockup
78%

Rated the task easy.

4.2 / 5

Average ease rating.

90%

Encountered no difficulty.

Dashboard icon DASHBOARD n = 39
Dashboard screen mockup
82%

Found viewing savings, loan, and investment information easy.

31%

Experienced a findability gap around important actions.

7.2 WHAT I'D MEASURE NEXT

These metrics would help validate whether the solution drives meaningful improvements at scale beyond the usability study.

Authentication icon AUTHENTICATION
  • First-attempt login success
  • mPIN adoption
  • OTP failure loops
  • Password-reset completion
  • Login-related complaint volume
Card Management icon CARD MANAGEMENT
  • First-click success
  • Completion of common card controls
  • Permanent-block reversals
  • Security-control usage
Dashboard icon DASHBOARD
  • Transfer discoverability
  • Quick Links usage
  • Customization behavior
  • Task abandonment
  • Contextual-offer engagement

Did we reduce the customer effort behind the problem that represented more than half of the complaints we uncovered?

7.3 REFLECTION

The real lesson was not about fewer clicks. It was about where complexity belongs.

Reflection: woman looking ahead
It took me a 45-minute bus ride to get home, but I used the time to set up my account. It felt simple, and I didn't get stuck once.

Why wasn't it always like this?

— USABILITY PARTICIPANT
01

Remove friction caused by recall burden and weak hierarchy.

02

Keep deliberate friction where consequences are high.

03

Make financial control feel understandable, not intimidating.

A login screen may look small, but it can determine whether the service is usable.