Product ecosystem × design systems × engineering
One system. Three product experiences.
At Bottle Rocket, I helped lead design across ShopRunner experiences for FedEx, spanning a consumer shipping and returns app, responsive marketplace experiences, and a B2B merchant dashboard—supported by a shared design system built for close design-to-code alignment.
The opportunity
Create one coherent product language across very different customer journeys.
The work stretched across consumer shipping and returns, marketplace experiences, and merchant-facing tools. Each product had different tasks and audiences, but they still needed to feel like parts of the same ecosystem.
That made consistency a product problem as much as a visual one: patterns needed to work across native and responsive environments while remaining practical for engineering teams to implement and maintain.
The product landscape
Three distinct experiences created three different kinds of design pressure.
The challenge was to support each product on its own terms without allowing the ecosystem to fragment into unrelated interfaces.
The idea
Build the system around shared product behavior, not superficial sameness.
We treated the design system as a common language between products and between design and engineering—reusing what should be shared while allowing each experience to respond to its own users, workflows, and platform constraints.
How might one system create continuity across a consumer app, marketplace, and merchant platform without making them feel identical?
Building Bolt
A shared design system designed to stay close to production.
The Bolt design system connected reusable Figma components with Storybook implementation, creating close design-code parity and a more dependable shared reference for designers and engineers across the product ecosystem.
System in action
Shared patterns, adapted to very different workflows.
The system created continuity without forcing every product into the same composition.
Consumer shipping flows prioritized clarity and task completion. Marketplace experiences needed responsive commerce behavior. Merchant tools required denser operational interfaces. The system provided enough structure to connect them while leaving room for each product to solve the right problem.
Design + engineering
The system became a shared contract between disciplines.
Maintaining close parity between Figma and Storybook reduced ambiguity between intended design and implemented components. The value was not just consistency on screen—it was a clearer operating model for teams building multiple products together.
Scale + impact
A product system that connected experience design with the way teams actually built.
The work established a coherent design language across consumer, marketplace, and merchant experiences while creating close Figma and Storybook parity for the teams responsible for carrying that language into production.