DesignOps: The API of design teams
summary
DesignOps at GitHub frames concrete work: a runnable design onboarding projects workflow built in GitHub Projects that new hires use during week one and month one and that collects iterative feedback, a living how we work docs repo that answers recurring questions, experiments with visibility like lightning shares and an asynchronous weekly WIP issue that fail to scale because of global time zones. Emphasis is on maintainability, reuse of existing tooling, and projects that remove single‑person bottlenecks.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:52Lightbulb moment
- 2:11What does it mean to do DesignOps?
- 7:40Bringing strategic vision to how a design team operates
- 9:20GitHub
- 15:36Who’s doing your work right now?
- 16:35Is the work being celebrated?
- 17:29DesignOps never starts from scratch
- 18:28What projects will make a difference?
- 18:50Closing
related talks
35mDesignOps: The Stabilizing Force In Uncertain Times
41mDesignOps 2.0 – Scaling Design
37mDesign Operations: Application and Archetypes of the Discipline
24mOperationalizing Design from the Ground Up
37mAdding Design to DevOps
42mUnifying Your Product Design Org through DesignOps
41mDesignOps - How I Built UX Teams from Scratch in a Company
35mDesignOps & Its Impact at Uber