Business Analysis · Product Ownership · UI/UX

Legacy Platform & Design System

Rebuilt a legacy investment platform around one cohesive design system

Rebuilt a legacy investment platform around one cohesive design system

Role

Project Manager & Business Analyst

Timeline

2024 – 2026

Team

4 concurrent projects, teams of 3–8

Domain

Investment Banking / Industrial Parks

Methods and Tools

Figma, design system, design-first workflow, roadmap prioritization

4

Concurrent projects

1

Unified design system

Development rework

Overview

A legacy investment platform had drifted into inconsistent patterns and slow delivery. I introduced a design-first workflow requiring stakeholder validation of Figma prototypes before any code was written, then built the design system that unified the product — cutting development rework across four concurrent projects.

The Problem

A legacy investment platform had drifted. Years of incremental additions by different teams left inconsistent patterns, duplicated components and a UI that no longer matched how the business actually worked.


That inconsistency was expensive in delivery time. Every new feature restarted the same debates about layout and behaviour, and rework surfaced late — after code had already been written.

My Approach

Running four concurrent projects across investment banking, industrial parks and FinTech, I translated business goals into clear requirements and owned roadmap prioritization across teams of three to eight people.


The central decision was process, not visual. I introduced a design-first workflow: no development starts until stakeholders have validated a Figma prototype. That moved disagreement to the cheapest possible point in the cycle.

The Design

I built a cohesive design system for the platform — shared components, consistent spacing and a single set of interaction patterns — and applied it across the revitalized product.


Rather than a big-bang redesign, I sequenced adoption so the highest-traffic flows moved first. That kept the platform shippable throughout and let the system prove itself before it was mandated everywhere.

Impact

Development rework dropped measurably once prototypes were validated before coding, and four concurrent projects stayed coordinated on one visual language.


The design system outlived the individual projects: new work now starts from established components instead of a blank canvas.

Razvan™

Razvan™

Razvan™

Razvan™

Copyright © Razvan 2026