DesignOps 2.0 – Scaling Design
summary
PayPal reframes design as an operational layer called DesignOps 2.0 that trains 60–100 product teams and supports ~1,000 developers with just five designers by shipping constrained components and a platform console. Teams use UXPin prototypes and a library of 63 components plus 3.5 hours of training to build working prototypes in ~10 minutes. A proof‑of‑concept wizard component records time-to-complete metrics, step drop‑offs and latency so dev teams are measured and held accountable for UX improvements.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:58Challenge of consistency and scale
- 5:48DesignOps' mission at PayPal
- 6:41Traditional model vs. DesignOps 2.0
- 14:19Evolution of teams' responsibilities
- 18:43What Erica found out about UX
- 21:36DesignOps 2.0 tools
- 26:09Getting to DesignOps 2.0
- 31:41Chat questions
related talks
41mDesignOps - How I Built UX Teams from Scratch in a Company
01h 06mScaling Design
37mDesign Operations: Application and Archetypes of the Discipline
19mDesignOps: The API of design teams
18mDesign Systems in Practice
42mUnifying Your Product Design Org through DesignOps
50mLean Design in Practice
35mTurning UX into Reality: Bringing DesignOps Fundamentals into Organizations