06 Selected work / Human Factors Institute
HDFC Bank · Internet banking
Enterprise banking · Responsive web
HDFC
Bank.
Move the complexity.
Not the task.
Five banking systems exposed five ways to find the same thing: transactions. We redesigned that fragmented experience around one customer input—a date range.
- Download Statement
- Request Statement
- Historical Statement
- View Statement
- Transaction Summary
behind the interface
transactions
The diagnosis
The interface
was a system diagram.
We mapped the existing flows and found that backend boundaries had become customer choices: recent or historical, download or request, statement or summary.
my transactions.”
- Recent or historical?
- Download or request?
- Statement or summary?
- Which system holds the date?
carries the routing.
The customer had to know where a transaction lived before they could retrieve it.
The design move
Ask for the period.
Route the rest.
The redesigned flow asked for only what the customer knew: a date range. The system then identified the right source, fetched the records, and presented one transaction list.
Early responsive interaction design
One task.
Five widths.
We designed the flow at 960, 768, 540, 480, and 320 pixels, then delivered working HTML so the client and developers could test the behavior rather than infer it from static screens.
The same information order and date-selection task survived every breakpoint; only the layout and action placement changed.
The outcome
The system carries
the constraint.
The bank kept its five data sources. Customers stopped navigating them.
A single date-range task made the service easier to understand, responsive by design, and feasible within the existing architecture.
End of selected work
← Previous · Standard Bank IVR