HDFC Bank · Lead Product Designer

Enterprise Loan Management Platform for India's Largest Private Bank

02 · TL;DR

At a glance

The Brief

Translating a legacy manual workflow into a streamlined, fully digital experience. By tackling market-specific challenges and balancing business needs for accelerated approvals and improved transparency.

Overview

HDFC's disbursement toolchain was fragmented across agents, spreadsheets, and legacy screens—a poor fit for high-volume tower projects—so borrowers and builders lacked a single coherent path from initiation to disbursement.

What I did?

° Conducted 6 in-depth user interviews across 6 major cities
° Led cross-functional alignment with 7+ stakeholder teams
° Designed holistic dashboard view with key KPIs

2 Product Managers

1 Operations

4 Marketing

1 Customer Success

Lead Product Designer (me)

1 Sales

2 Legal

4 Development

2 Finance

Stakeholder collaboration

Duration

months

Collaborators7+Stakeholder teams aligned

Adoption

Users onboarded inside the first operational year

Loan Volume30%Increase in loan volume

My role

Lead Product Designer

Team4Design, Research, and PM

03 · CONTEXT

A Market Built for a Different Era

Over 80% of India's urban housing market is driven by large multistory apartment projects — hundreds of units per property, multiple developers, thousands of customers, all moving through the same loan pipeline.

Why did HDFC need this?

HDFC's existing system wasn't built for this. It was built for single-unit listings, and it showed. Loan applications moved through a patchwork of agents, spreadsheets, and legacy screens

The opportunity

Build a fully digital workflow that eliminates agent dependency, reduces processing time, and scales with growing loan volume. Provides loan visibility, transparency, and trust for users and business owners.

04 · PROBLEM

What 30 Days of Silence Actually Looks Like

Here's what a housing developer's loan journey looked like before this platform existed:
A developer submits documents through an agent. The agent forwards them to the bank. Somewhere inside, the application enters a queue no one outside can see. Days pass. The developer calls the agent. The agent calls the bank. Nobody has a clear answer. More days pass. A document is missing — but no one told the developer, so they're still waiting. By the time the correction is made, weeks have gone by.

Problem

Agent dependency in legacy workflow: diagram of Housing Developers, Customers, Agent, and HDFC Bank with numbered steps and timeline.

Solution

Streamlined workflow reducing dependencies: Unified Portal connecting Housing Developers and Customers to HDFC Bank with verification, approval, and disbursement steps and 8-day timeline.

05 · RESEARCH

Six Cities, One Pattern

We interviewed housing developers across six cities — Mumbai, Delhi, Bangalore, Chennai, Hyderabad, and Pune — ranging from boutique developers with two ongoing projects to firms managing hundreds of units simultaneously.

Three things came up in every single conversation:

Language Barriers

Mid level developers face language barriers and low comfort with digital tools

Reliance on Agents

This dependency suggests the existing ecosystem doesn't meet user needs

Transparency in Status

Users experience frustration due to absence of direct visibility into loan status

Market Research

Market Analysis

India's urban housing market is dominated by large multistory apartment projects (over 80%) involving hundreds of units per property.

Competitor Benchmark

° Other banks relied on manual Excel-based data entry, increasing risk of errors.
° Real Estate platforms like MagicBricks and NoBroker optimized end-user browsing but lacked enterprise onboarding workflows.

Gaps & Opportunities

Placeholder: brief narrative on the main gaps between user needs and the current experience, and how those informed the opportunity areas explored in the matrix.

Identifying opportunities: effort versus impact matrix with initiatives such as digital document submission, unified dashboard, and developer self-service portal.

08 · ALIGNMENT

Seven Teams. Seven Agendas. One Product.

Business Needs	Balancing Both	User Needs
1. Data Entry Across Departments Each department (Credit, Legal, Technical, Disbursement) wanted their own data fields and forms to ensure complete information capture and accountability.	Designed a solution where shared fields auto-populate across departments. Introduced role-based views — each department could add specific fields without duplicating user input. This maintained departmental control while creating a seamless user flow.	Customers and relationship managers wanted to avoid filling or uploading the same information repeatedly during the loan journey.
2. Disbursement Compliance The business wanted strict audit trails and manual checkpoints before releasing funds to developers to ensure compliance with RBI and internal audit norms.	Implemented a semi-automated disbursement request flow — developers could trigger a request by uploading progress proofs, and the system would auto-validate completeness before sending for manual approval. This reduced delays while retaining compliance checkpoints.	Developers wanted faster disbursement processing once milestones were achieved, avoiding manual back-and-forth.
3. Loan Status Transparency Departments wanted control over when status updates were visible externally to avoid premature disclosure of internal decisions.	Created a tiered visibility model — certain statuses (like “under review” or “awaiting approval”) were automatically shared with customers, while sensitive backend updates remained internal until finalized. This built transparency without compromising internal control.	Customers wanted real-time updates to reduce uncertainty and constant follow-ups.

