NEO — WiseTechENGINEERING

The systems cut — custom components inside a shared design system.

ROLE
Senior designer
WHEN
2024–2025
STATUS
Shipped
IMPACT
+29% React code consistency (shared components)
#React#TypeScript#Figma

The three tracks only held together because they shared a spine. Neo ran its own spin on the org-wide design system: Supply, WiseTech's token-based system, decoupled from Vuetify. My job on the systems side was building custom components where the customers needed a better experience than the defaults gave them, without breaking out of Supply's constraints. Getting a component both right for the user and standards-compliant was as much an org problem as a design one.

The warehouse order screen: grids, drawers, and toolbars all drawn from the shared component set

The negotiation loop, and the one hard number

Every shared component ran a negotiation loop: the product designers on each track, the designers who own Supply, the devs who maintain Supply, the devs building each product, and back to the product designer. Holding that loop together is where the systems work actually lives. The measurable result of that discipline was +29% React code consistency across the shared components — the single hard metric on this project, and a systems one by nature.