CASE STUDY 02 · PAYPAL CONSUMER · 2019–2024
Bringing Coherence to a Company-Wide Reinvention
Thoughtful design process can help stabilize even a giant company during times of chaos.
THE PROBLEM
Leadership shakeup, ambiguous strategy, and tight timelines
PayPal's stock surged through COVID and then settled back, and that volatility brought new ambition at the top. A new C-Suite including Chief of Product and a new Chief Design Officer, both wanting to move the company past its identity as a digital wallet toward something broader: an ecommerce aggregator, a single place where a customer's financial and shopping life could sit together.
To set the direction, the new design leadership produced a high-fidelity branding exercise. It was a polished vision of the reinvented experience with newer, lower-fidelity strategy sketched underneath it. The intent was to provoke in a useful way, to pull the organization out of its assumptions and ask what the product could be instead. It was ambitious and deliberately unfinished, and it carried a clear challenge to everyone downstream: take this and make it real.
That challenge reached engineering and product first. By the time it got to the design teams, momentum had built and an expectation had set with it, that design would be the function to carry the vision the rest of the way. That was a reasonable expectation, since translating a branding-level vision into a working, regulated, buildable product is the kind of problem design is supposed to own. It was also a hard one. The vision was aspirational by design, the strategy beneath it was still forming, and the route from concept to a shippable global product ran through a stack of real constraints: regulatory requirements, the full inventory of features that already existed, and a design system that would have to be rebuilt to support the new look.
There was genuine ambiguity to sit with. How settled the strategy actually was remained unclear, and so did the question of how it would get built. On top of that, leadership had brought an explicit organizational challenge, a "new ways of working" mandate that was as much about reinventing how the teams operated as what they shipped. So the assignment had two halves at once: bring an unfinished vision down to earth, and rethink the process used to do it.
THE APPROACH
Some sort of cute headline
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.
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. The Dashboard was one of my teams, and it functioned as a live aggregate of nearly every other product in the app, so that rule quietly turned my own surface into the integration point for the whole strategy. If a team's work couldn't resolve into something the Dashboard could show, that became visible fast. The review protocol and the system architecture ended up being the same thing.
A production environment. None of this could run without shared infrastructure, so we built a structured Figma workspace called the Design Playbook that worked as both a set of team sandboxes and the single design source of truth. Every product team's work was structured the same way. Each component became a configurable element with variants for region and language, account age, engagement and activity level, product options, and user type. The Dashboard was built first and built to receive, so a team could drag its module in, configure it, and create the context for a full walkthrough that always started from the Dashboard. Each team worked out what the new vision meant for its area in a sandbox, then fed back into the Dashboard as a preview, a heads-up display, a peek, or an empty first-time state, plus growth placements my team could route into progressive onboarding.
A design system being rebuilt 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 here. They translated the new look into components, the product teams and I put those components to work in real layouts and pushed them past where they were comfortable, and we reported back where they held and where they broke so the team could iterate. System and application moved in the same loop instead of one waiting on the other. That was, very literally, one of the new ways of working the mandate had asked for, and it held up.
A communication lattice. Coordination on this scale doesn't happen by accident, so I built the structure for it. There was a Slack channel for the aggregate Dashboard view and separate channels for each product team, plus channels for prototyping and the design system. Daily all-team scrums surfaced what was done, what was next, and what was stuck. I ran daily in-person co-design with my own team, held bi-weekly sessions with my ladder-up to clear approvals, and kept weekly prototyping and design-system meetings so we were always ready for the weekly Chief Design Officer review. My daily scrum reports went up through a management channel. The whole thing was built to pyramid, 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. When those reviews moved the strategy, and they did, we absorbed the change and kept going.
The cross-cutting work. Layered on top were initiatives that cut across every team. One was refreshing every illustration in the experience, which I took on by building an inventory and repository the illustration team could work against, tracking where each asset lived, when and why it appeared, and what it needed to convey, in close partnership with content strategy. When the PMO decided to move off spreadsheets onto Asana to unblock itself, I worked alongside them to populate it from the design side. I ran sessions with legal and compliance to keep the vision tied to regulatory reality, and full-stack reviews that paired my design, engineering, and PM leads with their counterparts so everyone was working from the same picture.
The footprint was large. I directly managed 5 surfaces, the PayPal Dashboard, Financial Snapshot, Wallet and the Activity Ledger, Onboarding, and Growth, with around 10 designers who shared responsibilities across them. Around that, I coordinated a cross-functional group of more than fifty people across nine product areas: design, content strategy, engineering, product, and a five-person research team, plus the design system team and legal and compliance partners.
WHAT IT PRODUCED
The most useful outputs of this work weren't screens. They were the ways of working that outlasted the initiative.
The cascading reviews, run on a tight clock, did something the vision work couldn't. Teams that had operated in silos, with their own PMs, roadmaps, and metrics, started seeing how their work fit into one whole, and they saw it weekly. That built working trust that hadn't existed before. The Design Playbook became a real source of truth, a drag-and-drop system anchored at the Dashboard that let anyone assemble a contextually accurate page of the app across regions, languages, account states, and user types.
The honest picture of the outcome is mixed. 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.
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 would 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 actually ship, and to treat those gates as leadership decisions rather than design puzzles. Building the operating model was right. Pairing it with harder, earlier conversations about how ready the strategy really was would have made the effort more durable.
WHAT IT PROVED
Design is the stabilizing force.
The skill here isn't a redesign. It's bringing coherence to a large organization in motion, building the decision spine, the production environment, and the communication structure that let dozens of people across many teams work against an ambitious, still-forming vision without the whole thing fragmenting. It's also the part of design leadership that's hardest to read off a portfolio of finished screens, because it only shows up when the work is fast, ambitious, and not yet settled. That's the condition this was built for.