PayPal · Case study
Elevating the developer experience.
- Information Architecture
- Design Systems
- Developer Experience
- Content Strategy
- Research Synthesis
- Cross-functional Leadership
- Role
- Lead UX Designer
- Team
- Developer Experiences
- Timeline
- 2020 — 2021
- Platform
- Web · Documentation · Tooling
Overview
A platform foundational to online commerce, with a developer experience that had fallen behind.
Developer Experience had never carried a dedicated design function. Documentation, tooling and onboarding had been built independently, each on its own IA, components and voice.
External research and partner feedback consistently flagged the surface as fragmented and dated. The mandate was to bring integrating with PayPal up to the standard of the consumer product.
Pre-redesign portal: inconsistent layouts, type systems and IA models running in parallel.
Strategy
Three pillars set by leadership, and a fourth that did most of the real work.
- 01
Unify the documentation
One IA and one design system across 1,700+ developer doc pages.
- 02
Simplify onboarding
Reduce time-to-first-call. The first hour of integration should be a clear path, not a search problem.
- 03
Enhance self-service
Shift volume from support tickets to in-product resolution: stronger search, working examples, real sandboxes.
- 04
Align with the modern PayPal
Bring the developer surface up to the quality bar of the PayPal 2.0 brand and consumer product.
Research
Decisions calibrated by research, not org chart.
The program ran a mix of methods against the open questions: internal and external focus groups, card sorts and tree tests against new IA prototypes, and a short developer diary study. Synthesis was iterative, not a one-shot debrief.
The output was a developer journey covering discovery, integration, launch and maintenance. It became the artifact every subsequent design decision was tested against.
Design
From IA reset to a working Payment Simulator.
The work spanned IA, search, typography, documentation templates and the in-product testing experience. Three moments are worth calling out.
A unified IA and design system across the developer surface
1,700+ pages of documentation, satellite tools and onboarding flows were consolidated under a single IA and a shared component library. Type ramps, navigation grammar and content patterns now run consistently end to end.
Strategy pillars grounded in developer research
The pillars were derived from the journey work, diary studies and tree-test data, not from a workshop. Each carried a measurable bet, and every downstream decision had to ladder back to one of them.
A Payment Simulator that collapsed 24 steps into 9
Standing up a test environment previously required 5 platforms and 24+ screens. The new side-by-side simulator pairs GUI controls with live code under a single URL and pre-issued sandbox credentials, cutting the path to a first successful call by more than half.
Outcome
Shipped across the developer surface, not just the landing page.
88+
page templates shipped
10+
navigation IA iterations tested
24 → 9
steps to a working sandbox
1,700+
docs unified under a new IA and design system
Reflection
The hardest part wasn’t the design system.
It was getting documentation accepted as a first-class product surface. Once that shifted internally, the IA work, the typography system and the simulator stopped being debates and became execution.
The artifact I still reach for from this program is the prioritization matrix. Its value was less the content than the act of forcing cross-functional partners to agree, in writing, on what mattered most.
Previously
No earlier case study yet
Next case study
Under Armour Unified Profile →