William Bruno

Five tools. One platform.

FedEx ran five separate developer tools. As lead product designer at Tank Design, I led the work to consolidate them into one platform for thousands of developers worldwide.

lead product designer platform design biweekly research 2022–2024 at tank design fedex
The FedEx Developer Portal dashboard in a browser window on a purple background

goal

FedEx asked for better documentation. Research said developers were leaving before they ever opened the docs: the barrier was onboarding, not content. I argued for the bigger scope, a full platform redesign instead of a doc refresh, and won the budget to deliver it. The platform is live for thousands of developers.

The FedEx Developer Portal dashboard on a laptop
The FedEx Developer Portal on a desktop monitor
The FedEx Developer Portal on a phone, held in a hand

what we did

I led product and UX across the platform for more than two years, with a small design team on execution. Research ran on a biweekly cadence: internal rounds at Tank plus three independent studies with AnswerLab, across the U.S., Canada, the U.K. and India. A comparison matrix mapped every screen against every test, so findings went from the lab straight into the backlog.

The API status page layered over the post-login dashboard
FedEx Developer Platform illustrations: a handheld scanner and package, the test, learn and integrate steps, and a webhook diagram

Spot illustrations give a dense developer product a human voice: test, learn, integrate.

Close-up of the API catalog

show the value before asking for a login

Funnel data and research across six developer personas pointed the same way: developers couldn’t tell whether the platform was for them before they committed. So the pre-login experience answers three questions first: what can I build, how hard is it, and how good are the docs. Confidence first, commitment second.

The pre-login homepage with a value proposition and an API overview
The API catalog, with every API linked to its docs

The API catalog shows every API at a glance, each linked straight to its docs.

design the paths that don’t end in success

The webhook flow looked simple on the happy path, but webhooks touch billing accounts, shipping accounts and org permissions, and most real developers don’t arrive in a clean state. I designed eight non-success paths, from no billing account and no shipping account to a contributor without permission, plus a saved-in-progress lane so half-finished work was never lost.

Webhook project setup, step one
Webhook project setup, choosing shipping accounts
The post-login home across four states, from a new user to a full administrator

one notification system

A platform this dense generates a lot of system messages. Instead of letting every screen invent its own, I built a single authoring template for toasts, alerts, modals and gates: icon semantics, variable slots, button hierarchy and link text. One grammar now runs across more than sixteen production surfaces.

Toast, alert, modal and gate, all from one template.

a design system that grew with the brand

I led the design library updates for this initiative, designing new components that live inside FedEx’s 1DX design system. Weekly workshops with FedEx’s internal brand team kept the platform and the broader brand system evolving together.

The FedEx Developer Platform design library built on the 1DX system

mobile redesign

The mobile experience preserved the same confidence-building path: understand the platform, browse the APIs, and evaluate pricing before asking for a commitment.

pre-login
post-login
pricing guide

explore the architecture

The full information architecture is an interactive map. Move through the surfaces, from the pre-login pages to the org admin and the component library.

result

2.5 yrs

leading product and UX across the entire platform.

biweekly

research with real developers across multiple rounds, internal and AnswerLab-led.

11

PI design briefs across two product increment cycles.