AI-generated cover illustration. Project screens are shown below.
One system for complex decisions.
Auditing data applications and documenting reusable interface patterns within Palantir Foundry’s design and implementation constraints.
Lead UX research & design / Public case-study material only
01 / Context & constraints
Improve the experience within Foundry.
FORVIA used Palantir Foundry applications to support industrial analysis. Related applications could present navigation, filters, metrics and actions differently, forcing users to reinterpret the interface when moving between tasks.
The constraint was the Palantir ecosystem. We worked within its existing application environment and available interface capabilities. This was not a blank-canvas redesign: the design system had to guide implementable choices, not promise unrestricted custom components or behavior.
From May 2023 to June 2025, my work included end-to-end UX audits, design-system creation and documentation, dashboard design, feedback-led iteration and workshop facilitation with R&D stakeholders.
02 / System decisions
Standardize what teams could reuse.
I organized guidance around foundations, page structure and repeatable interface patterns. Navigation establishes location; filters define the analysis context; metrics summarize it; charts and tables support inspection; actions remain distinct from those information controls.
Documenting usage examples and dos and don’ts helped designers and developers work from the same rules. The value was consistent composition within platform limits, rather than visual novelty for its own sake.
Tradeoff: consistency cannot mean making every analysis page identical. Shared patterns provide orientation while the main content reflects matching, weight or part-composition tasks.
03 / Application examples
Show the system in real task contexts.
The SAMBA screens show the patterns applied to matching performance, weight analysis and part composition. They are stronger evidence than an unconfigured dashboard template because they show how filters, summaries and detailed analysis are composed around a task.
My design focus was the relationship between scope and result: users need to know which context a metric describes and which control changes that context. Layout and emphasis therefore serve interpretation, within the structures the platform makes available.
These examples demonstrate UI application. They do not, on their own, prove faster decisions or fewer operational errors.
04 / Collaboration & delivery
Connect domain knowledge with design rules.
Audits and stakeholder feedback informed the interface work. R&D workshop facilitation in Paris Nanterre created a setting for discussing domain workflows and design priorities. I translated those conversations into dashboard decisions and reusable guidance.
The deliverable combined documented foundations, component usage and application examples. It gave teams a reference for reviewing new interfaces against existing patterns, while recording where a task required a different arrangement.
Palantir constraints made prioritization important: improve hierarchy and consistency where the platform supports them, and surface implementation limitations rather than conceal them behind a polished mockup.
05 / Outcome & reflection
A reusable basis for constrained design.
This work demonstrates enterprise UX auditing, dashboard design and system documentation within an existing platform. The added value is a common interface vocabulary tied to concrete application examples.
Adoption across all FORVIA applications, engineering time saved and improvements in user performance are not quantified by the public material. I would evaluate reuse and representative analysis tasks before making those claims.
For the next iteration, inspect whether users can identify the active filter context, interpret a metric and move into relevant detail. Track repeated pattern exceptions to distinguish gaps in the guidance from limits of the platform.
The first gesture
Have a good challenge?Let’s talk.