← BACK TO CASE STUDIES

CASE STUDY 06 · PAYPAL · 2019–2024

The Redesign
Nobody Had a Plan For

A new CDO arrived with a bold platform vision and no implementation framework. I built the decision pipeline, the compliance scaffolding, and the cross-org alignment process that turned concept into something shippable.

0

EXISTING REVIEW PROCESS

4+

FUNCTIONS REALIGNED

Global

COMPLIANCE FRAMEWORK BUILT FROM SCRATCH

THE SITUATION

The vision arrived before anyone had a plan.

A new Chief Design Officer arrived with a mandate to reinvigorate PayPal's consumer product following a period of post-pandemic decline. Early conceptual explorations — ambitious, forward-looking, genuinely exciting — were shared with the C-suite before the broader design org had context for them. The result was significant: leadership alignment gaps, teams working from different assumptions, and a growing disconnect between what had been shown to executives and what was buildable at scale.

Nobody was wrong in this situation. The new CDO was doing what new CDOs do — establishing a vision, generating momentum, signaling ambition. The problem was structural: the org didn't have the machinery to translate that vision into coordinated execution. Decisions were being made in multiple directions simultaneously. Compliance, engineering, and product had no shared framework. And the design work itself — strong at the concept level — had no pathway to become a system.

On the stabilizing role during a major redesign initiative: My job was not to redirect the vision. It was to build the infrastructure that made the vision real — without losing what made it worth pursuing in the first place.

WHAT I BUILT

Four things the org needed and didn't have

Decision pipeline — before and after
No process
Structured pipeline
Before — fragmented execution
C-suite
Concepts released without context
Executive explorations shared before design org could frame them. Teams working from screenshots, not briefs.
Design org
No shared system model
Designers interpreting the vision differently. No components, spacing rules, or compliance variants defined.
Compliance / Legal
Not in the room
Statutory requirements not yet mapped to the new system. Risk of non-compliant designs reaching production.
Engineering / PM
No review pipeline
Decisions made in parallel without coordination. No single source of truth for what was approved or blocked.
Result:
Momentum without direction. Work duplicated, contradicted, or stranded without a path to production.
Vision was strong. Infrastructure was absent.
Stabilization → structured execution
After — structured decision pipeline
1
System framework — components, spacing, interaction model
Conceptual explorations translated into buildable specification. Defines what the vision means as a shippable system.
↓
2
Compliance scaffolding — disclosures, regional rules, accessibility
Statutory requirements mapped to new system components before design scaled. Constraints understood early — not discovered at engineering review.
↓
3
Cross-org review pipeline — decisions tracked and communicated
Weekly cross-functional reviews. Decision logs documented and distributed. Escalation paths clarified. One source of truth across design, PM, engineering, and leadership.
↓
4
Designer development — ownership, escalation, cross-functional influence
Initiative used as a growth environment. Designers assigned explicit ownership areas and coached in high-pressure communication.
What became real
A scalable, compliance-safe system framework. Leadership's vision became actionable without losing its ambition.
What persisted
The pipeline, compliance docs, and designer capabilities outlasted the initiative — adopted as standard operating procedure.

Concept ≠ system

Executive-level design explorations are built to inspire, not to ship. Translating inspiration into a buildable, compliant, globally-consistent system is a distinct skill — and the one the org needed most.

Constraints as design inputs

Compliance, legal, and accessibility requirements were surfaced early and mapped to the system — not discovered during engineering review. This protected the initiative's momentum and prevented last-minute design pivots.

Stability is a deliverable

During leadership transitions, the most valuable thing a design leader can produce isn't a new feature — it's a functioning organization. Keeping the team grounded, aligned, and moving with integrity was the outcome.

OUTCOMES

What the audit and governance produced

1

Decision pipeline built from nothing — cross-org review process that coordinated design, PM, engineering, and leadership

X-func

Compliance framework covering credit disclosures, regional rules, and accessibility — mapped to the new system before design scaled

Durable

System framework, review process, and designer capabilities that outlasted the initiative and strengthened the org's ability to execute independently

THE DISTINCTION THAT MATTERS

This case study isn't about the redesign. It's about the infrastructure that made the redesign possible. The features shipped under this initiative matter less than the decision-making capacity, compliance fluency, and design team confidence that were built alongside them — and persisted after the initiative concluded.