Product Design
Meridian Bank Concept
Private Bank Concept
Year :
2026
Industry :
Banking
Project Duration :
2 Weeks
Problem :
As Product Designer, I designed a sovereign-grade digital banking platform for institutional clients of a regulated financial institution. The project covered onboarding, KYC, account management, and compliance reporting across 40+ screens, delivered end to end and solo — from discovery through developer handoff.
Solution :
I built the design system before designing individual screens: tokens, a typography scale, and a component library that every downstream screen would inherit. This let the platform scale to 40+ screens without losing consistency.
TOKEN-BASED DESIGN SYSTEM
Reusable tokens, typography, and components used as the foundation for every screen in the platform.
COMPLIANCE-ALIGNED FLOWS
Onboarding, KYC, and account management flows designed to meet the standards expected of a regulated institution.
COMPONENT LIBRARY
A shared component library that made adding new screens straightforward, without reworking existing patterns.
CONSISTENCY AT SCALE
Regular checks to confirm the system held up as more screens were added, rather than reviewing each screen in isolation.
DESIGN PROCESS
Delivered the full lifecycle solo: discovery, information architecture, interaction design, Figma system build, and developer handoff.
Challenge :
The platform needed to support 40+ screens for a regulated financial institution, spanning onboarding, KYC, account management, and compliance reporting. Without a shared system, projects at this scale typically become inconsistent across screens and difficult to maintain as they grow.
40+ screens required for full platform coverage
Regulated institution with strict compliance requirements
No existing design system to build from
Solo delivery, with no team to catch inconsistencies
Summary :
Impact & Results
The platform shipped as a 40+ screen banking system built on a single design foundation, delivered solo for a regulated financial institution, with the platform remaining consistent across every flow from onboarding through compliance reporting.
Key Learnings
Build the system before the screens, not alongside them
Consistency at scale depends on the foundation, not individual review
Regulated environments require the system to hold up under scrutiny, not just look polished
More Projects
Product Design
Meridian Bank Concept
Private Bank Concept
Year :
2026
Industry :
Banking
Project Duration :
2 Weeks
Problem :
As Product Designer, I designed a sovereign-grade digital banking platform for institutional clients of a regulated financial institution. The project covered onboarding, KYC, account management, and compliance reporting across 40+ screens, delivered end to end and solo — from discovery through developer handoff.
Solution :
I built the design system before designing individual screens: tokens, a typography scale, and a component library that every downstream screen would inherit. This let the platform scale to 40+ screens without losing consistency.
TOKEN-BASED DESIGN SYSTEM
Reusable tokens, typography, and components used as the foundation for every screen in the platform.
COMPLIANCE-ALIGNED FLOWS
Onboarding, KYC, and account management flows designed to meet the standards expected of a regulated institution.
COMPONENT LIBRARY
A shared component library that made adding new screens straightforward, without reworking existing patterns.
CONSISTENCY AT SCALE
Regular checks to confirm the system held up as more screens were added, rather than reviewing each screen in isolation.
DESIGN PROCESS
Delivered the full lifecycle solo: discovery, information architecture, interaction design, Figma system build, and developer handoff.
Challenge :
The platform needed to support 40+ screens for a regulated financial institution, spanning onboarding, KYC, account management, and compliance reporting. Without a shared system, projects at this scale typically become inconsistent across screens and difficult to maintain as they grow.
40+ screens required for full platform coverage
Regulated institution with strict compliance requirements
No existing design system to build from
Solo delivery, with no team to catch inconsistencies
Summary :
Impact & Results
The platform shipped as a 40+ screen banking system built on a single design foundation, delivered solo for a regulated financial institution, with the platform remaining consistent across every flow from onboarding through compliance reporting.
Key Learnings
Build the system before the screens, not alongside them
Consistency at scale depends on the foundation, not individual review
Regulated environments require the system to hold up under scrutiny, not just look polished
More Projects
Product Design
Meridian Bank Concept
Private Bank Concept
Year :
2026
Industry :
Banking
Project Duration :
2 Weeks
Problem :
As Product Designer, I designed a sovereign-grade digital banking platform for institutional clients of a regulated financial institution. The project covered onboarding, KYC, account management, and compliance reporting across 40+ screens, delivered end to end and solo — from discovery through developer handoff.
Solution :
I built the design system before designing individual screens: tokens, a typography scale, and a component library that every downstream screen would inherit. This let the platform scale to 40+ screens without losing consistency.
TOKEN-BASED DESIGN SYSTEM
Reusable tokens, typography, and components used as the foundation for every screen in the platform.
COMPLIANCE-ALIGNED FLOWS
Onboarding, KYC, and account management flows designed to meet the standards expected of a regulated institution.
COMPONENT LIBRARY
A shared component library that made adding new screens straightforward, without reworking existing patterns.
CONSISTENCY AT SCALE
Regular checks to confirm the system held up as more screens were added, rather than reviewing each screen in isolation.
DESIGN PROCESS
Delivered the full lifecycle solo: discovery, information architecture, interaction design, Figma system build, and developer handoff.
Challenge :
The platform needed to support 40+ screens for a regulated financial institution, spanning onboarding, KYC, account management, and compliance reporting. Without a shared system, projects at this scale typically become inconsistent across screens and difficult to maintain as they grow.
40+ screens required for full platform coverage
Regulated institution with strict compliance requirements
No existing design system to build from
Solo delivery, with no team to catch inconsistencies
Summary :
Impact & Results
The platform shipped as a 40+ screen banking system built on a single design foundation, delivered solo for a regulated financial institution, with the platform remaining consistent across every flow from onboarding through compliance reporting.
Key Learnings
Build the system before the screens, not alongside them
Consistency at scale depends on the foundation, not individual review
Regulated environments require the system to hold up under scrutiny, not just look polished