← Back to selected work
Case Study 05 / Enterprise banking · UX & design systems

Consistency is a product decision.

Contributing to UX research, accessibility and reusable interface patterns in the context of Finacle's enterprise banking products. This case study focuses on my design responsibilities while protecting internal work, customer information and proprietary artefacts.

Illustrative portfolio reconstruction — not an internal Finacle interface
Product context
Finacle · Enterprise banking
Organisation
Infosys · Experience Design
Project period
July 2021 – September 2022
Contribution
UX design and research · Selected workstream ownership within a team

A design system is more than a collection of components.

A shared language for interaction can help complex journeys feel more predictable. The important questions concern what a component communicates, how its states behave, and how people recognise what happens next.

01 / Public product contextVendor materials · Not personal project outcomes

One platform ecosystem. Many banking journeys.

Finacle is an enterprise banking product portfolio spanning core banking, digital engagement, payments and other financial-institution capabilities. Its public information provides context for a complex product domain, but is not evidence of the specific internal UX/UI components or interfaces my team created.

Experience layer

Digital banking experiences

  • Retail
  • Small business
  • Corporate
Operational foundation

Core banking

  • Deposits
  • Lending
  • Payments
Shared UX layer · the focus of this case study

Reusable interaction patterns

  • Forms
  • Data tables
  • Status
  • Confirmation

Patterns that can make similar tasks behave predictably across different journeys.

Componentised technology architecturePublicly described platform engineering concept

UX component libraryInterface patterns; internal contents not disclosed

Conceptual diagram of the product domain · Domain categories from public vendor descriptions; the pattern layer is a portfolio framing
Domain / Core banking

High-stakes operations

Finacle describes core banking needs including deposits, lending and payments. This illustrates the breadth of the domain; it does not establish that I designed particular modules.

Domain / Digital engagement

Different customer contexts

Its digital suite addresses retail, small-business and corporate audiences. The existence of these product categories is public information, not a record of my workstreams.

Domain / Platform

Two meanings of components

Finacle publicly discusses a componentised technology architecture. This is distinct from the UX design-system and UI pattern contributions described here.

Sources: Finacle official website, Digital Banking Solution Suite and Finacle Core Banking brochure. The current brochure contains 2025 material even though its URL says 2022; it is public background, not a dated record of this engagement.

02 / Design challengePortfolio framing · Not an internal project brief

Make complexity feel more understandable.

Enterprise financial interfaces can present dense information, consequential actions and many connected steps. My portfolio framing asks how research and shared UI patterns can support consistent interaction, clearer information and accessibility throughout those experiences. This is a design question, not a claim about a verified client problem or a measured outcome.

  1. 01

    Information density

    Many values on one screen need hierarchy and alignment to stay scannable.

  2. 02

    Common actions

    The same action should look and behave the same wherever it appears.

  3. 03

    Component states

    Default, focus, disabled and error states each need a clear, consistent appearance.

  4. 04

    Accessibility

    Labels, contrast, focus and feedback should work for people with different needs and tools.

  5. 05

    Predictable journeys

    Recognisable structure and placement help people anticipate what happens next.

Conceptual design considerations · Not verified findings about particular Finacle clients

Consistency

How can similar tasks behave predictably across journeys?

An independently expressed design question; not a confidential brief.
Clarity and access

How can interfaces communicate hierarchy, states and next actions without relying on visual familiarity alone?

A general design consideration, not a claim of certified compliance or improvement.

03 / My roleContributor and selected workstream owner

Research-led UX within a larger team.

I worked as a contributing designer and researcher at Infosys, with responsibility for selected workstreams rather than ownership of the overall Finacle design system. My involvement covered both banking-product UX and shared interface patterns. The contributions below are the high-level areas I can describe publicly.

Larger experience-design team · Infosys

My contributionsSelected workstream ownership · not the overall design-system programme
User research

Studies and usability

Contributed to user research and usability studies examining how people understood product interactions.

  • Research and usability
Experience design

Journey mapping

Worked with journey mapping to connect user needs and touchpoints beyond any single screen.

  • Journey mapping
Interface systems

Components and patterns

Contributed to UI components, design patterns, accessibility reviews and design documentation to support consistent interaction decisions.

  • UI patterns and components
  • Accessibility review
  • Documentation

Not claimed: leading the overall design-system programme, engineering implementation, product ownership or managing other designers.

These responsibilities are confirmed by the project owner. Confidential project artefacts, user records, specific clients and internal outcomes are not reproduced.

04 / Areas of practiceA contribution summary · Not a reconstructed internal timeline

From research to repeatable decisions.

My work connected research with reusable design decisions. The five practices below describe areas in which I contributed. Their order here is editorial rather than a claim about a confidential delivery methodology.

  1. Research considerations
    01 / Research

    Understand use

    Examine potential friction through user research and usability studies.

  2. Journey understanding
    02 / Journeys

    Connect touchpoints

    Use journey mapping to consider how interactions relate within a wider experience.

  3. Reusable interface decisions
    03 / Patterns

    Design coherently

    Support predictable UI behaviours through component and pattern work.

  4. Accessibility review
    04 / Accessibility

    Review inclusivity

    Consider readable structure, recognisable states and understandable controls.

  5. Design documentation
    05 / Documentation

    Share rationale

    Contribute documentation that makes design decisions easier for others to interpret.

