{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Question: Design System Collaborative Learning","title":"Episode 081 Recap: The Culture We Build with Ben Callahan and Shaun Bent","html":"<iframe width=\"100%\" height=\"180\" frameborder=\"no\" scrolling=\"no\" seamless src=\"https://share.transistor.fm/e/82751af3\"></iframe>","width":"100%","height":180,"duration":1957,"description":"Ben Callahan and Shaun Bent look back on the Episode 081 deep dive about how design systems shape, and are shaped by, the cultures of the organizations they serve. They walk through the four survey questions (1,124 practitioners invited, 45 responses) and talk about who decides when product priorities conflict with cohesion, how incentives shift over time, what “deciding together” looks like in practice, and a story about three teams building three tab bars.\nShow Notes\n 00:00 — Welcome and Shaun on why this topic fascinates him\n 00:30 — Redwoods UK meetups in London and Manchester, ahead of Converge\n 01:26 — Overview of the four survey questions\n 03:12 — Response count and where to find the raw data\n 03:34 — Shaun on “we decide together” topping Question 1\n 04:18 — How collaboration has grown as systems have matured\n 05:16 — Do designers care about cohesion more than engineers?\n 06:53 — Ben on why this is individual, not disciplinary\n 07:52 — The long history of systematic thinking in design and engineering\n 09:18 — Why is working systematically still hard? Incentives\n 11:22 — Autonomy as an expectation vs. what systems ask of teams\n 12:31 — Shaun: understand your organization’s shape or the system gets stuck\n 13:34 — Speed and innovation vs. quality and cohesion\n 14:21 — Shaun on system teams as enabling teams\n 15:00 — How incentives cascade from CEO vision to individual promotions\n 16:00 — Shaun on shifting priorities during nine years at Spotify\n 19:03 — Showing a system’s value when priorities keep changing\n 20:21 — Unpacking what “deciding together” looks like\n 21:24 — Choosing one or two teams to go deep with, per Christoph and Maya\n 22:31 — “White glove service” as a carrot for other teams\n 23:55 — Ben on the risk of over-supporting consuming teams\n 25:55 — Three moments for disagreement: before, during, and after production\n 26:53 — Shaun on why he didn’t check “before” in Question 2\n 27:29 — Shaun’s story: three teams building three tab bars\n 29:14 — Why...","thumbnail_url":"https://img.transistorcdn.com/8ZoZhDyVederAFF-YGuNFdyaUvqzao3a6rYS6VFp3F4/rs:fill:0:0:1/w:400/h:400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9kMjQ2/MjJjYzdiYmY4MWU0/NGQzMjJmOGUyNzlj/YmMwZS5wbmc.webp","thumbnail_width":300,"thumbnail_height":300}