Is Your UX Design Process Holding You Back?
summary
Bootstraps design at Tessle with a prebuilt RAX component library, rebuilds the whole UI in one week to establish a single system, and keeps quality by running a public UX bug bears + Linear integration for daily filing and fixes. At Multiverse, runs focused quarterly component cleanups, reports Figma metrics (component usage and detachments), merges design systems after an acquisition, and scales UX 4→20 in 2.5 years while shortening hiring rounds and replacing take-home tasks with presubmitted case discussions.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 3:56Product design truth
- 4:41Building Tessle from scratch
- 10:41Daily product quality at Tessle
- 12:55Hiring best practices
- 16:56Engineers designing the product
- 17:43Scaling UX at Multiverse
- 23:21Influence in design systems
- 26:43UX quality muscle at scale
- 28:58Scaling the UX team
- 33:21Hiring reflects team culture
- 34:08Final takeaways
related talks
23mBridging the gap between UX and QA through design systems
41mDesignOps - How I Built UX Teams from Scratch in a Company
49mUX and an Agile Development Process
18mDesign Systems in Practice
40mHow to make UX & Devs build killer products
51mUX + Engineering: A Tale of Two Cities
42mLean UX Lessons Learned from One Dozen Projects
36mMixing Lean UX & Agile Development