Hey...

Figma Migration

Figma Migration

Figma Migration

From Fragmented Workflows to a Unified Design System

From Fragmented Workflows to a Unified Design System

From Fragmented Workflows to a Unified Design System

A mockup of a Macbook on a sofa
A mockup of a Macbook on a sofa

When HP’s printer software team faced growing pains with their Axure-based workflows, the cracks began to show. Designers worked in silos, components were inconsistently reused, and developer handoffs became tedious guesswork. Our mission was clear: migrate the entire design system to Figma - not just as a tool switch, but as a transformation in how the team created, collaborated, and scaled UX for HP’s global printer software. The goal wasn’t just to rebuild, but to reimagine - turning disjointed assets into a living, breathing design system that could evolve with the product.

Client:

HP

My Role:

Interaction Designer

Year:

2024

Service Provided:

Strategic Planning, Design Inputs

We started by dissecting Axure’s legacy components, treating the migration like an archaeological dig - each layer revealed outdated patterns and hidden inconsistencies. In Figma, we rebuilt the system atom by atom, establishing strict naming conventions, auto-layout rules, and variant-driven components. The real breakthrough came when we trained the team: suddenly, designers who once struggled with version conflicts were co-editing in real time, and developers could inspect specs with a single click. What began as a tool migration became a cultural shift - proving that the right system doesn’t just store components; it unlocks a team’s potential.