All work
WEALTH MANAGEMENT2017—25

Making complex financial workflows work for people.

Connecting enterprise UX and a scalable design system for investment professionals.

PROJECT

RedBlack Rebalance

MY ROLE

UX Lead · Redblack Software

TIMELINE

February 2017 — September 2025

REDBLACK / DESIGN SYSTEMBuilt to scale.
AaClarity at every scale.
Create portfolio Portfolio settings A shared source of truth
90+ components
THE CONTEXT

Start with the people.
Understand the problem.

RedBlack Rebalance is a portfolio management platform for continuous monitoring, compliance, cash and tax management, portfolio rebalancing, order management, and trade reconciliation. I led user experience strategy and front-end design across the platform.

THE CHALLENGE

Complexity is necessary. Confusion isn’t.

Investment professionals work across complex, interconnected workflows where consistency and precision matter. The design challenge was to simplify these tasks while maintaining the depth required by expert users and creating a shared foundation for product teams.

THE APPROACH

A clearer path from intent to action.

I connected user research, personas, journey maps, and information architecture with a scalable Figma design system. Reusable interaction patterns and developer-ready specifications helped bridge design intent and implementation.

01

Start with real workflows

Use interviews, card sorting, personas, and journey maps to structure the product around the work investment professionals actually need to complete.

02

Build a shared design language

Establish and maintain more than 90 reusable Figma components, bringing consistency to dense enterprise screens and a common source of truth to the team.

03

Close the delivery gap

Work alongside engineering in Agile teams, maintain HTML and CSS/SCSS foundations, and use Figma Dev Mode to make handoffs clearer and more practical.

THE THINKING BEHIND THE INTERFACE

Explain the product clearly. Make its patterns repeatable.

The portfolio covers two related but distinct challenges: complex financial product workflows and a public website that explains the offering. The website frames below are marketing artifacts, not screenshots of the rebalancing application.

DESIGNED FOR

Investment professionals evaluating the platform, and the teams designing and building it

A UX reading of the supplied artifacts. The sequence below explains the design logic, not a verified chronology of research. Intended benefits and proposed tests are not measured outcomes.

The user's path

  1. Understand the offering
  2. Explore relevant capabilities
  3. Evaluate the information
  4. Choose a next step
PROCESS & ARTIFACTS

How the problem becomes an interface.

  1. Separate discovery from daily use

    Website visitors need a clear explanation of the offering; investment professionals inside the product need precise operational controls. Keeping those contexts separate avoids applying the same navigation and information density to both.

  2. Establish an information hierarchy

    The website explores desktop, tablet, and mobile layouts. Its navigation and content sections provide a path through the information instead of presenting the entire product story as one undifferentiated block.

  3. Extract foundations and components

    The dedicated design-system and component pages separate shared rules from page composition. Buttons, navigation, cards, and pagination can then use a consistent interaction vocabulary.

  4. Check behavior across sizes

    The website page contains responsive layouts. The separate Responsive Test page is currently empty, so it is a place for future evidence—not proof that responsive testing has been completed.

THE ORIGINAL SCREEN

RedBlack · 01 / Desktop — 1440

1440 × 3729 · Exact source frame, not a recreated mockup.

A downloadable screenshot is not available in this portfolio yet. Open the original frame, or load its Figma preview below. Figma may require sign-in or block embedding.

View the original screen
Load original Figma frame
WHY IT IS DESIGNED THIS WAY

Every choice has a reason.
And a trade-off.

Differentiate utility and product navigation

The desktop frame separates contact information in a utility bar from the main navigation. This lets contact access remain available without becoming the primary reading path.

THE TRADE-OFF

Two navigation layers use vertical space. On smaller screens, retain essential actions without repeating every desktop link.

Use a shared component vocabulary

Reusable buttons, cards, and navigation make similar actions recognizable and reduce interpretation differences between design and development.

THE TRADE-OFF

A component library is not automatically usable. States, focus behavior, content limits, and implementation rules need documentation too.

Treat responsive layouts as priorities

Desktop and mobile frames allow the same information to be reorganized around available space rather than simply scaled down.

THE TRADE-OFF

A static frame cannot prove reading order or keyboard behavior. These need testing in the implemented experience.

REPORTED PROJECT IMPACT

A foundation that moves the team forward.

90+Reusable Figma components
80%Reduction in task completion time
70%Reduction in design and development effort

Figures reported in my professional experience. The design-system visual is a portfolio presentation, not a product screenshot.

BEHIND THE FINISHED SCREENS

Design presentations4 pages

Explore project presentations in Figma, without opening the working design file.

WEALTH TECHNOLOGY

RedBlack · Website & system

Website layouts, design foundations, and reusable interface components.

Read the UX process & rationale
  • Why this page exists
    Purpose
    Explain RedBlack through a responsive public website.
    UX rationale
    The website has a different job from the application: help a visitor understand the offering and choose a next step.
    Next check
    Test comprehension and navigation on mobile and desktop. These are website frames, not rebalancing-product screenshots.
  • Why this page exists
    Purpose
    Document the visual rules used across the RedBlack website.
    UX rationale
    A shared type scale, color palette, and spacing system preserve hierarchy and reduce arbitrary variation as pages grow.
    Next check
    Review semantic token use, long content, and contrast in real components.
  • Why this page exists
    Purpose
    Translate visual foundations into reusable interface patterns.
    UX rationale
    Buttons, navigation, cards, and pagination let designers and engineers reuse decisions rather than reproduce individual pixels.
    Next check
    Define hover, focus, disabled, loading, and error behavior where relevant; inspect keyboard and screen-reader support.
  • Why this page exists
    Purpose
    Reserve a dedicated space for responsive verification.
    UX rationale
    A separate test page can help compare breakpoints and edge cases without cluttering presentation layouts.
    Next check
    This page currently has no frames. Add long-content, zoom, and breakpoint checks before claiming responsive validation.
Browse all case studies
THE TAKEAWAY

Consistency is a team capability.

A design system is more than a component library. Its value comes from shared decisions, repeatable patterns, and a close relationship between research, design, and engineering. That foundation allows teams to spend less time recreating interfaces and more time solving the right problems.

NEXT PROJECT

NSE Intraday Opportunity Scanner

A real-time NSE scanner that ranks stocks with rule-based quantitative analysis and builds a full entry-to-exit trading plan for each one.

GOOD THINGS START WITH A CONVERSATIONKerala, India · Working everywhere

Have something
in mind?