Business Needs

Balancing Both

User Needs

1. Data Entry Across Departments

Each department (Credit, Legal, Technical, Disbursement) wanted their own data fields and forms to ensure complete information capture and accountability.

Designed a solution where shared fields auto-populate across departments. Introduced role-based views — each department could add specific fields without duplicating user input. This maintained departmental control while creating a seamless user flow.

Customers and relationship managers wanted to avoid filling or uploading the same information repeatedly during the loan journey.

2. Disbursement Compliance

The business wanted strict audit trails and manual checkpoints before releasing funds to developers to ensure compliance with RBI and internal audit norms.

Implemented a semi-automated disbursement request flow — developers could trigger a request by uploading progress proofs, and the system would auto-validate completeness before sending for manual approval. This reduced delays while retaining compliance checkpoints.

Developers wanted faster disbursement processing once milestones were achieved, avoiding manual back-and-forth.

3. Loan Status Transparency

Departments wanted control over when status updates were visible externally to avoid premature disclosure of internal decisions.

Created a tiered visibility model — certain statuses (like “under review” or “awaiting approval”) were automatically shared with customers, while sensitive backend updates remained internal until finalized. This built transparency without compromising internal control.

Customers wanted real-time updates to reduce uncertainty and constant follow-ups.

09 · IDEATION

Proposed workflow

This workflow transforms the fragmented, agent-dependent manual process into a unified digital ecosystem that reduces processing time from 30 days to just 8 days—a 73% improvement—while eliminating dependency on bank agents as intermediaries.

Streamlined workflow diagram: Housing Developers and Customers submit documents to a Unified Portal, verification with HDFC Bank, and outcomes through project approval and loan sanction with an 8-day timeline.

01For HDFC

° Central underwriting queue with SLA tracking
° Role-aware approvals and escalation paths
° Integrated risk flags with audit trails
° Dashboards for disbursement KPIs across regions
° Batch exports for treasury and reconciliation

02For Customers

° Transparent application timelines
° Digital document submission and previews
° Status notifications via SMS/email
° Self-help checklist for prerequisites
° Mobile-responsive journey for co-applicants

03For Developers

° Portfolio view of towers and disbursement stages
° Offline-friendly site progress capture
° Shared document vault with versioning
° Comment threads anchored to approvals
° Export handoffs to compliance reviewers

Co-creating Information Architecture with Stakeholders

We worked closely with stakeholders in an iterative, back-and-forth process to co-create a clear and intuitive information structure. We aligned on user needs, business goals, and content priorities, ensuring the architecture supported seamless navigation and discoverability across the platform.

Design Philosophy

Design for Efficiency

Reduced workflow steps through guided paths, dashboards, and inline validation so analysts spend time on judgment, not data wrangling.

Design for Trust

Clear status timelines, disclosures, and feedback patterns so borrowers and developers understood where they stood.

Design for Scale

Component-based patterns and repeatable templates adapted as new projects and corridors onboarded.

Design for All Stakeholders

Kept HDFC analysts, borrowers, builders, and field teams united in shared objects and statuses.

Design for Resilience

Planned offline edge cases and exception flows so disruptions did not deadlock disbursement.

Design for Inclusion

Plain-language copy, multilingual consideration, and legible hierarchies lowered barriers for junior staff and borrowers.

HDFC loan tool: PortDe project summary with sidebar, metrics, disbursement chart, and actions.

Project Listing

Users can view projects and locate them on a map — surfacing approvals, timelines, and project health at glance.

Disbursements

Users can view tower listing, customer details, and request disbursements.

Work Progress

Developers keep banks informed about construction status with structured milestones.

13 · Outcomes & learnings

Outcomes & learnings

What worked

° Embedding early checkpoints with underwriting led to tighter feedback loops.
° Transparent milestones reduced inbox escalations.
° Shared component library aligned dev and QA handoffs.

What I'd do differently

° Probe regional branch variations sooner in rollout planning.
° Instrument analytics earlier to validate KPI adoption dashboards.
° Expand multilingual pilot coverage for tier-3 cities earlier.

Key takeaway

Harmonizing underwriting logic with humane status communication proved as important as optimizing screen flows — accelerating adoption required making the invisible bureaucracy legible across every stakeholder.