Banking · Case Study · Growth under constraint

A bank needed to double its Fixed Deposit bookings. The backend was off-limits. Design delivered a 60% lift in three months.

How I turned a stalled growth target into roughly 3,000 extra bookings a day — not with new technology or a bigger budget, but by finding the customer the business had misjudged.

Fixed Deposit booking app screens showing custom FD setup, popular picks with returns, and a booking confirmation, with a callout showing daily Fixed Deposits booked rising from 5,000 to about 8,000
5,000 → ~8,000Daily Fixed Deposit bookings
+60%Growth in three months
0Backend changes required
25–30The real audience, not the assumed 35–50

My role

UX Lead

Industry

Banking · Mobile app

Timeline

3 months, UX + Engineering

Constraint

Experience layer only — no backend changes

Overview

The problem, the constraint and the outcome in one minute

Leaders rarely need more screens. They need a number to move. This project is a clean example of how I work: start from the business outcome, question the assumptions standing in its way, and prove the answer before scaling it.

The goal

Grow daily Fixed Deposit bookings in the bank's mobile app from 5,000 to 10,000.

The constraint

The backend was completely off-limits. Every gain had to come from the experience layer alone.

My move

When the first redesign failed, I went back to real customer behaviour and found the business was designing for the wrong people.

The result

Daily bookings rose to nearly 8,000 in three months — about 60% growth, with no backend change.

Challenge

A growth target, a locked backend and an audience everyone agreed on

With the backend untouchable, every decision had to happen in the interface. Stakeholder discussions pointed to one logical audience — customers aged 35 to 50 — and we built the landing page, key screens and messaging around them. The redesign failed in testing.

The real risk was never a weak design. It was a confident, shared assumption that nobody had tested — the kind of risk that survives meetings, dashboards and sign-offs, and quietly drains budget.
01 — Target: 5,000 → 10,000 bookings a day 02 — Backend completely off-limits 03 — First redesign failed in testing

Insight

I stopped optimising and went back to the evidence

Instead of polishing a broken assumption, I studied real behaviour and data from people actually using the banking app. The pattern that emerged had nothing to do with the age group the business had in mind.

"

The customers most likely to book a Fixed Deposit weren't 35 to 50 — they were 25 to 30. Nothing like we'd assumed.

Turning a failed test into a better question — rather than defending the original plan — is the decision that unlocked everything that followed.

Approach

A four-step path from a failed assumption to a measurable result

A 25-to-30-year-old booking a Fixed Deposit has different motivations, different trust signals and a different pace than the audience we had assumed. So the journey had to be rebuilt around them, not retrofitted.

STEP 01

Diagnose

Treated the failed test as information, not a setback, and traced behaviour and data to find who was really booking.

STEP 02

Reframe

Mapped what the real audience needed — motivation, trust signals and pacing — and chose the direction around them.

STEP 03

Rebuild

Redesigned the landing page and every key screen in the booking flow, all within the experience layer.

STEP 04

De-risk

Tested the new experience with a small group of customers before rollout, so scale came with evidence.

Five screens from the redesigned Fixed Deposit booking flow: custom FD setup, custom tenure picker, FD ready to book, review screen, and booking confirmation

The final booking flow — pick an amount and tenure, review what you’ll get, and book in one clear step.

Results

About 3,000 extra bookings a day, without touching the backend

Within three months of the redesign, the app was booking close to 8,000 Fixed Deposits a day, up from 5,000. That is roughly 60% growth, delivered entirely through a better understanding of the customer.

~3,000Additional bookings every day
+60%Daily booking growth
3 monthsFrom redesign to result
0Lines of backend code changed
We did not reach the 10,000 target, and I say so plainly. Leaders make better decisions when the numbers they are given are honest — that is as much a part of the job as the design.

How I work

The problem-solving pattern I bring to your organisation

The Fixed Deposit story is one example of a habit I apply to every business problem. If you lead a team, a product or a budget, this is what you can expect from me.

I question the assumption before funding the fix

The most expensive mistakes are the ones everyone agrees on. I find the belief that hasn't been tested and test it first.

I work inside real constraints

Locked systems, fixed budgets and tight timelines are the starting point, not an excuse. Constraints often produce the clearest thinking.

I prove it small before scaling it

A short test with real customers costs far less than a failed launch, and it gives leadership evidence instead of opinion.

I report results honestly

I connect design to a business number and share it as it is, including what fell short, so you can decide with confidence.

This applies when growth has stalled, when a product is live but unused, when a costly rebuild is on the table, or when a capable team is building confidently for the wrong user. If any of that sounds familiar, write to me at pranjal.productmind@gmail.com.

Explore more

Driver safety app screens showing safety score, challenges, and star drivers leaderboard

The app was excellent. Every feature the drivers needed was there. So why was nobody using it?

← Back to all projects

See everything I've worked on

© 2026 Pranjal Chawan. All rights reserved.