Role: IT UX Analyst, Low-Code & Frontend
Industry: Banking / Enterprise
Scope: User flows · Requirements clarification · Low-code implementation · Frontend adjustments · Testing
Collaboration: Business analysts · Product owners · Developers · Stakeholders
Focus: Making complex banking journeys clearer, safer, and easier to deliver across desktop and mobile
Due to GDPR and banking confidentiality, I cannot share real production screens or detailed internal visuals. This case study focuses on flow analysis, design decisions, collaboration, and the impact of the work.
At VÚB Bank, I worked in the IT department on internal and client-facing banking products. My work covered desktop Internet Banking and mobile banking flows in a highly regulated environment with strict security, technical, and low-code constraints.
Even small changes could affect important banking processes. This meant that every update had to be carefully considered in terms of consistency, validation, error handling, and implementation feasibility.
I worked on analysing, improving, and implementing user flows across desktop and mobile banking platforms.
My role combined UX flow design with low-code and frontend work. I collaborated with business analysts, product owners, developers, and stakeholders to make sure changes were clear for users, technically feasible, and safe to release.
The same banking functionality often existed across desktop and mobile platforms, but the flows were not always aligned. At the same time, business requests had to fit within a restrictive technical environment and could not compromise security, compliance, or usability.
The challenge was not only to improve the interface. It was to make sure each change worked logically across platforms, covered edge cases, and could realistically be implemented.
I compared equivalent user journeys across desktop and mobile banking, identified inconsistencies, and simplified flows where possible.
The aim was to create a more predictable experience for users switching between devices while respecting the limitations of each platform.
Business requests were often shared before their full UX or technical impact was clear.
I reviewed requests early, mapped their effect on existing flows, highlighted risks, and proposed alternatives when a solution would create unnecessary complexity or would not work within the low-code framework.
Many standard UX patterns were difficult to implement because of platform limitations.
I adapted flows and interaction patterns to what the system could support, combining low-code configuration with targeted frontend changes where needed.
A recurring part of the work was identifying missing states, such as validation messages, confirmations, error handling, and recovery paths.
I helped make these states more explicit so users received clearer feedback and could better understand what was happening during important banking actions.
Because I was involved in both flow analysis and implementation, I could follow changes from the initial request through testing and refinement.
This reduced misunderstandings between analysis, design, and development and helped make delivery smoother.
More consistent user flows across desktop and mobile banking platforms
Earlier identification of UX risks, technical limitations, and unclear requirements
Clearer validation, confirmation, and error handling in important banking flows
Faster iteration through closer collaboration between business, UX, and development
More practical, implementation-ready solutions within low-code constraints
This role strengthened my ability to work on complex digital products where UX needs to balance user needs, business priorities, technical limitations, and risk.
It also showed me how important it is to make product decisions early, before a request becomes expensive to build or difficult to change.