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.
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.
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.
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
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.
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.
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.
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.
Many values on one screen need hierarchy and alignment to stay scannable.
The same action should look and behave the same wherever it appears.
Default, focus, disabled and error states each need a clear, consistent appearance.
Labels, contrast, focus and feedback should work for people with different needs and tools.
Recognisable structure and placement help people anticipate what happens next.
Conceptual design considerations · Not verified findings about particular Finacle clients
How can similar tasks behave predictably across journeys?
An independently expressed design question; not a confidential brief.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.
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
Contributed to user research and usability studies examining how people understood product interactions.
Worked with journey mapping to connect user needs and touchpoints beyond any single screen.
Contributed to UI components, design patterns, accessibility reviews and design documentation to support consistent interaction decisions.
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.
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.
Examine potential friction through user research and usability studies.
Use journey mapping to consider how interactions relate within a wider experience.
Support predictable UI behaviours through component and pattern work.
Consider readable structure, recognisable states and understandable controls.
Contribute documentation that makes design decisions easier for others to interpret.
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.
Purpose → action → state → feedback.
Shown in the independently drawn component specimens below, using fictional information.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.
Why it helpsPeople always know what a field is for, even after they start typing.
Why it helpsEach state looks distinct, and the error state uses an icon and words as well as colour.
Why it helpsOne primary action per step; secondary actions are visibly quieter, so the next step is clear.
Why it helpsThe message explains what went wrong and how to fix it, next to the field, without clearing what was typed.
Why it helpsStatus is carried by an icon and a word, not by colour alone.
Why it helpsDense information stays scannable through alignment, tabular figures and restrained styling.
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.
A persistent label stays visible; placeholder text disappears as soon as someone types.
Text and essential graphics need enough contrast against their background to be read comfortably.
Keyboard users need to see where they are; focus should never be invisible.
A specific message, placed next to the field, tells people what to change.
Pairing colour with an icon and a word keeps meaning available to everyone.
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.
£1,200.00 to Harbour Lane Stationery on 14 March.
Confirmation ID EX-2041
The illustrative components on this page are original, labelled as portfolio reconstructions and separate from official Finacle product screenshots or private design-system assets.
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.
A public overview of enterprise banking solutions.
View Finacle's website → (external site, opens in a new tab)
Public descriptions of core banking and digital engagement offerings.
View the digital suite → (external site, opens in a new tab)
Official product marketing, including publicly shown interface imagery; its current version postdates my engagement.
View the official brochure → (external site, opens in a new tab)
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.
Best Innovator Award for the Quarter
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.
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.
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.