Trust Between Teams
summary
Claims clear: design systems are presented as decision frameworks, not just tokens; concrete examples include IBM scaling design from 60 to over 3,000 designers, Airbnb adding an organizational development axis to career ladders, Shopify’s partnership program pairing cross-line makers, and a winter-storm Austin case where local networks improvise food distribution. Methods include visualizing shared maps, creating a system of systems, running eight-week cross-team pilots, and changing incentives and measurements to make cross-team stewardship actually work.
AI-written summary · about
chapters (5)
related talks
32mDo You Trust Me? A look at Trust, Time, and Teams
41mWhy one model can’t fit all creating fulfilling engineering organizations
12mDriving design transformation with your design system
39mThe Key To High-Performing Teams Based On Trust
47mScaling Design Orgs Rapidly for Long Term Success
44mUnderstanding Teams Through Systems Thinking and Stories
29mTeam first
16mMostly Clear, Partly Sunny