> Markdown version of [/videos/194-breaking-down-silos-between-design-and-development?t=1783](https://www.wearedevelopers.com/videos/194-breaking-down-silos-between-design-and-development?t=1783). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Breaking Down Silos Between Design and Development 

How does PayPal maintain exceptional UX with a 1-to-311 designer-to-developer ratio? Discover how shared React components and Design Ops 2.0 completely eliminate the design-to-engineering gap.

- **Speakers:** Erica Rider, Stan Carrico
- **Event:** World Congress 2021
- **Published:** July 1, 2021
- **Duration:** 54:22
- **URL:** https://www.wearedevelopers.com/videos/194-breaking-down-silos-between-design-and-development

## Summary

At PayPal, the Tools and Platform Experience (TPX) organization successfully manages an extreme 1-to-311 designer-to-developer ratio by pioneering "Design Ops 2.0." To scale design support across 60–100 internal products without endlessly expanding the design team, the organization merges DevOps principles with design operations. Instead of policing unread UI documentation, UX professionals pivot into high-leverage coaching roles—empowering product managers and engineers to own the end-to-end design process. By establishing "design on rails," the process natively restricts layout and configuration options, enforcing accessibility and foundational brand consistency by default. This philosophy ensures developers focus on solving core business logic, drastically reducing UI development toil.

A pillar of this transformation is the Equivalent Responsibility Principle, which redefines user experience far beyond visual aesthetics to encompass error handling, API latency, and system trust. Historically, engineers have held 100% of the implementation control with zero accountability for the resulting UX, while designers carried all the accountability with none of the control. By socializing the idea that "UX is the entire deliverable," PayPal holds federated development teams accountable for holistic product quality. Instead of manually instrumenting analytics, UI components feature built-in tracking that fuels public-facing scorecards, sparking a healthy, competitive culture of continuous UX improvement among engineering squads.

To physically prevent drift between static mocks and shipped code, the TPX team relies on a single React-based component library powering both the prototyping phase and the federated development runtime. Using UXPin Merge and Storybook.js, product managers and engineers drag and drop interactive, data-connected React components into high-fidelity prototypes. Because the visual mockups and the production applications share the exact same underlying SDK, the traditional interpretation gap between design and engineering is entirely eliminated. Teams are enabled to test realistic data grids, iterate based on actual user feedback, and ship faster with absolute confidence that the final application will perfectly match the prototype.

**Keywords:** design ops 2.0, scaling organizational design, react component prototyping, uxpin merge prototyping, federated development runtime, equivalent responsibility principle, developer toil reduction, interactive high-fidelity prototyping, internal developer tools UX, built-in component analytics, cross-functional UX accountability, single component library workflow

## Chapters

1. **Overview of the developer experience scope at PayPal** (00:31) — Scaling internal tooling across thousands of developers requires transitioning from individualized support to uniform systems.
1. **Defining product quality through accessibility and user trust** (04:10) — Products must satisfy fundamental accessibility and usability thresholds before advanced capabilities become relevant.
1. **Blending design and development into a single workflow** (09:08) — Fusing specialized roles into unified operational tracks removes frictional handoffs between interface planning and technical execution.
1. **Replacing distinct work silos with interactive team prototypes** (12:47) — Visualizing requirements directly in shared canvas tools eliminates misinterpretation caused by text heavy feature tickets.
1. **Shifting product teams to a customer focused mindset** (19:23) — Product engineers assume primary responsibility for customer outcomes while specialized interface designers shift into coaching roles.
1. **Unifying UI libraries across React development and Storybook** (22:45) — Injecting production code components into layout programs keeps aesthetic mockups functionally identical to finalized applications.
1. **Reducing interface drift using high fidelity interactive prototypes** (27:12) — Reusing baseline code packages for layout dimensions ensures mockups perfectly mirror the final production environment.
1. **Optimizing component libraries for developers and product managers** (29:43) — Complex layouts become highly accessible when internal building blocks parse simple data inputs instead of demanding specialized coding.
1. **Adopting federated development using a single web runtime** (36:57) — Deploying a central application runtime limits blocking updates while retaining consistent styles across independent company applications.
1. **Standardizing navigation and data configurations in web platforms** (40:38) — Extracting generic interface elements like menus into platform defaults accelerates repetitive layout assembly tasks.
1. **Expanding the user experience definition to include latency** (44:15) — Evaluating true usability requires incorporating backend service responses and logical error messaging into core interface standards.
1. **Driving team accountability through public performance metric reporting** (48:03) — Publishing automated telemetry metrics on shared organizational dashboards forces technical teams to proactively address substandard behaviors.
1. **Reviewing strategies for scaling collaborative user experience practices** (52:47) — Adopting shared prototyping ecosystems immediately dissolves destructive boundaries between interface planning and technical execution.

## Related Moments

- [Organizing cross-functional and balanced product teams](https://www.wearedevelopers.com/videos/398-building-the-right-product-and-building-it-right-a-glimpse-into-extreme-programming-atomic-design) (from "Building the Right Product and Building It Right: A Glimpse into Extreme Programming, Atomic Design ")
- [Pioneering the concept of developer experience](https://www.wearedevelopers.com/videos/919-coffee-with-developers-adam-wiggins) (from "Coffee with Developers - Adam Wiggins")
- [Unifying product developer and visual designer user behaviors](https://www.wearedevelopers.com/videos/1345-building-collaborative-open-source-tools-for-developers-and-designers-pablo-ruiz-muzquiz-from-penpot) (from "Building Collaborative Open Source tools for Developers and Designers - Pablo Ruiz-Muzquiz from Penpot")
- [Cross-functional roles and collaboration in a balanced team](https://www.wearedevelopers.com/videos/66-how-to-be-balanced-in-a-software-development-team) (from "How to be balanced in a software development team")
- [Introduction to an open source design prototyping tool](https://www.wearedevelopers.com/videos/1345-building-collaborative-open-source-tools-for-developers-and-designers-pablo-ruiz-muzquiz-from-penpot) (from "Building Collaborative Open Source tools for Developers and Designers - Pablo Ruiz-Muzquiz from Penpot")
- [Restructuring engineering teams into pods for end-to-end feature ownership](https://www.wearedevelopers.com/videos/100128-the-golden-age-of-email-owning-the-inbox-in-the-age-of-ai) (from "The Golden Age of Email: Owning the Inbox in the Age of AI")

## Related Articles

- [Declarative Design and a fresh take on collaboration with developers](https://www.wearedevelopers.com/magazine/595-declarative-design-and-a-fresh-take-on-collaboration-with-developers)
- [Are design and development really just the same thing?](https://www.wearedevelopers.com/magazine/520-are-design-and-development-really-just-the-same-thing)
- [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters)
- [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)

## Related Jobs

- [Senior Web Designer, Growth](https://www.wearedevelopers.com/jobs/ext/102722-senior-web-designer-growth) at **Intercom, Inc.**
- [React Engineer for Next.js UI - Hybrid, Impactful FinTech](https://www.wearedevelopers.com/jobs/ext/1444505-react-engineer-for-next-js-ui-hybrid-impactful-fintech) at **Bitpanda**
- [iOS Engineer, Swift/SwiftUI/Combine (B2C Broker)](https://www.wearedevelopers.com/jobs/ext/1611832-ios-engineer-swift-swiftui-combine-b2c-broker) at **Bitpanda**
- [Senior Software Engineer, React (Investing & Trading)](https://www.wearedevelopers.com/jobs/ext/1937625-senior-software-engineer-react-investing-trading) at **Bitpanda**
- [React Engineer For Next.Js Ui - Hybrid, Impactful Fintech](https://www.wearedevelopers.com/jobs/ext/1934580-react-engineer-for-next-js-ui-hybrid-impactful-fintech) at **Bitpanda**
- [Senior Software Engineer, React (Websites & Martech)](https://www.wearedevelopers.com/jobs/ext/1605272-senior-software-engineer-react-websites-martech) at **Bitpanda**