Editorial summary of my contribution areas · Not a reconstruction of the confidential workflow
05 / Design-system thinkingIllustrative principles only · No proprietary inventory

The same pattern should mean the same thing.

Component consistency includes more than visual similarity: purpose, labels, states, feedback and recovery all affect how a control is understood. Generic banking-interface examples such as a form field, a data row or a confirmation state illustrate these ideas below. They are newly created portfolio examples, not the internal Finacle library or a claim that I owned those specific components.

Illustrative anatomy

Purpose → action → state → feedback.

Shown in the independently drawn component specimens below, using fictional information.
Illustrative accessibility checks

Can people identify a control, recognise its status and recover if something goes wrong?

This is not a disclosed audit, compliance assessment or internal component specification.

Component specimens

Independent portfolio examples · Not proprietary Finacle components
C1

Form field · anatomy

  1. 1Persistent label — stays visible while typing
  2. 2Input with a search affordance
  3. 3Helper text — explains before an error happens

Why it helpsPeople always know what a field is for, even after they start typing.

C2

Form field · states

Why it helpsEach state looks distinct, and the error state uses an icon and words as well as colour.

C3

Actions

Why it helpsOne primary action per step; secondary actions are visibly quieter, so the next step is clear.

C4

Validation and recovery

Why it helpsThe message explains what went wrong and how to fix it, next to the field, without clearing what was typed.

C5

Status badges

Why it helpsStatus is carried by an icon and a word, not by colour alone.

C6

Dense data rows

  1. 1Primary detail first, supporting details beneath
  2. 2Status with icon and word
  3. 3Right-aligned, tabular amounts for comparison

Why it helpsDense information stays scannable through alignment, tabular figures and restrained styling.

C7

Confirmation

Why it helpsConfirms what happened, the key details and what the person can do next.

Newly created explanatory examples with fictional names and values. Not copies of original project work and not a published Finacle design-system library.

Accessibility, made visible

Independently created comparisons · Not an audit, score or compliance claim
  1. Clear labels

    Harder to use
    Clearer

    A persistent label stays visible; placeholder text disappears as soon as someone types.

  2. Readable contrast

    Harder to use
    Clearer

    Text and essential graphics need enough contrast against their background to be read comfortably.

  3. Focus visibility

    Harder to use
    Clearer

    Keyboard users need to see where they are; focus should never be invisible.

  4. Helpful error feedback

    Harder to use
    Clearer

    A specific message, placed next to the field, tells people what to change.

  5. Status beyond colour

    Harder to use
    Clearer

    Pairing colour with an icon and a word keeps meaning available to everyone.

Patterns in context

Illustrative banking UI · Independently reconstructed for portfolio presentation

Two conceptual compositions show how the generic patterns above might work together in an enterprise interface. They are visual explanations with invented names and values, not evidence that these screens were designed or shipped during my Finacle engagement.

Illustrative banking UI · Independently reconstructed for portfolio presentation01 · Account overview (fictional)
Illustrative banking UI · Independently reconstructed for portfolio presentation02 · Payment review and confirmation (fictional)

The illustrative components on this page are original, labelled as portfolio reconstructions and separate from official Finacle product screenshots or private design-system assets.

06 / Public product referencesOfficially published imagery · Not my screen designs

Show the domain. Protect the work.

The vendor's public website and brochure include product imagery that helps explain the banking context. Those screens were published by Finacle and are not presented as my individual deliverables. Rather than duplicate third-party artwork without a publication licence, this case study links directly to the official sources.

Finacle trademarks and visual assets belong to their respective owners. Public availability does not itself grant rights to redistribute them. The linked pages are context, not evidence of which screens I designed.

07 / RecognitionOwner-confirmed · Private evidence not published

Recognised for innovation.

Personal recognition

Best Innovator Award for the Quarter

Owner-confirmed · Evidence held privately · Date and citation not published

During my professional experience-design work, I received the Best Innovator Award for the Quarter. I retain supporting documentation, but its internal details are not published here.

This personal recognition is not presented as a claim about Finacle's customer reach, product growth or any measured business result.

08 / Reflection and disclosureResearch and patterns · No confidential deliverables

Design beyond one screen.

Working in a complex enterprise domain strengthened my interest in research-led product design, shared interaction patterns, accessibility and design documentation. A consistent interface is meaningful when it helps people understand their options and make informed decisions.

This public case study does not reproduce proprietary design systems, internal UI screens, client workflows, research data, implementation details or third-party assets. It does not claim that I led the full initiative, delivered a particular number of prototypes or achieved an unverified increase in engagement.

Labels used on this page

Evidence boundary: my role, dates, contribution categories and award are owner-confirmed. Finacle product descriptions are based on vendor-public sources and were not created by me. Visuals on this page are independently reconstructed, clearly labelled and use fictional data only.