Overview
I partnered with business and engineering to shape a reusable banking product that consolidates customer information, tasks, and follow-ups into a single view.
My contribution was defining key flows, the initial information architecture, product guidelines, and a component library adaptable across banks.
The challenge
To understand a single customer, the bank had to check up to 10 systems. This slowed servicing, increased friction, and complicated daily operations.
Key issues identified
- 30 min average servicing time before the product.
- 10 systems consulted to consolidate information.
- High dependency on manual rules and approvals.
- Low clarity around the initial product flows and structure.
Objective
Create a 360 banking platform that brought together customer data, tasks, follow-up, and sales opportunities in a clear, reusable, and viable first version.
Unify the customer view
Reduce dependency on multiple systems and surface key context in a single interface.
Speed up servicing
Reduce operational query and resolution time without losing traceability or control.
Scale the MVP
Design a foundation adaptable to new brands, banks, and business rules.
My role and scope
I worked as Product Designer and UX/UI Designer, connecting discovery, architecture, flow design, UI Kit, and handoff to turn an operational need into a usable banking product.
Research and definition
I reviewed mapped needs, interviewed business and legal stakeholders, and identified gaps in users, flows, and structure.
Architecture and design
I aligned the initial architecture, prioritized the MVP, and turned decisions into mockups and testable screens.
System and handoff
I documented components, guidelines, and deliverables to support development kickoff.
How I worked
I ran the project in short sprints, with workshops and frequent validations to align product, design, and technical feasibility.
Discovery
Internal interviews, pain points, needs, and baseline hypotheses.
Definition
MVP v1, critical flows, and feasible scope with the PO and technical lead.
Design
Mockups, client validation, and short iterations.
Delivery
UI Kit, handoff, and reusable foundation for development.
Deliverables
1. Architecture and MVP
I defined a baseline architecture where customer information and the commercial module coexist in the same flow without losing operational context.
- MVP defined to validate quickly with the client.
- Architecture aligned with engineering from day one.
- Reusable baseline to customize per bank.
2. Single customer view
The proposal consolidated products, key data, follow-ups, and commercial context into a clear dashboard to reduce context switching.
Before the final UI, I worked through flows, information architecture, and mockups to ensure the solution was clear and technically feasible.
3. UI Kit and reusable system
I designed an organized UI Kit to adapt the product to different brands without rebuilding the system foundation.
The library helped align components with engineering and speed up future implementations.
Impact
Reduction in servicing time, from roughly 30 min to 10 min.
Consolidation of consulted systems into a single environment.
Reusable baseline to adapt brand and structure to new banks.
Gallery
Learnings and improvements
“Today, I would complement this work with a measurement plan from the first version to keep iterating with stronger evidence.”
- 01
Alignment
Defining the MVP, architecture, and working cadence early unblocked decisions between business and engineering.
- 02
Banking domain
Understanding rules, approvals, and business language was key to designing better solutions.
- 03
Scalability
Designing for components and customization from the start made the product more scalable and sellable.