Hitting Ctrl+N: How to work through a design breakup
summary
A legacy purchase orders revamp gets designed in Figma, tested in 15 usability studies, and shipped to 80% of merchants after 1.5 years, then gets rolled back because the team rejects the implementation despite agreeing with the problem. The concrete story shows what fails (the how), what was actually built and why it didn’t stick, the tools used, the surprising rollout number, and the recovery steps: two weeks off, journaling, mentorship, facilitation practice, and skills gained that lead to promotion.
AI-written summary · about
chapters (5)
- 0:00Hello, I’m Shanique!
- 2:48Storytime
- 12:01How I recovered
- 14:13So, how do you work through a design breakup?
- 20:55Closing
related talks
24mInside Figma: failing together
50mManaging Design Systems, from Features to Roadmaps
21mResearch-driven design systems
20mDeath to Handovers!
14mRethinking Designer-Developer Collaboration
18mMaking the Things That Help Others Do Their Thing
19mGrow a Design team in a Non-Design-Driven Environment
41mThe Evolution of the Role of Designers | Francesco Vetica and Laura Camillucci