Palette and navigation
A defined white, blue, sky-blue, dark-grey, and light-grey palette creates a controlled base for navigation and data emphasis.
One system for complex decisions.
Leading the process, people, and system behind clearer industrial decision-making across FORVIA's Palantir ecosystem.
Lead UX research & design / Public case-study material only
01 / Why it mattered
Valuable data.
Fragmented rules.
FORVIA teams were using Palantir applications for manufacturing and business decisions, but different modules could introduce different layout logic, hierarchy, components, and scanning patterns.
The goal was a shared operational grammar: make dense industrial information easier to read while giving product teams a reusable system for future landing pages, dashboards, and workshop tools.
I led the work across audit, process definition, designer critique, stakeholder alignment, and R&D workshops in Paris Bercy and Nanterre. The same role extended into executive presentations and photo and video storytelling for innovation initiatives.
02 / The system
A shared
operational grammar.
The design system documents the interface from foundations upward: FORVIA palette, web landmarks, headers, navigation, card structures, filters, metrics, tabs, tables, charts, and action patterns.
Templates carry those rules into complete landing pages and data-heavy dashboards so a team can see how components behave in context, not only as isolated library pieces.
03 / Documentation model
From tokens to
working products.
The documentation is organized to answer four practical questions: what visual rules govern the product, how pages are structured, which components teams can reuse, and what the system looks like inside a live operational application.
Landmarks before decoration
Banner, header, main content, cards, side filters, and dashboard regions establish predictable reading and interaction zones.
Reusable controls at scale
More than 30 documented buttons, tabs, metric cards, actions, and information patterns form a common interface vocabulary.
SAMBA as system proof
Matching, weight, and part-composition dashboards demonstrate the library against real analytics and industrial decision flows.
04 / Deliverable
Consistency is a
product capability.
The deliverable creates one source of truth across foundations, components, structural patterns, and complete page templates. Designers and developers can evaluate new screens against a documented system rather than reinventing the interface each time.
In enterprise software, consistency is operational: the system makes dense applications more predictable and gives future modules a clear place to start.
The result was not only a component library. It was a shared design process: a way for designers, developers, product owners, and R&D stakeholders to discuss quality using the same language.
The first gesture
LET'S MAKESOMETHING FELT.