Scalable DS patterns for denser screens: faster dev, fewer debates, and data‑dense reports across 4 portals.
Institutional portal for Asset Management, heavy on reports and holdings for decision‑making.
Overview
I joined the Asset Management team to help adapt their new Design System language to it’s primary tools that builds unified client experience for their internal users and external clients.
Timeline
2024 - 2025
Team
Product, Design, Research & Engineering
Contributions
Product Design (B2B), Design System
Context
Institutional portal for Asset Management : heavy on reports, account holdings, risk analysis and access to Investment Dashboard.
Goal
Reduce decision overhead for expert users without diverging from the system’s components or tokens.
Problem
DS guidance overlapped components and patterns, and the tool header used 30% of page, hiding data
Insights
Expert users scan dense tables; they need high information density and a predictable place for heavy‑use exports.
Approach
Collaborated across portals to map core journeys and define DS‑aligned patterns that are required, optional, or conditional, resolving component overlap.
Scalable Design System patterns for denser screens: faster dev, fewer debates, and data‑dense reports across 4 portals.
Institutional portal for Asset Management, heavy on reports and holdings for decision‑making.
Timeline
2024- 2025
Team
Product & Engineering
Contributions
Design System Patterns & Interface Design
Overview
I joined the Asset Management team to help adapt their new Design System language to it’s primary tools that builds unified client experience for their internal users and external clients.
Context
Institutional portal for Asset Management : heavy on reports, account holdings, risk analysis and access to Investment Dashboard.
Goal
Reduce decision overhead for expert users without diverging from the system’s components or tokens.
Problem
DS guidance overlapped components and patterns, and the tool header used 30% of page, hiding data
Insights
Expert users scan dense tables; they need high information density and a predictable place for heavy‑use exports.
Approach
Collaborated across portals to map core journeys and define DS‑aligned patterns that are required, optional, or conditional, resolving component overlap.
👁️
Due to confidentiality with regulated finance clients, this project is shown in a limited format.
Portfolio reviewers can request a private walkthrough to view process, rationale, and outcomes.
Older Institutional Portal Header
Low Adoption rate
Dated Interface
Design System Suggested Header Pattern
Design System Suggested Header Pattern
Long Header
Earlier Header Variant
Inconsistent Styling
New Institutional Portal Header
Compact Header
Dated Interface
Header Variant from Advisor Portal - Tools
Header - Value Added Connect - Profile
Header - Institutional Portal
Results
Speed: fewer design debates, faster builds via component reuse, and one‑place exports that cut steps.
Scale: patterns applied across the reports and ready for adoption in 3 additional AM portals.
Results
Speed: fewer design debates, faster builds via component reuse, and one‑place exports that cut steps.
Scale: patterns applied across the reports and ready for adoption in 3 additional AM portals.
Have something for me?
Let’s Chat
© 2025 Anuj Arora
Have something for me?
Let’s Chat
© 2025 Anuj Arora
Have something for me?
Let’s Chat
© 2025 Anuj Arora