Design System Lead at Oracle
Building the design system foundation for one of the world’s leading enterprise SaaS platforms.
Design System Architecture
I led the architecture of the design system foundations, defining the principles, tokens, accessibility standards, and component framework needed to support a scalable and consistent product experience.
Linked Libraries
Interconnected design libraries enabled multiple product teams to work from a single source of truth, ensuring consistency across products while reducing duplication and maintenance overhead.
Source of Truth
To drive adoption, I created a dedicated design system hub that centralised documentation, components, guidelines, and tools into a single source of truth for design and engineering teams.
Design System Delivery
Creating the design system was only part of the challenge. Success depended on driving adoption across more than 50 independent product teams, each with their own workflows, priorities, and requirements. Through a structured discovery and validation process, we developed a scalable framework that could be adopted consistently across the wider NetSuite product ecosystem.
A design system only succeeds when teams adopt it. The focus of this phase was validating the system and creating a scalable model that could be successfully adopted across more than 50 independent product teams.
Dashboard Design
As an extension of the design system, we’ve begun kicking off the next-generation UI dashboards experience, advancing the interface with improved layouts and updated interaction patterns.
-
Seeing as we were transitioning from Legacy we needed a new base "Shell" into which the Dashboard pieces would fall.
Here is an early sketch showing the main components that would form the Dashboard shell: Local Navigation, Tabular screens (for comparisons), grid tools, grid layouts, notifications area, marketplace for dashboard widgets and modals for SPA interactions. It was to be a Single Page Application architecture and everything needed to be "on hand".
-
On top of the infrastructure, inside the Grid, we would be placing our Dashboard Widgets, which would come from the Library/Marketplace (the name wasn't finalised). Widgets could come individually, or in logical groups. The layout is customisable by the user.
-
We wanted elements of "Intelligence" to be incorporated into the dashboards, such as the below suggestion which would leverage the Oracle Netsuite data universe for comparative benchmarking, and other more banal examples like, for example: Auto-approving expenses - a boring, detail-heavy and time-consuming job for managers.
-
We demoes a very early iteration as a concept at SuiteWorld 2018: giving a flavour of what was in the works to Oracle Netsuite customers at their annual conference..
Intelligence baked in.
We wanted elements of "Intelligence" to be incorporated into the dashboards, such as the below suggestion which would leverage the Oracle Netsuite data universe for comparative benchmarking, and other more banal examples like, for example: Auto-approving expenses - a boring, detail-heavy and time-consuming job for managers.
Concept Demo at SuiteWorld Conference.
We demoed a very early iteration as a concept at SuiteWorld 2018, offering attendees a preview and sense of what was in development for Oracle NetSuite customers at their annual conference.
Watch the demos below.
