Multi-Platform Flow Analysis and Optimisation in Enterprise Banking
Confidentiality note
Due to GDPR and enterprise confidentiality, real production user interfaces and detailed visuals from this project cannot be publicly shared. This case study focuses on user flow analysis, system logic, decision making, and outcomes across banking platforms.
VÚB Bank operates multiple internal and client-facing digital platforms used daily by a large and diverse user base. These platforms included desktop Internet Banking and mobile banking applications, each built under strict regulatory, security, and technical constraints.
I worked embedded directly within the IT department, where UX decisions had to balance business expectations, regulatory requirements, and the limitations of an enterprise low-code framework. Changes often affected critical banking workflows, which required a high level of precision, predictability, and risk awareness.
I worked as an IT UX Analyst focused on low-code and frontend environments, with responsibility for analysing, validating, and optimising user flows across desktop and mobile banking platforms. I acted as a bridge between business stakeholders, technical constraints, and user experience logic, ensuring that proposed changes were usable, feasible, and safe to implement in a banking context.
My role combined analytical UX work with hands-on implementation, which allowed me to own flows from early validation through to delivery.
The main challenge was to maintain logical, consistent, and usable user flows across multiple banking platforms while operating within strict low-code and enterprise constraints. Business teams frequently requested new features or interface changes, often without full visibility into technical limitations or UX risks.
Even small changes could introduce inconsistencies, missing states, or increased cognitive load for users. UX needed to function as a control mechanism, ensuring that every change preserved clarity, predictability, and system integrity across platforms.
Problem: Desktop and mobile platforms provided similar functionality but followed different user flows, which caused confusion and increased cognitive load for users switching between devices.
Solution: I mapped and compared equivalent flows across platforms, identified inconsistencies and redundant steps, and redesigned flows to follow the same logical structure where technically possible.
Outcome: User flows became more predictable across platforms, reducing friction and lowering the risk of user errors.
Problem: Business requests for new features or interface changes were often proposed without understanding their impact on existing flows or low-code limitations.
Solution: I analysed each request before implementation, evaluated feasibility and UX risk, and clearly communicated trade-offs and alternatives to stakeholders.
Outcome: Risky or infeasible requests were identified early, reducing rework and preventing degradation of critical banking workflows.
Problem: The low-code framework imposed strict limitations that made standard UX patterns difficult or impossible to implement.
Solution: I designed UX solutions specifically adapted to low-code constraints and implemented flow adjustments using a combination of low-code tools and targeted frontend changes.
Outcome: Business requirements were met without breaking platform rules, and UX quality was maintained despite technical limitations.
Problem: Many flows lacked clearly defined system states such as validation, confirmation, or error handling, which increased uncertainty and support risk.
Solution: I identified missing states and edge cases and ensured they were explicitly handled within each flow, with clear feedback and predictable behaviour.
Outcome: User confidence improved, error scenarios became easier to recover from, and overall UX risk was reduced.
Problem: Traditional separation between analysis and implementation slowed down delivery and increased the chance of misinterpretation.
Solution: I combined flow analysis and implementation by owning validated changes end to end, from mapping and validation to direct implementation and testing.
Outcome: Iteration cycles became faster, delivered flows were more stable, and trust increased across both business and technical teams.
This work resulted in consistent and logically aligned user flows across desktop and mobile banking platforms. Business requests were implemented more safely within low-code constraints, UX risks in critical banking workflows were reduced, and iteration speed improved without sacrificing stability. UX gained a stronger role as a decision-making and risk-mitigation function within IT and business teams.