Home Work About Contact
← All work
Infor Design System (SoHo) · Figma Library

Library Reorganization

My role & team

Role: Library Owner & Design System Lead. I was responsible for the full scope of the project.

Collaborators
· {{ c }}
Scale & context
{{ s.num }}
{{ s.label }}
Process
{{ p.n }} {{ p.step }}
Scope

Figma design library used by designers across multiple Infor product teams. The library reflects the SoHo / IDS Enterprise component codebase — changes here affect how designers work across products built on one of the world's largest enterprise ERP platforms (90,000+ customers, 58M+ end-users).

How current structure looks like?

The current Figma design system consists of a single file that includes:

· {{ c }}

Goal: The primary objective was to reorganize and clarify the structure of the main components list, as well as the "Internal Components" and "Charts and Data Viz" sections, to improve overall consistency and usability.

Components library — current index
Code, Figma and documentation perspective

In the codebase and documentation, there was a clear distinction between sections such as patterns, utilities, and charts. We aimed to introduce the same structure in Figma, which led us to take the following steps:

· Audit of the "Internal Components" section: identifying which elements should remain as components, which were unnecessary and could be removed, and which should be relocated to more appropriate sections.
· Review of the Data Visualization section: determining which elements were up to date and aligned with web components, and which belonged to an older enterprise version and should be marked as "legacy." This also included validating variants, removing duplicates, and ensuring consistency with the latest codebase.
Internal components audit

Each internal component was assessed against Web Components, Enterprise, Docsite and Figma — with a decision and rationale logged for every element (Busy Indicator, Cursor, Dirty Indicator, Footer, Overlay, Pointer, Selection Bar, Shell Icon, Vertical Menu Item, Date and Time, Swappable).

Component Web Components Docsite Figma Decision Rationale
{{ r.name }} {{ r.wc }} {{ r.docsite }} {{ r.figma }} {{ r.decision }} {{ r.rationale }}
Or drop the original audit table screenshot
Data Viz section

While working on the data visualization section in Figma, we focused primarily on aligning our library with what exists in the WC codebase. We had around 30 elements, many of which variants represented the same component in different variations. From a design system perspective, it was inefficient to display and maintain every variant separately in Figma. Therefore, we decided to focus on core components and group their variants under them, which improves clarity and navigation.

Additionally, we renamed the section to "Charts" to maintain consistency with the documentation site, and moved it to the bottom of the component list, under the "Utilities" section.

Decisions

Create a page for:

{{ c }}

Rename section to "charts library".

Example of final page for chart
Reorganization results

New section for charts created

· {{ c }}

Elements moved to components section

· {{ c }}

Removed elements

· {{ c }}

New section for other elements created

· {{ c }}
Impact

Before → After

Outcomes of the library reorganization for the IDS Figma library and the teams that use it.

Before
· {{ c }}
After
· {{ c }}
Governance signals

{{ g.title }}

{{ g.text }}

What I would scale next
· {{ c }}
Next project
Engineering and Construction →
All work