{"type":"rich","version":"1.0","provider_name":"Transistor","provider_url":"https://transistor.fm","author_name":"The Question: Design System Collaborative Learning","title":"Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith","html":"","width":"100%","height":180,"duration":1693,"description":"Episode 079 Recap: The Evolution of Design System Documentation with Ben Callahan and Afyia Smith\n\nBen Callahan and Afyia Smith, a content designer and technical writer specializing in design systems, recap what the community said about who owns documentation and where docs are headed now that machines are reading them too.\nThe survey went to more than 1,100 design system practitioners and drew 61 responses across five questions. The conversation covers the shift from prose to structured content, the case for a dedicated documentation owner, the design system knowledge architect role, the DSDS spec work with PJ Onori, and the fourteen respondents who said machines will be the only future readers of their docs.\nShow Notes\n00:00 — Welcome and introductions\n00:14 — Black-and-white prints and a giraffe collection\n01:00 — Almost 80 episodes, and the first one on docs\n01:24 — Survey setup: 1,100 practitioners, 61 responses\n02:34 — Afyia answers the open-ended question herself\n02:41 — Documentation as a knowledge layer, not just content\n03:20 — Focused ownership and just-in-time documentation\n04:08 — What docs looked like in the early design system days\n04:30 — Bare, scattered, outdated, ungoverned\n06:17 — The case for a point person\n07:53 — The design system knowledge architect role\n08:20 — Coming back a year later to the same mess\n11:03 — Question one results: who owns documentation\n11:57 — By design or by default?\n12:24 — Digging into the 30% who answered \"other\"\n13:36 — Question two: everyone figuring agentic workflows out alone\n14:24 — The correlation that wasn't in the data\n15:00 — Question three: reporting on agentic workflow success\n16:07 — Ownership reveals visibility more than success\n17:00 — Machine readable versus machine parsable\n17:20 — Surface-level changes versus foundational ones\n17:49 — Bad docs surfaced everywhere are still bad docs\n18:49 — Working upstream of AI\n19:38 — The component schema work with PJ Onori\n20:45 — DSDS, doc origin, and metadata as...","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}