PayPal's internal tools team faced a massive 1-to-300 designer-to-developer ratio, requiring an innovative way to scale design.
A quality product must be discoverable, useful, usable, accessible, trustworthy, valuable, desirable, and measurable to succeed.
The DesignOps 2.0 model merges traditional design and DevOps principles into a single, unified product development workflow.
Replacing the traditional "telephone game" of requirements with a collaborative model where teams rapidly iterate on prototypes using shared tools.
Product teams take ownership of user research and prototyping, while the UX team transitions to a mentorship and platform-building role.
A single React component library is used in both the UXPin prototyping tool and Storybook documentation to eliminate drift between design and development.
Components must be designed to serve three distinct users: the developer implementing it, the non-technical prototyper, and the final end-user.
The "console" platform uses an SDK and runtime to allow many teams to develop and deploy independently while enforcing UX consistency.
The entire product team is responsible for the user experience, which encompasses not just UI but also latency, errors, and system performance.
Accountability for UX is enforced through mandatory prototyping, heuristic evaluations, baked-in analytics, and transparent public dashboards.
A recap of the five key principles for scaling design, focusing on customer outcomes, a shared component library, and creating shared responsibility.
06:16Philipp Kremer
28:35Lucien Immink
29:53Jade Jiang & Noga Mann
13:57Anna Schoderer & Maximilian Franzke
57:45Robert Hoffmann & Christian Denich
56:24Pablo Ruiz-Muzquiz
26:13Malte Breitzmann & Saskia Henatsch
26:51Rita Castro
.webp?w=240&auto=compress,format)
Jobs that call for the skills explored in this talk.
Speech Processing Solutions
Vienna, Austria
Swisscard Aecs Gmbh
PartSpace