Noelle A Moncibaiz
SLB · GLOBAL DESIGN LANGUAGE SYSTEM
A scalable design system that gave six platforms a shared foundation while preserving the flexibility each brand needed.
Role
Visual Designer, UX Research
Focus
Design Systems & Accessibility
Process
Research → Define → Structure → Design → Validate
SLB needed a design system, a framework that combines the set of reusable components, standards and documentation prodiving consistency in the products, streamlining design and development, and improving productivity. In short, SLB needed a standard that served as a bridge between various teams.
It's simple, SLB needed 1 design language so everyone is on the same page. Through 2019, Schlumberger (SLB) lacked any formalized design system. Brands existed on the web as separate identities with individual teams creating their own source of standards for UI elements, components, or modules–in both internal or outside agencies.
01 No shared source of truth
Teams and agencies maintained their own UI standards.
02 The same problems were solved repeatedly
Common components were recreated across products.
03 Brand consistency broke at scale
Without shared foundations, products increasingly looked and behaved differently.
Consistency couldn't come at the expense of brand identity
With multiple products and brands sharing similar needs, one rigid UI library wouldn't work. We needed a shared foundation for accessibility, interaction, and structure while giving each brand room to maintain its own identity.
One foundation. Different products, workflows, and interfaces.
03 FOUNDATIONS
Start with the rules everything else depends on
Color with a purpose
Each palette performing specific functions.
-
Neutral Palette:
Structure & hierarchy
-
Theme colors:
Brand expression
-
Semantic Colors:
Status & feedback
Color Contrast
Contrast standards were built into the system to keep text, controls, and interaction states accessible across brands and themes.
Typography built for clarity
ROBOTO
Roboto provided a consistent, highly readable foundation across dense enterprise interfaces, different screen sizes, and multiple products.
04 COMPONENTS
Reusable wasn't enough. Behavior had to be predictable.
Components were designed not only for visual consistency, but for predictable behavior across products, breakpoints, interaction states and input methods.
05 PATTERNS
A component library wasn't enough.
Teams also needed guidance for combining individual components into repeatable product experiences. Patterns established shared solutions for common workflows while still allowing teams to adapt them to their product needs.
06 ACCESSIBILITY
Accessibility wasn't an afterthought. It was part of the system.
Accessibility was built into the design system from the start, from color contrast and interaction states to keyboard behavior and component guidance. We documented these standards alongside each component so teams could design and build accessible experiences consistently, rather than addressing accessibility at the end.
07 Governance and Documentation
A design system only works if teams can actually use it.
We created a shared source of truth for designers and developers, documenting component usage, accessibility standards, design principles, and implementation guidance. Governance gave teams a clear way to adopt the system while keeping it consistent as products evolved.
08 IMPACT
From disconnected products to a shared design language.
What started as a need for consistency became a scalable design system supporting six platforms. Shared foundations, reusable components, accessibility standards, and governance gave teams a common language for designing and building products while preserving the flexibility each experience needed.
6 PLATFORMS
Supported by a shared design system
ONE FOUNDATION
Common components, patterns, and standards
ACCESSIBILITY BUILT IN
Standards established from the start
BUILT TO EVOLVE
Documentation and governance supported continued adoption