Reviewing full customer flows together, instead of siloed products alone, gave every team the same view of the customer experience, sharpened week over week.
Rebuilding PayPal’s app with teams used to incremental work
How I built the operating model that let my team and eight partner product teams execute against an ambitious, still-forming product vision without fragmenting.
We got a design provocation, and we had lost some of those muscles.
A new Chief Product Officer and Chief Design Officer arrived after COVID with big ambitions: turn PayPal from a digital wallet into a place where a customer's financial life and shopping life sat together.
For years we had been tuning a mature product, one release at a time. This was a reinvention, and the people in place had never had to coordinate at that scale.
To set direction, the CDO had a small team craft six core screens at very high fidelity, with no documentation. The screens carried a new look and a lot of new strategy, with no account of how PayPal's organization would support either.
At PayPal, high fidelity meant ready to build, with product development, concept testing and user testing already behind it. These screens were a deliberate challenge, and they reached the C-suite, then product and engineering, before design saw them. The CDO challenged us to fill in the gaps. Product and engineering asked us how it all worked together. We needed a new way of working.
I had to retool our processes
We needed to review and build across several teams, moving fast, all at once. It came together as five moving parts, built in parallel.
I worked with the design and product leaders above me to settle how reviews and decisions would be made, anchored on one new rule: every walkthrough would start at the PayPal Dashboard and build outward. The Dashboard was a live peek of every product, so anchoring prototype reviews made it the primary integration point. I had governance over the Dashboard and its component parts, which made it my responsibility to bring each product team’s pieces together into one coherent whole. The review protocol mirrored the mental model, and the design process was re-focused around it.
Dashboard
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, built to receive. We created it to allow anyone to build a new prototype using the shared source of truth, which enabled individual teams to rapidly work out experiences side by side within their product teams, and those iterations fed back into the Dashboard.
teamShopping
teamDeals & offers
teamRewards
teamCredit
teamSavings
teamCrypto
teamAI assistant
team
All of it had to be skinned against a design system that was being rebuilt at the same time, underneath us. The five-person system team carried an enormous load, and the work moved in a tight bidirectional loop: system and application moving together, neither waiting on the other to finish.
- Five people translating the new look into components
- Put components to work in real layouts, pushed them hard
I set up a meeting rhythm that rolled up to the CDO. 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.
I made a daily Slack check-in mandatory, with a mid-morning readiness deadline every day, so we could audition the current state and decide what to change first.
Across this were initiatives that cut across every team. With content strategy and brand design, we drove an illustration refresh, tracking the inventory and repository the illustration team worked against. We led the PMO's move to Asana, populating the new system from the design vantage point, a seat the org hadn't had before. Standing legal and compliance sessions kept the vision tied to regulatory reality with early, frequent input.
What lasted was the way we worked.
These new ways of working outlasted the initiative. The process got more nimble and integrated across every partner: product, engineering, project management, analytics, legal, and design.
A drag-and-drop build system anchored to the Dashboard let anyone assemble a contextually accurate page across regions, languages, account states, and user types.
The aggregator vision didn't ship; the effort was overtaken by restructuring. What lasted was the operating model: the spine, the Playbook, the cadence, and the relationships.
How I ran the team.
Eight designers reported to me, split across Home, Financial Snapshot, Wallet and Ledger, Onboarding, Growth and Giving, plus a Profile team we stood up for the redesign.
I coach to strengths. One designer had a reputation for being hard to work with because of how they communicated. We worked on reading the room in the moment while leaning on what they did best. Within six months they were a trusted partner again to two teams that had refused to work with them.
I hired an intern whose communication skills were already remarkable, and coached those skills as their lead attribute. They were promoted twice and became our most sought-after design partner. They’re now a staff designer at another company.
Give voice to the hard questions even while building the machine.
I should have pushed harder and earlier to make the strategy's gaps and regulatory hand waving 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, but we'd have been more effective if I'd gotten leadership to name up front what had to be true, from a regulatory and technical standpoint, for the vision to ship.