Unifying Your Product Design Org through DesignOps
summary
DesignOps consolidates scattered operational work into one role for a 65-person product org and delivers concrete systems: a governance layer for the jUIce design system, adoption playbooks and component standards implemented during the switch to Figma playbooks in Miro, training on accessibility and localization tied to a goal of fewer translation bugs, and a shared story-pointing for design system plus a visible Miro backlog of quarterly projects that leaders can measure and fund.
AI-written summary · about
chapters (19)
- 0:00Introduction to DesignOps
- 1:03About Citrix and my role
- 2:29What is DesignOps and its value
- 4:34DesignOps for product alignment
- 8:28DesignOps for process consistency
- 12:41DesignOps for people and culture
- 19:00Starting a DesignOps practice
- 22:55Over-communicating DesignOps
- 27:31Recap and celebrating wins
- 28:34Q&A: Story pointing and scope creep
- 30:44Q&A: Consolidating feedback
- 31:27Q&A: Proving DesignOps value
- 33:13Q&A: Challenges and pitfalls
- 35:23Q&A: Vision for DesignOps
- 36:47Q&A: Timing of DesignOps formalization
- 37:53Q&A: Podcast and resources
- 38:16Q&A: Roles and responsibilities
- 39:20Q&A: Transitioning to DesignOps
- 40:45Q&A: Support from team and managers
related talks
35mDesignOps: The Stabilizing Force In Uncertain Times
41mDesignOps 2.0 – Scaling Design
35mTurning UX into Reality: Bringing DesignOps Fundamentals into Organizations
37mDesign Operations: Application and Archetypes of the Discipline
19mDesignOps: The API of design teams
41mDesignOps - How I Built UX Teams from Scratch in a Company
28mTools of Destruction
57mUnifying design and development through design systems