“Partnership & Trust to Fuel Growth”
summary
Gap builds Stitch, a design system run by two dedicated teams (Ecommerce ~8–10 front‑end devs + designer; Associate Enablement ~3 devs + designer) that starts with styles and grows through office hours, developer embeds and time‑boxed ambassadorships, design sprints and journey mapping. A pragmatic scorecard rates components on code quality, performance, usability and citizenship. Migration to React forces embeds, contribution workflows and a build‑measure‑learn cycle, which increases adoption, fixes performance blind spots and shifts culture toward shared ownership.
AI-written summary · about
chapters (11)
- 0:00Introduction to Stitch
- 1:58Challenges in scaling systems
- 3:56Design system analogies
- 6:52The cultural shift
- 9:30Building system maturity
- 12:09Collaboration methodologies
- 18:59Workshops and journey mapping
- 23:57Co-creation with brands
- 26:03Communication and scorecards
- 30:23Build, measure, learn approach
- 34:45Conclusion and reflections
related talks
20mDesign Systems for the Rest of Us
21mFrom handoffs to upstream
28mCreating Better Products Together. UX and Engineering Working in Harmony
33mSolving the Design System Problem When Products Live for Decades
45mBridge the Gap between Design and Development
58mLet's Work Together!
19mYou've Built a Design System - Now What?
25mEnterprise Final Frontier – is it possible to change the corporate ways...