Projects
VeriBranch SaaS
A branch-facing banking SaaS platform redesigned to simplify high-volume service operations for call center teams, branch staff, and headquarters users.
Role: Senior Product Designer (UX/UI)
Scope: UX Strategy, User Flows, Information Architecture, Dashboard Experience, Design System-based Product UX
Platform: Enterprise Banking SaaS
Approach: Modular UX, White-label Structure
Overview
VeriBranch is a branch-facing banking platform built to support operational teams across customer service environments. The product serves different user groups, including call center agents, branch staff, and headquarters teams, all working within complex, high-volume service flows.
I was involved from the early phase of the product direction, following the same design language and system logic established across the broader VeriPark ecosystem. Once the design system foundation was in place, my focus shifted heavily toward UX structure, user flows, and the overall product experience.
The Challenge
The core challenge was not only visual modernization. The product needed to replace a legacy structure with a scalable and maintainable SaaS experience that could support operational clarity, adapt to different banking environments, and remain consistent across multiple use cases.
Users needed to manage queue flow, transaction status, service actions, and performance-related targets in one ecosystem. That required a clearer information structure, more intuitive task organization, and a more flexible interface model for long-term product scaling. The current VRP page already frames the redesign as a replacement of a legacy interface with a centralized design system, aimed at improving consistency, accessibility, maintainability, queue visibility, transaction tracking, KPI follow-up, and SLA-driven workflows.
Product Context
This project did not start from a blank canvas. Its design language, modular logic, and system thinking were aligned with the wider VeriPark product structure already documented in the Banking Channel case. That structure describes a central foundation library feeding multiple products, while local design systems allow customization for different banks, brands, or customer needs.
This gave us a strong base, but the real product value depended on how effectively the UX could translate that system into usable day-to-day flows.
My Role
I contributed from the early stages of the product and was actively involved in shaping the experience after the design system foundations had been defined.
My main contribution focused on:
-
restructuring user flows
-
improving information architecture
-
organizing task logic for operational users
-
shaping the dashboard experience
-
making the interface clearer, more modular, and easier to scale across white-label banking contexts
This was less about decorating a ready-made system and more about turning a system foundation into a usable product experience.
Design Approach
User Mental Model
The product followed a mobile-first and modular approach, which made it easier to define core interaction patterns clearly before extending them into larger desktop contexts. On the VPChannel page, this same logic is explained as a move from function-based architecture toward a more product-based information structure, supported by renewed business flows and tokenized system thinking.
For this SaaS experience, that meant focusing on:
Operational clarity
Designing for users who need to process tasks quickly, not browse leisurely.
Structured flows
Reducing friction across complex service actions and making task paths easier to follow.
Reusable logic
Ensuring that experience patterns could remain consistent while adapting to different institutional setups.
Scalable UX
Building on top of a centralized system so the product could grow without becoming fragmented again.
Design System Structure
The experience was built on top of a centralized design system structure that supported multiple products through a shared foundation. In the VPChannel case, this is described as a modular architecture with a central base library and local design systems connected to it, balancing consistency and flexibility across products and markets.
For this project, that structure mattered because it allowed UX decisions to remain consistent at the system level while still supporting white-label implementation needs at the product level.
Outcome & Learnings
The result was a cleaner and more adaptable branch SaaS experience designed for real operational pressure. Instead of treating the interface as a static dashboard, the redesign created a more structured environment for managing queues, monitoring transactions, tracking service performance, and supporting branch operations through a responsive, modular system.
The current case page describes that outcome as a clean, modular design that can be adapted for different banks through a white-label SaaS model.
