CASE STUDY 06 · PAYPAL · 2019–2024
Bringing Coherence to a Company-Wide Reinvention
How I built the operating model that let dozens of teams execute against an ambitious, still-forming product vision without fragmenting.
The Challenge
PayPal's stock surged through COVID and then settled back, and that swing brought new ambition at the top. A new product leader arrived, and then a new Chief Design Officer. Both wanted to move the company past its identity as a digital wallet and toward something larger: an ecommerce aggregator where a customer's financial life and shopping life could sit in one place. PayPal already saw the customer across dozens of silos, and the bet was that this view could make it central to shopping itself, the way it had already become central to payments.
To set direction, the new design leadership produced and circulated six high-fidelity core screens, a polished picture of the reinvented experience. The intent was provocation: pull the organization out of its assumptions and ask what the product could become. But six screens were being asked to carry a lot. They had to force new thinking, stand in for a strategy, work through the regulatory questions, square against the products that already existed, and lock the new look and feel, all at the same time. They were key screens built to sell a direction, not yet a working system, and they ran against the strategy the teams were already executing.
That collided with how the company read high-fidelity work. By convention, screens at that level were production-ready, with the strategy and interactions behind them already vetted. So when these "what if" screens reached product, engineering, and PMO first, and without caveats, everyone reasonably assumed the thinking behind them existed somewhere and that design was holding it. Design hadn't seen them either. We were as surprised as anyone.
By the time the work reached the design teams, momentum had gathered, and an expectation had formed with it: design would carry the vision the rest of the way. That expectation was fair. Turning a brand-level vision into something regulated and buildable is exactly the kind of problem design should own. It was also hard, and a lot was still open. How settled the strategy really was stayed unclear, and so did the question of how any of it would get built. Leadership, product, engineering, PMO, and compliance each had a different picture of what success looked like, and the work had to hold all of them together at once. That was the challenge.
Approach
The mockups were never the real problem.
The real problem was that an ambitious vision had landed with no operating model to turn it into coherent, reviewable, buildable work. That gap was where I focused, building the machine that could produce the redesign rather than just producing screens. It came together as five moving parts, built in parallel.
1 · A DECISION SPINE
I worked with my ladder-up, who carried the work to the Chief Design Officer, to settle how reviews and decisions would be made. We anchored on one rule that did more structural work than it looked like: every walkthrough would start at the PayPal Dashboard and build outward.
Dashboard
Every product had to resolve into something the Dashboard could display. The review protocol and the system architecture became the same thing.
The Dashboard was my team and a live aggregate of nearly every product, so anchoring reviews there made it the integration point for the whole strategy
2 · A PRODUCTION ENVIRONMENT: THE DESIGN PLAYBOOK
None of this could run without shared infrastructure, so we built a structured Figma workspace that worked as both a set of team sandboxes and the single design source of truth. Every component became a configurable element, and the Dashboard was built first and built to receive.
Each team fed back into the Dashboard as a preview, heads-up display, peek, or empty first-time state, plus growth placements routed into progressive onboarding
3 · A DESIGN SYSTEM REBUILT AND PRESSURE TESTED MID-FLIGHT
All of it had to be skinned against a design system that was getting rebuilt at the same time, underneath us. The five-person design system team carried an enormous load, and the work moved in a tight bidirectional loop.
System and application moved in the same loop, neither waiting on the other to finish. One of the new ways of working the mandate had asked for.
4 · A COMMUNICATION LATTICE
Coordination on this scale doesn't happen by accident, so I built the structure for it. Everything was designed to pyramid upward, so the work rolled up cleanly enough that leadership could walk the rest of the C-suite through it on a separate cadence, without me in the room.
5 · CROSS-CUTTING WORK
Layered on top were initiatives that cut across every team.
ILLUSTRATION REFRESH
Built the inventory and repository the illustration team worked against, tracking where each asset lived, when and why it appeared, and what it needed to convey, in close partnership with content strategy.
PMO MOVE TO ASANA
Prior to this, PMO did not work with design. The design team was given estimates for their own work as dictated by product and dev partners into PMO's spreadsheets. When the PMO chose to move off spreadsheets to unblock itself, I worked alongside them to populate the new system from the design vantage point.
Legal & Compliance
Ran working sessions to keep the vision tied to regulatory reality, plus full-stack reviews pairing my design, engineering, and PM leads with their counterparts on the partner teams. We'd always had these reviews, but not on a quick cadence. Our legal partners welcomed the opportunity to have input into the product early and often, which built additional trust.
Outcome
The primary output of this project was operational.
New ways of working outlasted the initiative, and enabled a more nimble and integrated product design process. Not just the design team, but all of our partners in product, engineering, project management, analytics, and legal.
New working trust
Newly instituted cascading reviews, run on a tight clock, did something the vision work couldn't: Teams previously operating in silos, with their own PMs, roadmaps, and metrics, gained perspective of the whole, and they saw it weekly.
The Design Playbook
This easy to use drag-and-drop build system anchored around the Dashboard encouraged anyone with need to assemble a contextually accurate page of the app across regions, languages, account states, and user types.
However…
The aggregator vision as originally proposed did not ship, and the broader effort was overtaken by organizational restructuring before it fully played out. A few design changes surfaced in the year or two after. What lasted was the operating model: the decision spine, the Playbook, the review cadence, and the relationships, all of which worked as designed for as long as the organization around them held together.
Hindsight
Build the machine. Also force the question.
WHAT I'D DO DIFFERENTLY
I would have pushed earlier to make the strategy's open questions explicit and shared, instead of letting them sit as things for design to quietly work around. The team was good at producing coherent work against a moving target. We'd have been more effective if I'd gotten leadership to name up front what had to be true, regulatorily and technically, for the vision to ship, and to treat those gates as leadership decisions rather than design puzzles.
A LESSON
Building an operating model to keep 9 teams aligned was good. Pairing it with harder, earlier conversations about strategic readiness would have been better, and made the whole effort more durable.
WHAT THIS PROVED
Bringing coherence to a large organization in motion is the part of design leadership hardest to read off a portfolio of finished screens. It only shows up when the work is fast, ambitious, and not yet settled.